Evolution API MCP server
MCP server for Evolution API — WhatsApp messaging, instances, contacts
271 stars
Reviews
Write oneNobody has reviewed Evolution API yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Evolution API tools (25, 10 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
archive_chatArchive or unarchive a chat
check_numberCheck if a phone number is registered on WhatsApp
connection_stateGet the connection state of an instance (open, connecting, close)
create_groupwrite actionCreate a WhatsApp group
create_instancewrite actionCreate a new WhatsApp instance
delete_instancewrite actionDelete an instance permanently
delete_messagewrite actionDelete a message for me or for everyone in a chat
fetch_group_invite_codeFetch the invite code/link for a WhatsApp group
get_chat_historyGet full chat history with pagination support
get_contactsGet contacts from an instance
get_group_infoGet group metadata, participants, and settings
get_instancesList all WhatsApp instances
get_messagesGet messages from a chat
get_qrcodeGet QR code for instance pairing
leave_groupLeave a WhatsApp group
logout_instanceLogout an instance (disconnects the WhatsApp session without deleting the instance)
mark_message_as_readMark one or more messages in a chat as read
restart_instanceRestart an instance
send_documentwrite actionSend a document via WhatsApp
send_imagewrite actionSend an image message via WhatsApp
send_pollwrite actionSend a poll message via WhatsApp
send_textwrite actionSend a text message via WhatsApp
set_presenceSet online/offline presence for an instance
update_group_participantswrite actionAdd, remove, promote, or demote participants in a WhatsApp group
update_profilewrite actionUpdate instance profile (name, status text, or picture)
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 29 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Evolution API compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 25
- the typical server has 7
- Tools that change things
- 40%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 271
- more than 95% of 28,688 servers
What its tools let an agent do: 11 read · 2 create · 4 change · 3 delete · 4 send or post · 1 run or deploy
Install Evolution API in Claude Code, Cursor or VS Code
Runs npx -y @codespar/mcp-evolution-api on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-evolution-api -- npx -y @codespar/mcp-evolution-api
What the publisher says
From the Evolution API repository's README, as published. We do not edit it. Read it on GitHub
MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute
The Problem
AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).
Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.
MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.
The Solution
Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.
🛒 Customer places order
→ 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
→ 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
→ 📦 Agent generates shipping label (Melhor Envio / Skydropx)
→ 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
→ 📊 Agent records in ERP (Omie / Bling / Tiny)
→ 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)Six systems. Zero human intervention. One agent.
Agentic Payment Protocols
Four servers for the emerging agentic payment stack:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Evolution API: common questions
- Is Evolution API MCP server safe?
- Mostly: it is graded B (82/100). Read the Evolution API safety report
- How do I install Evolution API?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Evolution API need an API key?
- Yes. The registry entry asks for
EVOLUTION_API_KEY. - Is Evolution API maintained?
- The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.
- How does Evolution API compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 25 (the typical server has 7); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.