mcp-whatsapp
Related Servers
Alternatives to mcp-whatsapp
- MIT
- AlicenseAqualityBmaintenanceEnables Claude to interact with WhatsApp on macOS through the Model Context Protocol. It allows reading messages, searching contacts, listing chats, and sending replies via natural conversation.841 PyPI2MIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server providing Claude with full access to Brevo's marketing automation platform through the official SDK, featuring tools for email operations, contact management, campaigns, SMS, conversations, webhooks, e-commerce, and account management.16131 npm3MIT
- AlicenseBqualityDmaintenanceEnables sending WhatsApp Business messages including text, media, interactive lists/buttons, and template management through the WhatsApp Business API via Nango integration.11MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables AI to control WhatsApp Web via Puppeteer Stealth for reading and sending messages. It features human-like interaction patterns and anti-ban protections to securely manage chats and communications through natural language.311 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to interact with WhatsApp through the WSAPI service, supporting comprehensive messaging, contact management, group operations, and account management functionality. Allows sending various media types, managing chats, and controlling WhatsApp sessions through natural language.10114 npm3MIT
Related Servers
- AlicenseBqualityBmaintenanceFull-featured personal WhatsApp MCP server: read and full-text search all chats, send, reply, react, edit and delete, media as raw files, groups and communities, multi-account and live notifications. Rust server with a Go whatsmeow bridge, local SQLite.392MIT
- AlicenseNot gradedqualityCmaintenanceWhatsApp MCP server that exposes messaging, groups, contacts, and profile management as tools and resources for AI agents, supporting Baileys and Meta Cloud API.26MIT
- FlicenseBqualityDmaintenanceRead-only MCP server for WhatsApp Web allowing listing chats and reading recent messages, without sending or mutating WhatsApp state.33 npm-
- AlicenseNot gradedqualityCmaintenanceMCP server for WhatsApp that exposes send, read, and media management tools through the waxum REST API gateway, enabling any MCP client to interact with WhatsApp chats and media over stdio.2MIT
- AlicenseNot gradedqualityDmaintenanceA least-privilege, send-only MCP server for WhatsApp, backed by Meta's official WhatsApp Cloud API. It exposes tools to send text messages and pre-approved templates.8 npmMIT
- AlicenseNot gradedqualityBmaintenanceA secure, zero-setup WhatsApp MCP server that lets AI assistants read, search, summarize, and (with user confirmation) act on personal WhatsApp chats via a safety-focused toolset, built as a maintained successor to the abandoned whatsapp-mcp.5MIT
TDQS
Scored across 42 tools
Most tools target clearly distinct resources or actions, and descriptions explicitly cross-reference alternatives such as send_presence vs send_typing and send_file vs send_audio_message. Minor overlap remains between get_status and pairing_status, and between mark_read and mark_chat_read, but careful reading resolves the ambiguity.
The set is predominantly snake_case with a verb_noun pattern (send_message, get_chat, set_group_name, list_messages). A few outliers break the pattern, notably pairing_status as a noun phrase and is_on_whatsapp as a predicate, but the convention is still mostly predictable.
42 tools is well above the typical 3–15 range for an MCP server and exceeds the 25+ threshold. While WhatsApp is a broad domain, several tools could be consolidated (e.g., status/pairing, read-marking, group setting updates), making selection unnecessarily heavy.
The surface covers a very full WhatsApp lifecycle: sending, editing, deleting, replying, reacting, media download, message search/context, group creation/join/leave/settings/participants, blocking, privacy, presence, polls, contacts, sync, and pairing/status. Core workflows have no obvious dead ends.