InnerVault

zapcore-mcp

Stale Official MCP Registry, io.github.adeiltonpessini

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

Open the source (opens github.com) https://github.com/adeiltonpessini/zapcore

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: ZAPCORE_CF_ACCESS_CLIENT_ID, ZAPCORE_CF_ACCESS_CLIENT_SECRET, ZAPCORE_TOKEN. Use a key with the least access you can.

What it is

MCP servers from io.github.adeiltonpessini.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

zapcore-mcp@0.1.1

From the server's entry in the official MCP Registry

oci package (stdio)

ghcr.io/adeiltonpessini/zapcore-mcp:0.1.0

From the server's entry in the official MCP Registry

Settings it asks for

  • ZAPCORE_TOKEN secret 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 secret · 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 secret · Client secret do service token do Cloudflare Access. Par de ZAPCORE_CF_ACCESS_CLIENT_ID.
  • ZAPCORE_TOKEN secret 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.

Related

  1. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  2. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  3. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  4. Anthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.

    Hand-checked InnerVault (hand-checked), Anthropic Anthropic documentation

  5. Playwright MCP

    MCP servers

    Lets an agent drive a real browser: open pages, click, fill in forms and read what's on screen.

    Hand-checked InnerVault (hand-checked), Microsoft Apache-2.0

    claude mcp add playwright npx @playwright/mcp@latest
  6. The open standard for connecting AI apps to tools and data. Start here to understand servers, clients, tools and resources.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0 (code); see the project for docs licence