home / mcp / mcp evolution api mcp server
MCP server for evolution, the non official api for whatsapp
Configuration
View docs{
"mcpServers": {
"aiteks-ltda-mcp-evolution-whatsapp-api": {
"url": "http://localhost:3000",
"headers": {
"EVOLUTION_API_KEY": "REPLACE_WITH_YOUR_REAL_KEY",
"EVOLUTION_API_URL": "https://evo-api.decisao.ai/"
}
}
}
}You can connect Claude to WhatsApp through the Evolution API using this MCP server. It acts as a bridge between your Claude workflows and WhatsApp, enabling you to manage instances, send a variety of messages, handle contacts and groups, and configure webhooks and settings in a cohesive MCP environment.
Connect an MCP client to the Evolution API MCP server to start automation with WhatsApp. Use the HTTP endpoint to interact with the server from your MCP client or orchestration layer. You can run the server locally or deploy it via Docker Compose, then point your Claude MCP client at the provided URL. Once connected, you can manage WhatsApp instances, send messages (text, media, location, contacts, etc.), and configure webhooks and settings through MCP actions.
Prerequisites: you will need a runtime environment and tooling similar to the following options. Choose the path that fits your deployment needs.
# Local development setup (using Bun as shown in setup steps)
git clone https://github.com/aiteks-ltda/mcp-evo-api.git
cd mcp-evo-api
bun install
bun run devAlternative local production build and run path.
git clone https://github.com/aiteks-ltda/mcp-evo-api.git
cd mcp-evo-api
bun install
bun run build
bun run dist/main.jsDocker Compose deployment lets you run the MCP server as a service. Use this when you want a self-contained, orchestrated setup.
git clone https://github.com/aiteks-ltda/mcp-evo-api.git
cd mcp-evo-api
docker-compose up -dIf you prefer a standalone Docker container, run the container with the required environment variables.
docker run -d -p 3000:3000 -e EVOLUTION_API_URL=yoururl -e EVOLUTION_API_KEY=yourkey --name mcp-evo-api ghcr.io/aiteks-ltda/mcp-evo-api:latestThe server expects Evolution API credentials to be provided via environment variables. Create a local .env with the following values, or configure them in your deployment environment.
EVOLUTION_API_URL=https://evo-api.decisao.ai/
EVOLUTION_API_KEY=REPLACE_WITH_YOUR_REAL_KEYTo connect Claude Desktop to the locally running MCP server, configure the HTTP MCP with the server URL.
{
"mcpServers": {
"evo-api": {
"url": "http://localhost:3000",
"args": []
}
}
}If you are deploying with Docker, point Claude Desktop at the container URL.
{
"mcpServers": {
"evo-api": {
"url": "http://localhost:3000"
}
}
}Retrieve server information and status to understand the current state of the MCP server.
Create a new WhatsApp instance within the Evolution API integration.
List all configured WhatsApp instances managed by the MCP server.
Establish a connection to a specific WhatsApp instance.
Restart a given WhatsApp instance to recover from errors or apply updates.
Query the current connection state of an instance.
Logout and disconnect an active WhatsApp instance.
Remove an existing WhatsApp instance from the MCP server.
Configure webhooks to receive event updates from the Evolution API.
Retrieve details about configured webhooks.
Apply global or per-instance settings for the Evolution API integration.
Query current settings for visibility and troubleshooting.
Send plain text messages to contacts, chats, or groups.
Send media attachments such as images, videos, or documents.
Send audio messages in WhatsApp format.
Send sticker messages to recipients.
Share location details within chats.
Share contact cards with recipients.
React to messages with a chosen emoji or reaction.
Create and send polls within a chat.
Send structured lists with selectable options.
Attach interactive buttons to messages.
Search and retrieve contact information.
Find and list current chats for quick access.
Locate a group by its JID (Jabber ID).
Retrieve all groups associated with the account.
List members within a specific group.