claude-whatsapp-mcp
Related Servers
Alternatives to claude-whatsapp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read, search, and reply to your personal WhatsApp messages by linking as an extra device, with support for chat history, full-text search, media downloads, and sending messages or files.32 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnect Claude Desktop to WhatsApp. Send & receive messages, manage groups, share media — all through natural conversation with Claude.32 npm2MIT
- AlicenseNot gradedqualityDmaintenanceConnect your personal WhatsApp to Claude — send messages, read chats, and manage contacts.GPL 3.0
- 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.2840 PyPI2MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to interact with WhatsApp: read chats, search messages, send messages with a mandatory confirmation step, and transcribe voice notes locally, all with encrypted storage and prompt-injection scrubbing.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to read and send WhatsApp messages, including media and call history, via a local bridge.MIT
TDQS
Scored across 22 tools
Each tool targets a clearly distinct resource and action: chat listing, message search/send, media download, group administration, community management, and broadcast progress are all separated without meaningful overlap. Even adjacent tools like send_message vs broadcast_message or update_group vs manage_group_participants are easy to tell apart from their descriptions.
The vast majority of tools follow a clear verb_noun pattern such as list_chats, send_message, create_group, and manage_group_participants. A few noun-style names like whatsapp_status, broadcast_status, and group_invite_link break the pattern slightly, but there is no mixing of naming conventions or casing.
With 22 tools, the surface is noticeably above the typical 3–15 well-scoped range and feels heavy, even though the extra tools serve legitimate WhatsApp features like communities, group management, and broadcasting. The count is not excessive for a full-featured integration, but it is borderline and could benefit from consolidating status and maintenance operations.
The server covers the core WhatsApp workflow well: authentication, chat retrieval, message send/read/search, media transfer, group CRUD, participant management, community linking, and broadcast lifecycle. Minor gaps exist around community deletion/updating, contact/profile management, and richer message types like locations or polls, but these are workaround-level rather than blockers.