Skip to main content
Glama
zernio-mcp-cloudflare

zernio-mcp-cloudflare

by liamakeup

zernio-mcp-cloudflare (liamakeup-mcp-portal v2.0)

Multi-Server MCP Portal & Multi-Tool Batch Executor in front of the Zernio MCP server (and any additional upstream MCP servers), running as a stateless Cloudflare Worker. One endpoint for every agent (Antigravity, Claude Code, Codex, Cursor, Cloudflare Agents, n8n…), with upstream API keys kept as Worker secrets instead of in each client's config.

  • Endpoint (Full Mode): https://api.liamakeup.workers.dev/mcp

  • Endpoint (Compact Mode — ~90% fewer tool tokens): https://api.liamakeup.workers.dev/mcp?mode=compact

  • Health: https://api.liamakeup.workers.dev/health

Portal Capabilities (v2.0)

  1. Multi-Server Aggregation (UPSTREAM_SERVERS):

    • Primary server zernio (https://mcp.zernio.com/mcp) exposes unprefixed tool names (and also accepts zernio__<tool>) for 100% backward compatibility.

    • Additional upstream MCP servers configured in UPSTREAM_SERVERS JSON ([{"id":"crm","name":"CRM MCP","url":"https://...","token":"..."}]) have their tools exposed as <id>__<toolName> in tools/list and routed automatically on tools/call.

  2. Multi-Tool Batch & Chain Execution (portal_batch_call):

    • Execute up to 10 MCP tool calls in a single round-trip across one or multiple servers.

    • mode: "parallel" runs all calls concurrently (Promise.all).

    • mode: "sequential" runs calls in order and interpolates previous step JSON outputs via {{$steps.0.field.path}} (with optional stopOnError: true).

  3. Compact Discovery Mode (?mode=compact or header x-portal-mode: compact):

    • Filters tools/list down to zernio_overview, search_tools, call_tool, portal_list_servers, and portal_batch_call.

Related MCP server: remote-mcp-server-authless

Cloudflare Free plan

  • Plain fetch Worker: no Durable Objects, KV, D1 or other paid bindings.

  • ~2.5 KiB gzipped, ~3 ms startup; the Worker only relays I/O, well under the 10 ms CPU limit.

  • Free plan quota: 100,000 requests/day on *.workers.dev.

How requests are authorized

The Worker fails closed:

Caller sends

Result

x-gateway-token: <GATEWAY_TOKEN> (or Authorization: Bearer <GATEWAY_TOKEN>)

Uses the Worker's ZERNIO_API_KEY

Gateway token and its own key in x-api-key

Uses the caller's key

Nothing, or a wrong gateway token

401, no upstream call

  • Without GATEWAY_TOKEN configured, the Worker never spends its own key; callers must bring their own key via x-api-key or Authorization: Bearer.

  • Tokens are accepted only in headers, never in the URL, so they stay out of Workers logs.

  • Prefer x-gateway-token over Authorization: some clients treat Authorization as an OAuth slot.

Behaviour

  • POST /mcp only. Every JSON-RPC request (including initialize) is relayed to https://mcp.zernio.com/mcp, so capabilities, tools and Mcp-Session-Id come from upstream.

  • Responses stream back unbuffered (text/event-stream or JSON).

  • Notifications get 202 Accepted immediately and are relayed in the background (ctx.waitUntil).

  • Batch requests return -32600 (JSON-RPC batching was removed from MCP in 2025-06-18).

  • Upstream calls that send no response headers within 60 s return 504; streams already under way are not cut; a rejected Zernio key returns the upstream 401/403 with code -32001.

Deploy

npm install
npx wrangler secret put ZERNIO_API_KEY
openssl rand -base64 32 | tr '+/' '-_' | tr -d '=' | npx wrangler secret put GATEWAY_TOKEN
npm run deploy
curl https://api.liamakeup.workers.dev/health   # requiresGatewayToken: true

Connect agents

Replace <GATEWAY_TOKEN> with the value you stored. Ready-made snippets are in clients/.

# Antigravity
agy mcp add --header "x-gateway-token: <GATEWAY_TOKEN>" zernio https://api.liamakeup.workers.dev/mcp

# Claude Code
claude mcp add --transport http zernio https://api.liamakeup.workers.dev/mcp -H "x-gateway-token: <GATEWAY_TOKEN>"
# Codex: ~/.codex/config.toml
[mcp_servers.zernio]
url = "https://api.liamakeup.workers.dev/mcp"
http_headers = { "x-gateway-token" = "<GATEWAY_TOKEN>" }
// Cursor: .cursor/mcp.json (keep this file out of git)
{ "mcpServers": { "zernio": { "url": "https://api.liamakeup.workers.dev/mcp",
  "headers": { "x-gateway-token": "<GATEWAY_TOKEN>" } } } }

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers