io.github.adeiltonpessini/zapcore-mcp vs io.github.codespar/mcp-z-api
io.github.adeiltonpessini/zapcore-mcp is an MCP server published by adeiltonpessini. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.codespar/mcp-z-api is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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-z-api | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 109 Downloads/week (npm): 20 Not marked · First seen |
Listed Version: 0.2.2 Downloads/month (npm): 85 Downloads/week (npm): 8 Forks (GitHub): 52 Stars (GitHub): 274 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.adeiltonpessini/zapcore-mcp | io.github.codespar/mcp-z-api |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 274 |
| Forks (GitHub) (differs) | No figure on GitHub | 52 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (zapcore-mcp) | On your machine (@codespar/mcp-z-api) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 3 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/adeiltonpessini/zapcore | github.com/codespar/mcp-dev-latam |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.adeiltonpessini/zapcore-mcp
Servidor MCP do zapCore (WhatsApp): leitura sempre, envio atrás de flag e allowlist de destino.
io.github.codespar/mcp-z-api
MCP server for Z-API — WhatsApp messaging, contacts, media
How to run each
io.github.adeiltonpessini/zapcore-mcp As a local MCP server: npm package
claude mcp add --env "ZAPCORE_CF_ACCESS_CLIENT_ID=<YOUR_ZAPCORE_CF_ACCESS_CLIENT_ID>" --env "ZAPCORE_CF_ACCESS_CLIENT_SECRET=<YOUR_ZAPCORE_CF_ACCESS_CLIENT_SECRET>" --env "ZAPCORE_TOKEN=<YOUR_ZAPCORE_TOKEN>" --transport stdio zapcore-mcp -- npx -y zapcore-mcpRequires: ZAPCORE_CF_ACCESS_CLIENT_ID (secret), ZAPCORE_CF_ACCESS_CLIENT_SECRET (secret), ZAPCORE_TOKEN (secret)
io.github.codespar/mcp-z-api As a local MCP server: npm package
claude mcp add --env "ZAPI_TOKEN=<YOUR_ZAPI_TOKEN>" --transport stdio mcp-z-api -- npx -y @codespar/mcp-z-apiRequires: ZAPI_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.adeiltonpessini/zapcore-mcp asks for
ZAPCORE_CF_ACCESS_CLIENT_ID (secret)ZAPCORE_CF_ACCESS_CLIENT_SECRET (secret)ZAPCORE_MCP_ALLOWZAPCORE_MCP_DOWNLOAD_DIRZAPCORE_MCP_TIMEOUT_MSZAPCORE_MCP_WRITEZAPCORE_TOKEN (secret)ZAPCORE_URL
Only io.github.codespar/mcp-z-api asks for
ZAPI_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.adeiltonpessini/zapcore-mcp · What it can do: io.github.codespar/mcp-z-api · 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.