HelloHop WhatsApp MCP
Related Servers
Alternatives to HelloHop WhatsApp MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read, search, and send personal WhatsApp messages and files through a locally linked device.44 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to read, search, and send WhatsApp messages with a server-enforced send gate for safety.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to pair multiple self-hosted WhatsApp accounts via QR and read chats, contacts, messages, and groups, as well as send text or attachments from an explicitly selected account through standard MCP transports with scoped credentials.GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to access a user's WhatsApp account as a linked device, with local search of chats and messages, inbox and review workflows, and permission-gated sending, editing, reacting, deleting, and chat-management actions.4,094 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents and MCP clients to read and send WhatsApp messages and media, search chats, and manage contacts and groups after a one-time QR pairing.44 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets any MCP client read, search, and optionally send messages from a linked personal WhatsApp account through a hosted endpoint secured by a bearer token.3MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource (channel status, chats, contacts, messages, groups, communities). The main potential confusion is list_chats (from the gateway's log) versus list_groups (queried from WhatsApp), but the descriptions explicitly spell out this log-vs-live distinction, so misselection risk is low.
Most tools follow a clean verb_noun pattern (list_chats, get_contact, read_messages, list_groups, get_group, get_community, list_community_subgroups). The lone deviation is channel_status (noun_state) and the minor read_ vs get_ split for retrieval, but the set is highly readable overall.
Eight tools is well-scoped for a WhatsApp gateway: channel health, chat/message reading, contacts, groups, and communities each earn their place without redundancy.
The surface is coherent but read-only: there is no send-message tool, no list_contacts (only get_contact), and no way to create or modify groups, which are obvious lifecycle gaps for a messaging-domain server. Core read workflows are covered, but agents will hit dead ends for any write action.