Other · Local MCP server
Zapcore MCP
Servidor MCP do zapCore (WhatsApp): leitura sempre, envio atrás de flag e allowlist de destino.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.adeiltonpessini/zapcore-mcp- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker)
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- adeiltonpessini (GitHub)
- Repository
- github.com/adeiltonpessini/zapcore (folder mcp)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | zapcore-mcp | 0.1.1 | stdio |
| OCI image (Docker) | ghcr.io/adeiltonpessini/zapcore-mcp:0.1.0 | — | stdio |
How to connect Zapcore MCP
Zapcore MCP runs locally from a Node.js package published to the npm registry: zapcore-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y zapcore-mcp@0.1.1. It reads these environment variables: ZAPCORE_TOKEN (required, secret), ZAPCORE_URL, ZAPCORE_MCP_WRITE, ZAPCORE_MCP_ALLOW, ZAPCORE_MCP_TIMEOUT_MS, ZAPCORE_MCP_DOWNLOAD_DIR, ZAPCORE_CF_ACCESS_CLIENT_ID (secret) and ZAPCORE_CF_ACCESS_CLIENT_SECRET (secret); set them in the client's configuration for this server.
Zapcore MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/adeiltonpessini/zapcore-mcp:0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e ZAPCORE_TOKEN -e ZAPCORE_URL -e ZAPCORE_MCP_WRITE -e ZAPCORE_MCP_ALLOW ghcr.io/adeiltonpessini/zapcore-mcp:0.1.0. It reads these environment variables: ZAPCORE_TOKEN (required, secret), ZAPCORE_URL, ZAPCORE_MCP_WRITE and ZAPCORE_MCP_ALLOW; set them in the client's configuration for this server. Required arguments: -i and --rm.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"zapcore-mcp": {
"command": "npx",
"args": [
"-y",
"zapcore-mcp@0.1.1"
],
"env": {
"ZAPCORE_TOKEN": "<secret>",
"ZAPCORE_URL": "<value>",
"ZAPCORE_MCP_WRITE": "<value>",
"ZAPCORE_MCP_ALLOW": "<value>",
"ZAPCORE_MCP_TIMEOUT_MS": "<value>",
"ZAPCORE_MCP_DOWNLOAD_DIR": "<value>",
"ZAPCORE_CF_ACCESS_CLIENT_ID": "<secret>",
"ZAPCORE_CF_ACCESS_CLIENT_SECRET": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ZahabPrice — Live Gold & Silver PricesLive gold & silver prices for 37 countries. Tamara/Tabby installment calculators for Saudi Arabia. | Remote · HTTP |
| ZamboTrust Layer for AI work. Give your AI hands. Every run returns a verifiable receipt. No key needed. | Remote · HTTP |
| ZamboGive your AI hands. One URL. Type a job. Get a receipt. | Remote · HTTP |
| ZaoqiniaoerSend three unrelated real people to a physical address in China and get back what they actually saw. | Remote · HTTP |
| Zavod Stanki CNC CatalogOfficial MCP for Kamensky CNC Plant (Twite): machines, prices, Birzha orders, FAQ, leads. | Remote · HTTP |
| Zcash MCPZcash shielded operations for AI agents. Memo decoding, attestation, proof verification. | Local · stdio |
| zdte.ai SPX Market StructureSPX 0DTE dealer market structure: GEX, walls, gamma flip, regime. Free previews; pay per read. | Remote · HTTP |
| Zelinqa MCPGoal-oriented conversations and next-question selection through the Zelinqa API. | Local · stdio |