evolution-api-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Ambiente (production ou development) | |
| MCP_SERVER_PORT | No | Porta do servidor MCP | 3000 |
| EVOLUTION_API_KEY | Yes | Chave da Evolution API | |
| EVOLUTION_API_URL | Yes | URL base do Evolution API |
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 | {} |
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
Each tool has a clearly distinct purpose, covering different aspects like instance management, messaging, group management, and templates. There is no overlap or ambiguity between tools.
Most tools follow a verb_noun pattern (e.g., create_instance, send_text). However, 'instance_status' breaks the pattern (noun_verb), causing a minor inconsistency.
25 tools is slightly above the typical range but still appropriate for a comprehensive WhatsApp API. Each tool addresses a distinct operation, and the count feels well-scoped.
The tool set covers core operations for instance management, messaging, group management, templates, and contacts. Minor gaps exist (e.g., no explicit instance QR retrieval, no update group info), but agents can handle most workflows.