Titanmind WhatsApp MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_conversations_from_the_last_dayD | – |
| get_the_messages_of_a_conversation_D | – |
| send_whatsapp_message_to_a_conversationD | – |
| register_msg_template_for_approvalB | |
| get_the_templatesD | – |
| send_msg_to_multiple_num_using_approved_templateD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| whatsapp_and_server_workflow | WhatsApp messaging workflow guide, and server tools return info |
| send_whatsapp_message | WhatsApp messaging workflow guide, and server tools return info |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| whatsapp_and_server_workflow_resource | WhatsApp messaging workflow guide, and server tools return info |
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.