wazap-mcp
Related Servers
Alternatives to wazap-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that connects AI agents to WhatsApp using the multi-device API, enabling messaging, group management, and more as a regular user.9 npmMIT
- FlicenseNot gradedqualityCmaintenanceWhatsApp MCP server that exposes messaging, groups, contacts, and profile management as tools and resources for AI agents, supporting Baileys and Meta Cloud API.22-
- AlicenseNot gradedqualityBmaintenanceMCP server that turns WhatsApp into agent-callable tools, enabling search contacts, send/receive messages, read chats, handle media, and monitor calls via the WhatsApp Web multi-device protocol.3 npmMIT
- AlicenseNot gradedqualityAmaintenanceA native MCP server for SocialMate that gives your AI a WhatsApp, enabling it to send and read messages, manage contacts and groups, and more through 44 tools.11 npm1MIT
- AlicenseNot gradedqualityAmaintenanceA self-hosted WhatsApp bridge that exposes a stdio MCP server with ~20 tools for reading conversations, sending messages, managing groups, contacts, and aliases, enabling AI agents to operate WhatsApp directly.2MIT
- FlicenseNot gradedqualityBmaintenanceOpenWA MCP server that bridges AI agents to the OpenWA WhatsApp API, exposing 40 tools for sessions, messages, contacts, groups, and webhooks so agents can read and send WhatsApp messages through a self-hosted OpenWA gateway.-
TDQS
Scored across 33 tools
Most tools have clearly distinct purposes, but the set includes several message-reading and account-related tools (read_messages, get_recent_messages, get_unanswered, wait_for_messages; get_status, list_accounts) that could cause hesitation despite descriptive guidance. The draft/send pattern is well differentiated.
Nearly all tools use snake_case with a verb-first pattern, but a few names (learn, get_unanswered, mark_handled, wait_for_messages, confirm_send) deviate from strict verb_noun structure. Still predictable overall.
33 tools is well above the typical 3–15 range for a focused server, and many granular operations (five send_* drafts, multiple get_* variants, manage_group bundling many actions) could be consolidated. This increases selection overhead and cognitive load.
The surface covers core messaging, contacts, groups, media, account linking, and chat management with CRUD-like operations, leaving few dead ends. Minor gaps exist (e.g., no unlink/logout, no block/unblock contacts, no WhatsApp-side contact editing), but agents can work around most.