Evolution API MCP is answering right now. Last checked 6 min ago. 85 installs a week from pypi. Last commit 8 Oct 2026.
Operate one Evolution API (WhatsApp) instance: chats, history, sending, groups, settings.
Today is the operative word: we check Evolution API MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
claude mcp add evolution-api-mcp --transport http https://evolution-mcp.singleflo.com/mcp
https://evolution-mcp.singleflo.com/mcp
[mcp_servers.evolution-api-mcp]
url = "https://evolution-mcp.singleflo.com/mcp"
{
"mcpServers": {
"evolution-api-mcp": {
"url": "https://evolution-mcp.singleflo.com/mcp"
}
}
}
{
"servers": {
"evolution-api-mcp": {
"type": "http",
"url": "https://evolution-mcp.singleflo.com/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://evolution-mcp.singleflo.com/mcp | streamable-http | sign-in | 313 ms | 6 min ago |
MCP server for Evolution API — WhatsApp messaging, instances, contacts
MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management.
Read WhatsApp chats and groups, and send messages when allowed, through the WaGate API.
Read WhatsApp chats and groups, and send messages when allowed, through the HelloHop API.
Operate WhatsApp Business: conversations, contacts, chatbot flows, templates, CRM and store.
Manage WhatsApp, Telegram and MAX mailings: audiences, drafts, moderation and sending.
Team WhatsApp inbox: read chats and contacts; every send needs a person's confirmation.
Set up and run your Conciergr WhatsApp assistant: settings, documents, team and Team Inbox.
Answers built from our own checks of this server.