whatsapp-local-mcp
Related Servers
Alternatives to whatsapp-local-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to read and send WhatsApp messages, including media and call history, via a local bridge.MIT
- AlicenseNot gradedqualityBmaintenanceProvides Claude with read-only access to your WhatsApp chat history entirely on your local machine, enabling natural language search, summarization, and retrieval of messages without sending data to the cloud.11 npmMIT
- AlicenseNot gradedqualityDmaintenanceGives Claude Desktop read-only access to your WhatsApp chats and message history via a local MCP server.3 npm3MIT
- 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.MIT
- AlicenseNot gradedqualityCmaintenanceProvides Claude Code read-only access to WhatsApp chats by mirroring them into a local SQLite database, allowing search, message listing, media retrieval, and optional voice-note transcription without any send capability.MIT
- 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
TDQS
Scored across 19 tools
Each tool has a clearly distinct purpose: message retrieval, media handling, connection management, and brief operations are all separate. Even the three save tools (save_image, save_voice, save_media) are differentiated by type and specificity, and descriptions reinforce the differences.
Almost all tools follow a clear verb_noun pattern (e.g., get_recent_messages, save_media_window). The only outlier is where_do_media_files_go, which uses a full question instead of a concise verb_noun. The overall pattern is strong and predictable.
19 tools is slightly above the typical 3-15 range, but the complexity of WhatsApp interaction (connection, caching, media, transcription, briefing) justifies the count. Each tool serves a unique purpose without redundancy.
The tool set covers reading, searching, caching, and analyzing messages well. However, it notably lacks any send_message or outgoing action capability, which is a significant gap for a messaging platform. The focus appears to be on passive analysis, but the omission limits potential workflows.