
Mcp Zenvia
io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026
MCP server for Zenvia — SMS, WhatsApp, RCS, Email, Voice, Facebook messaging, templates and reports
Overview
Local MCP server for Zenvia that lets an assistant send SMS, WhatsApp, RCS, email, voice and Facebook messages and manage contacts, templates and reports.
- What you can do
- Send messages over SMS, WhatsApp, RCS, email, voice (TTS or audio URL) and Facebook Messenger, including pre-approved WhatsApp templates and opt-out registration for phone numbers. Check delivery status of a sent message and list available channels. Create, list and delete webhook subscriptions for message events. List, create and delete contacts in the contact base. List approved templates and fetch message report entries for a date range.
- When to use it
- Useful when you want an assistant to drive Zenvia multichannel messaging from a desktop client: sending customer notifications, checking delivery, managing contacts and templates, or pulling message reports without leaving the chat.
- Requirements
- Runs locally via npx from the npm package @codespar/mcp-zenvia (Node.js required) and is configured in a desktop client such as Claude Desktop, Claude Code, Cursor or VS Code. Needs a Zenvia account and an API token supplied in the ZENVIA_API_TOKEN environment variable; network access to the Zenvia API. A sandbox is available from the Zenvia dashboard for testing.
Installation
In SourceWeft
- Open Mcp Zenvia in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@codespar/mcp-zenvia
MCP server for Zenvia — multichannel messaging (SMS, WhatsApp, RCS)
Quick Start
Claude Desktop
Add to ~/.config/claude/claude_desktop_config.json:
Claude Code
Cursor / VS Code
Add to .cursor/mcp.json or .vscode/mcp.json:
Tools (18)
Authentication
Zenvia uses an API token passed via the X-API-TOKEN header.
Sandbox / Testing
Zenvia provides a sandbox via the dashboard for testing messages.
Get your credentials
- Go to Zenvia
- Create an account
- Get your API token from the dashboard
- Set the
ZENVIA_API_TOKENenvironment variable
Environment Variables
Roadmap
v0.2 (planned)
create_contact_list— Create a contact list for campaignssend_batch— Send batch messages to a contact listget_report— Get message delivery reportscreate_flow— Create a conversational flowlist_templates— List approved message templates
v0.3 (planned)
chatbot_integration— Integrate with Zenvia chatbot builderanalytics_dashboard— Get channel analytics and metrics
Want to contribute? Open a PR or request a tool.
Links
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Source: packages/communication/zenvia/README.md at commit d0a519a
Tools
0Version history
1- v0.2.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts