mcpbeat Sign in

Zapcore MCP Server

by adeiltonpessini Your server? Claim it
local only

Zapcore MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 87 installs a week from npm.

Servidor MCP do zapCore (WhatsApp): leitura sempre, envio atrás de flag e allowlist de destino.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 156 · avg 15 · -39% w/w
a month agotoday
87
Installs / week
npm · zapcore-mcp
—
Stars
on GitHub
—
Last commit
5 releases in 90 days
—
License
language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add zapcore-mcp -e 'ZAPCORE_TOKEN=<ZAPCORE_TOKEN>' -- npx -y zapcore-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "zapcore-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapcore-mcp"
      ],
      "env": {
        "ZAPCORE_TOKEN": "<ZAPCORE_TOKEN>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.zapcore-mcp]
command = "npx"
args = ["-y", "zapcore-mcp"]
env = { ZAPCORE_TOKEN = "<ZAPCORE_TOKEN>" }
.cursor/mcp.json
{
  "mcpServers": {
    "zapcore-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapcore-mcp"
      ],
      "env": {
        "ZAPCORE_TOKEN": "<ZAPCORE_TOKEN>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "zapcore-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "zapcore-mcp"
      ],
      "env": {
        "ZAPCORE_TOKEN": "<ZAPCORE_TOKEN>"
      }
    }
  }
}

Put your own value in place of <ZAPCORE_TOKEN> (Token da instância zapCore (header `token` da API v2)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: ZAPCORE_URL (Base da API do zapCore), ZAPCORE_MCP_WRITE (`1`/`true`/`yes` registra as 4 tools de envio. Sem allowlist (ZAPCORE_MCP_ALLOW) o servidor recusa a subir), ZAPCORE_MCP_ALLOW (Destinos autorizados a receber envio: telefones E.164 (só dígitos) separados por vírgula. Obrigatório quando ZAPCORE_MCP_WRITE está ligado), ZAPCORE_MCP_TIMEOUT_MS (Timeout por chamada HTTP à API do zapCore, em milissegundos), ZAPCORE_MCP_DOWNLOAD_DIR (Diretório onde `zap_media_download` grava o arquivo baixado), ZAPCORE_CF_ACCESS_CLIENT_ID (Client ID do service token do Cloudflare Access, se a base estiver atrás do Access. Anda em par com ZAPCORE_CF_ACCESS_CLIENT_SECRET — os dois ou nenhum), ZAPCORE_CF_ACCESS_CLIENT_SECRET (Client secret do service token do Cloudflare Access. Par de ZAPCORE_CF_ACCESS_CLIENT_ID).

Alternatives to Zapcore MCP

same job, measured the same way
Talktoplanb MCP
by jmlee850623

MCP server for TalkToPlanB: list rooms, read & send messages (WhatsApp alternative).

40 installs/wk local only
MCP Z API
by codespar

MCP server for Z-API — WhatsApp messaging, contacts, media

65 installs/wk local only
Guarded WhatsApp
by peter-tnc-453

Security gate for agent-driven WhatsApp: allowlist, secret scan, rate limit, audit log.

99 installs/wk local only
Whatsapp MCP
by meharajm

WhatsApp MCP Server - Human-in-the-loop for AI agents via WhatsApp

184 installs/wk local only
Wagent
by deepa-wagent

WhatsApp MCP server with per-chat permissions. Agents see only chats you allow; sends wait for you.

answering
Seu Rastreio
by rafaelomarques

API pública Seu Rastreio no MCP: rastreio, CEP, pedidos, reversa e WhatsApp.

answering
MCP Zenvia
by codespar

MCP server for Zenvia — SMS, WhatsApp, RCS, Email, Voice, Facebook messaging, templates and reports

63 installs/wk local only
MCP Evolution API
by codespar

MCP server for Evolution API — WhatsApp messaging, instances, contacts

185 installs/wk local only

Zapcore MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Zapcore MCP?
Zapcore MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package zapcore-mcp was installed 87 times last week.
Is Zapcore MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Zapcore MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls zapcore-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Zapcore MCP?
The npm package zapcore-mcp was installed 87 times in the last week. Week over week that is -39%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.