Zapcore-mcp Server

Zapcore-mcp is an MCP integration. Servidor MCP do zapCore (WhatsApp): leitura sempre, envio atrás de flag e allowlist de destino.

Packages and local setup

The published npm package is zapcore-mcp, version 0.1.1. Its declared MCP transport is stdio.

The package declares ZAPCORE_TOKEN (required): 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 published oci package is ghcr.io/adeiltonpessini/zapcore-mcp:0.1.0. Its declared MCP transport is stdio.

The package declares ZAPCORE_TOKEN (required): Token da instância zapCore.; ZAPCORE_URL: Base da API do zapCore.; ZAPCORE_MCP_WRITE: Liga as 4 tools de envio; exige ZAPCORE_MCP_ALLOW.; ZAPCORE_MCP_ALLOW: Destinos autorizados, E.164 separados por vírgula..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.