Zappaz MCP Server
Related Servers
Alternatives to Zappaz MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables connecting a personal WhatsApp number to any MCP client, providing tools to send, search, and manage WhatsApp messages, with an optional auto-reply feature.23 PyPI5MIT
- AlicenseNot gradedqualityCmaintenanceEnables connecting a personal or business WhatsApp account via QR pairing and then sending/reading messages, managing chats, contacts, groups, and searching message history through MCP tools.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables WhatsApp automation through MCP protocol, allowing users to manage sessions, send messages, handle groups/communities, and access contacts through natural language interactions with AI agents.3 npm-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send and receive WhatsApp messages, search chats, share media, manage approvals, and get activity summaries through MCP.Apache 2.0
- AlicenseBqualityBmaintenanceEnables sending messages, images, documents and more on WhatsApp directly from any MCP-compatible AI, with tools for chat management, groups, and webhooks.371MIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.6 npmMIT
TDQS
Scored across 22 tools
Each tool targets a distinct resource and action: webhook CRUD, message sending by type, and group management operations. Overlaps like update_group vs. update_group_picture are clearly differentiated by their descriptions. An agent can reliably select the intended tool.
All tools use a consistent snake_case verb_noun pattern in Portuguese/English mixed terms, e.g., send_text_message, create_webhook, add_participants. Pluralization varies slightly but follows natural resource semantics and remains predictable.
With 22 tools, the set is borderline heavy for the scope. While most map to distinct API operations, several message send variants and group participant actions could potentially be consolidated. It is still navigable but sits in the heavy range.
Webhook lifecycle is complete, but message handling lacks retrieval/list operations (e.g., get messages, mark as read) and group management lacks delete/get group details or leave group. These omissions are notable for an agent relying on full CRUD workflows.