WhatsApp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WATI_TENANT_ID | No | Your Wati tenant ID (only for multi-channel setups) | |
| WATI_AUTH_TOKEN | Yes | Your Wati authentication token (Bearer token from dashboard) | |
| WATI_API_BASE_URL | Yes | The base URL for the Wati API (e.g. https://live-mt-server.wati.io) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_contactsA | Search WhatsApp contacts by name or phone number. Returns contact information including name, phone, WhatsApp ID, status, teams, and custom parameters. |
| list_contactsA | List WhatsApp contacts with pagination. |
| get_contactB | Get detailed information about a specific contact. |
| add_contactA | Add a new WhatsApp contact. |
| update_contactsC | Bulk-update contacts' custom parameters. |
| get_contact_countA | Get total number of WhatsApp contacts. |
| assign_contact_teamsB | Assign a contact to one or more teams. |
| get_messagesA | Get conversation messages for a contact or conversation. |
| send_messageA | Send a WhatsApp text message to a contact. |
| send_fileB | Send a file (image, video, document, audio) via WhatsApp. |
| send_file_via_urlA | Send a file by URL without downloading it locally first. |
| download_mediaC | Download media from a WhatsApp message. |
| send_interactiveA | Send an interactive WhatsApp message with buttons or a list. |
| assign_operatorA | Assign an operator to a WhatsApp conversation. Pass no email (or null) to assign to the bot. |
| update_conversation_statusB | Update a conversation's status. |
| list_templatesA | List WhatsApp message templates. |
| get_templateB | Get details of a specific message template. |
| send_templateB | Send template messages to one or more recipients. |
| list_campaignsB | List broadcast campaigns. |
| get_campaignC | Get details and statistics for a broadcast campaign. |
| list_channelsC | List available WhatsApp channels. |
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 21 tools
Tools generally target distinct actions (e.g., send vs list vs get), but there is some overlap between send_file and send_file_via_url, and between send_message, send_interactive, send_template. Descriptions help disambiguate, but the similarities could cause misselection.
All tools follow a consistent verb_noun snake_case pattern (e.g., add_contact, list_templates, send_message). No mixing of styles or confusing abbreviations.
21 tools is on the higher side but still reasonable for a comprehensive WhatsApp server covering contacts, messaging, campaigns, and media. Could be slightly trimmed by merging file-send tools, but not excessive.
Covers most common operations (CRUD for contacts, sending various message types, campaigns, templates), but lacks delete operations for contacts, templates, and campaigns. This is a notable gap that may hinder some workflows.