Zapcore MCP Server

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.

claude mcp add zapcore-mcp -- npx -y zapcore-mcp

{
  "mcpServers": {
    "zapcore-mcp": {
      "args": [
        "-y",
        "zapcore-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.zapcore-mcp]
command = "npx"
args = ["-y", "zapcore-mcp"]

{
  "mcpServers": {
    "zapcore-mcp": {
      "args": [
        "-y",
        "zapcore-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "zapcore-mcp": {
      "args": [
        "-y",
        "zapcore-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: ZAPCORE_TOKEN (Token da instância zapCore (header `token` da API v2).), 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.). The author declared them in the registry entry; get the values from the project itself.