Mcp Zenvia
Wire Zenvia SMS, WhatsApp, and RCS into your coding agent so you can send messages and manage templates without leaving the IDE.
Overview
io.github.codespar/mcp-zenvia is a Build-phase MCP server that lets coding agents send SMS, WhatsApp, and RCS and manage Zenvia templates via stdio.
What is this MCP server?
- Stdio MCP server (@codespar/mcp-zenvia) with ZENVIA_API_TOKEN authentication
- Send and orchestrate SMS, WhatsApp, and RCS from agent-driven workflows
- Work with Zenvia message templates from Claude Code, Cursor, or Codex
- Part of codespar/mcp-dev-brasil communication packages for Brazil-focused stacks
- npm-packaged v0.1.2—fits local agent configs without a separate HTTP bridge
- npm package @codespar/mcp-zenvia at version 0.1.2
- stdio transport; single required secret env var ZENVIA_API_TOKEN
- Supports SMS, WhatsApp, and RCS messaging channels per server description
Community signal: 252 GitHub stars.
What problem does it solve?
You want agent-assisted messaging in Zenvia but keep copying API docs and tokens into chat instead of a stable tool surface.
Who is it for?
Indie builders wiring Brazilian SMS/WhatsApp/RCS into a product or internal agent workflows with Zenvia already chosen.
Skip if: Teams that only need email, use a different CPaaS, or cannot expose a messaging API token to a local MCP process.
What do I get? / Deliverables
After you register the server with ZENVIA_API_TOKEN, your agent can invoke Zenvia messaging and template operations as structured MCP tools during builds and lifecycle tweaks.
- Stdio MCP bridge to Zenvia SMS, WhatsApp, and RCS APIs
- Agent-callable access to Zenvia messaging and template workflows
- Versioned npm package (0.1.2) aligned with MCP server schema 2025-12-11
Recommended MCP Servers
Journey fit
MCP servers that connect external APIs belong on the Build shelf under integrations—the moment solo builders hook product comms into their stack. Zenvia is a third-party messaging API; registering this server is classic integration work alongside backend and agent tooling.
How it compares
Zenvia MCP integration for CPaaS channels, not an agent skill that teaches copywriting or campaign strategy.
Common Questions / FAQ
Who is io.github.codespar/mcp-zenvia for?
Solo and indie developers using Claude Code, Cursor, or Codex who already use Zenvia and want SMS, WhatsApp, and RCS available as MCP tools.
When should I use io.github.codespar/mcp-zenvia?
Use it during Build integrations or Grow lifecycle work when you need your agent to send messages or manage Zenvia templates without manual API calls.
How do I add io.github.codespar/mcp-zenvia to my agent?
Install @codespar/mcp-zenvia from npm, set the required ZENVIA_API_TOKEN environment variable, and add the stdio server entry to your Claude or Cursor MCP configuration.