Titanmind WhatsApp MCP
Related Servers
Alternatives to Titanmind WhatsApp MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with WhatsApp by sending messages, triaging urgent conversations, scheduling messages, and managing automated replies with safety controls and human approval.6 npmMIT
- AlicenseBqualityAmaintenanceEnables managing WhatsApp Business accounts through natural language, including sending messages, managing contacts, and querying conversations.6214 npmISC
- AlicenseAqualityDmaintenanceConnects AI assistants to the official Meta WhatsApp Cloud API for managing conversations and sending various message types through natural language. It provides tools for media management, template messages, and real-time webhook processing without the risk of account bans.186 npm23MIT
- AlicenseNot gradedqualityBmaintenanceAutomate and manage WhatsApp groups, communities, and channels with scheduling, moderation, analytics, and more.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables sending messages, managing templates, uploading media, and configuring webhooks for WhatsApp Business via the MCP protocol.10 npm5MIT
- AlicenseBqualityDmaintenanceEnables sending WhatsApp Business messages including text, media, interactive lists/buttons, and template management through the WhatsApp Business API via Nango integration.11MIT
TDQS
Scored across 6 tools
The tools have distinct purposes (get conversations, get messages, get templates, register template, send template messages, send direct messages), but some ambiguity exists between 'send_msg_to_multiple_num_using_approved_template' and 'send_whatsapp_message_to_a_conversation' since both involve sending messages. The lack of descriptions for most tools exacerbates this overlap.
Naming is inconsistent with mixed conventions: some use snake_case with underscores (e.g., 'get_conversations_from_the_last_day'), others have trailing underscores (e.g., 'get_the_messages_of_a_conversation_'), and verbs vary (e.g., 'get' vs. 'register'). While all names are descriptive, the lack of a uniform pattern reduces predictability.
With 6 tools, the count is reasonable for a WhatsApp-focused server, covering core operations like retrieving conversations/messages/templates, registering templates, and sending messages. It's slightly lean but not overly sparse, allowing for basic functionality without being overwhelming.
The server covers key WhatsApp operations (read conversations/messages, manage templates, send messages), but there are notable gaps: no tools for updating or deleting templates, managing conversation participants, or handling message statuses. The surface supports basic workflows but lacks full lifecycle management for templates and conversations.