Mcp Evolution Api
Connect Evolution API WhatsApp instances, contacts, and messaging to your agent so you can script support and outbound flows from the IDE.
Overview
io.github.codespar/mcp-evolution-api is a MCP server for the Build phase that lets agents control Evolution API WhatsApp instances, contacts, and messaging.
What is this MCP server?
- @codespar/mcp-evolution-api v0.1.2 stdio MCP for Evolution API
- Server description covers WhatsApp messaging, multi-instance management, and contacts
- Requires EVOLUTION_API_KEY environment variable for authenticated calls
- Lives in codespar mcp-dev-brasil communication/evolution-api package
- Suites agent workflows for support bots, onboarding nudges, and ops alerts over WhatsApp
- Package version 0.1.2
- Stdio transport only in published server manifest
- 1 required secret EVOLUTION_API_KEY
Community signal: 252 GitHub stars.
What problem does it solve?
Maintaining WhatsApp automations with Evolution means juggling REST docs and instance keys while your agent cannot safely send or list contacts.
Who is it for?
Builders who self-host Evolution API and want IDE agents to help with WhatsApp instance and messaging integration code.
Skip if: Teams without an Evolution deployment, brands that require only official Cloud API with no self-hosted stack, or non-technical marketers avoiding API setup.
What do I get? / Deliverables
Once EVOLUTION_API_KEY is set, your agent can use Evolution MCP tools while you build notifications, support bots, and instance ops scripts.
- MCP-registered Evolution API tool surface for agents
- Faster implementation of send, contact, and instance workflows in code
- Documented local MCP entry for repeatable WhatsApp integration sessions
Recommended MCP Servers
Journey fit
WhatsApp automation is usually implemented when you integrate customer comms into the product—not in pure research phases. Evolution API is an external messaging backend; integrations is the canonical MCP shelf for instance and send-message tooling.
How it compares
Evolution API MCP connector for developers, not a WhatsApp CRM SaaS or no-code broadcast UI.
Common Questions / FAQ
Who is io.github.codespar/mcp-evolution-api for?
Indie developers and small teams running Evolution API for WhatsApp who use MCP hosts to speed up messaging and instance management code.
When should I use io.github.codespar/mcp-evolution-api?
Use it in Build while integrating WhatsApp notifications or support—or in Grow when extending lifecycle automations—after your Evolution server and API key exist.
How do I add io.github.codespar/mcp-evolution-api to my agent?
Install @codespar/mcp-evolution-api from npm, configure EVOLUTION_API_KEY in the MCP env section, add the stdio server to your agent config, and restart.