YCloud WhatsApp API MCP Server
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 |
|---|---|
| wa_business_listB | List WABAs |
| wa_business_retrieveC | Retrieve a WABA |
| wa_inbound_markC | Mark message as read |
| wa_msg_send_directlyD | Send a message directly |
| wa_msg_sendD | Enqueue a message |
| wa_msg_retrieveC | Retrieve a message |
| wa_phone_listB | List phone numbers |
| wa_phone_retrieveD | Retrieve a phone number |
| wa_phone_retrieve_profileC | Retrieve a phone number profile |
| wa_phone_update_profileC | Update a phone number profile |
| wa_phone_retrieve_commerce_settingsD | Retrieve commerce settings |
| wa_phone_update_commerce_settingsD | Update commerce settings |
| wa_phone_registerC | Register a phone number |
| wa_template_listC | List templates |
| wa_template_createD | Create a template |
| wa_template_delete_by_nameC | Delete templates by name |
| wa_template_getC | Retrieve a template |
| wa_template_deleteC | Delete a template |
| wa_template_editD | Edit a template |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools have distinct purposes targeting specific WhatsApp API resources (WABAs, messages, phones, templates) with clear action verbs. However, wa_msg_send and wa_msg_send_directly could cause confusion as they both send messages with only a delivery timing distinction that might not be immediately clear from the names alone.
All tool names follow a consistent snake_case pattern with a clear wa_resource_action structure (e.g., wa_business_list, wa_msg_send, wa_template_create). The naming convention is predictable and uniform across all 19 tools, making them easily parsable.
With 19 tools, the count is slightly high but reasonable for a comprehensive WhatsApp API server covering multiple resource types (businesses, messages, phones, templates). It provides detailed operations without being overwhelmingly large, though it borders on the heavy side.
The tool set offers complete CRUD/lifecycle coverage for all key WhatsApp API domains: WABAs (list/retrieve), messages (send/retrieve/mark read), phone numbers (list/register/retrieve/update settings and profile), and templates (create/edit/get/list/delete). No obvious gaps exist for typical agent workflows.