io.github.codespar/mcp-zenvia vs SMS en Masse
io.github.codespar/mcp-zenvia is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). SMS en Masse is an MCP server published by git-acet. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.codespar/mcp-zenvia |  SMS en Masse |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2 Downloads/month (npm): 105 Downloads/week (npm): 22 Forks (GitHub): 51 Stars (GitHub): 273 Not marked · First seen |
Listed Version: 0.9.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.codespar/mcp-zenvia | SMS en Masse |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 273 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 51 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@codespar/mcp-zenvia) | Remote server (www.smsenmasse.fr/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/codespar/mcp-dev-latam | github.com/git-acet/smsenmasse-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 308 (2 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.codespar/mcp-zenvia
MCP server for Zenvia — SMS, WhatsApp, RCS, Email, Voice, Facebook messaging, templates and reports
SMS en Masse
Envoyez des SMS et gérez vos campagnes directement depuis vos agents IA.
How to run each
io.github.codespar/mcp-zenvia As a local MCP server: npm package
claude mcp add --env "ZENVIA_API_TOKEN=<YOUR_ZENVIA_API_TOKEN>" --transport stdio mcp-zenvia -- npx -y @codespar/mcp-zenviaRequires: ZENVIA_API_TOKEN (secret)
SMS en Masse As a remote MCP server
claude mcp add --transport http smsenmasse https://www.smsenmasse.fr/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SMS en Masse has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of SMS en Masse publish no settings it asks for, so we do not compare settings.
What it can do: io.github.codespar/mcp-zenvia · What it can do: SMS en Masse · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.