Evolution API WhatsApp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Entorno | development |
| MCP_SERVER_PORT | No | Puerto del servidor HTTP | 3000 |
| TEMPLATE_STORAGE | No | Tipo de almacenamiento | json |
| EVOLUTION_API_KEY | Yes | API Key global | |
| EVOLUTION_API_URL | No | URL de Evolution API | http://localhost:8080 |
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 |
|---|---|
| create_instanceB | Create a new WhatsApp instance |
| list_instancesC | List all WhatsApp instances |
| connect_instanceC | Connect a WhatsApp instance |
| instance_statusA | Get connection status of an instance |
| delete_instanceB | Delete a WhatsApp instance |
| send_textC | Send a text message |
| send_mediaC | Send media (image, video, audio, document) |
| send_buttonsD | Send message with buttons |
| send_listC | Send interactive list message |
| list_templatesC | List all message templates |
| get_templateB | Get a specific template by ID |
| create_templateC | Create a new message template |
| send_templateC | Send a message using a template |
| delete_templateC | Delete a custom template |
| update_templateB | Update an existing template |
| search_templatesC | Search templates by text |
| list_contactsC | List all contacts |
| check_numberC | Check if phone numbers have WhatsApp |
| create_groupB | Create a new WhatsApp group |
| list_groupsC | List all groups |
| add_participantsC | Add participants to a group |
| remove_participantsB | Remove participants from a group |
| get_chatsC | Get all chats |
| get_messagesC | Get messages from a chat |
| read_messageC | Mark message as read |
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 25 tools
Most tools have clearly distinct purposes targeting specific WhatsApp operations like instance management, messaging, group handling, and template management. However, there is some potential overlap between 'send_text', 'send_template', 'send_buttons', 'send_list', and 'send_media' as they all involve sending messages, though their descriptions differentiate them by message type.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_group', 'list_contacts', 'send_media', and 'update_template'. All tools use snake_case with clear, descriptive verbs aligned with their actions, making the set predictable and easy to understand.
With 25 tools, the count is on the higher end for an MCP server, bordering on heavy. While it covers a broad range of WhatsApp functionalities comprehensively, it may feel overwhelming or redundant in some areas, such as multiple message-sending tools, which could have been consolidated.
The tool set provides extensive coverage for WhatsApp operations, including instance lifecycle (create, connect, delete, status), messaging (text, media, templates, interactive), group management (create, add/remove participants, list), and template CRUD (create, get, update, delete, list, search). No obvious gaps are present for the domain.