io.github.adeiltonpessini/zapcore-mcp

io.github.adeiltonpessini/zapcore-mcp

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

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "zapcore-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapcore-mcp@0.1.1"
      ],
      "env": {
        "ZAPCORE_TOKEN": "<your ZAPCORE_TOKEN>",
        "ZAPCORE_URL": "https://zapcore.barberai.online",
        "ZAPCORE_MCP_WRITE": "0",
        "ZAPCORE_MCP_TIMEOUT_MS": "30000",
        "ZAPCORE_MCP_DOWNLOAD_DIR": "<TEMP>/zapcore-mcp",
        "ZAPCORE_CF_ACCESS_CLIENT_ID": "<your ZAPCORE_CF_ACCESS_CLIENT_ID>",
        "ZAPCORE_CF_ACCESS_CLIENT_SECRET": "<your ZAPCORE_CF_ACCESS_CLIENT_SECRET>"
      }
    }
  }
}
Environment variables
  • ZAPCORE_TOKENrequiredsecretToken da instância zapCore (header `token` da API v2).
  • ZAPCORE_URLBase 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_TIMEOUT_MSTimeout por chamada HTTP à API do zapCore, em milissegundos.
  • ZAPCORE_MCP_DOWNLOAD_DIRDiretório onde `zap_media_download` grava o arquivo baixado.
  • ZAPCORE_CF_ACCESS_CLIENT_IDsecretClient 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_SECRETsecretClient secret do service token do Cloudflare Access. Par de ZAPCORE_CF_ACCESS_CLIENT_ID.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.1.1
Registry
active
Published
9/14/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that io.github.adeiltonpessini/zapcore-mcp is listed here — it’s also the link we check for a free listing.

io.github.adeiltonpessini/zapcore-mcp — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-adeiltonpessini-zapcore-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="io.github.adeiltonpessini/zapcore-mcp — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![io.github.adeiltonpessini/zapcore-mcp — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-adeiltonpessini-zapcore-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.