mcp server · cloudflare

Cloudflare MCP server with cross-account routing.

Manage many Cloudflare accounts from one MCP connection. Built for agencies, consultancies, and platforms that operate dozens of client accounts. Vault-stored scoped API tokens, default read-only, audit log per call. wmcp.sh is not affiliated with Cloudflare Inc.

Connect at https://wmcp.sh/mcp/cloudflare · register many accounts per connection · default read-only

Why route through wmcp.sh instead of running the official server.

Cloudflare ships an excellent official MCP server at cloudflare/mcp-server-cloudflare — actively developed with sub-servers for Workers, R2, DNS, Browser Rendering, AutoRAG and more. For a single developer with one Cloudflare account, that's the right answer.

The gap is multi-account. Agencies, consultancies, and platforms that operate Cloudflare on behalf of multiple clients end up running N copies of the official server — one per client account — and switching between them in the IDE. The agent has no way to reason about "do this on client A's account, that on client B's".

wmcp.sh adds the multi-account layer: register many Cloudflare accounts (each with its own scoped API token) under one connection profile. Every tool call accepts an account_id parameter, and wmcp.sh routes to the matching token. One MCP endpoint, N client accounts, default read-only, full audit log.

Cloudflare tools, MCP-shaped.

Ten read-focused tools spanning zones, DNS, Workers, R2, and analytics.

Node — list zones across all client accounts.

// npm i @modelcontextprotocol/sdk @anthropic-ai/sdk
import Anthropic from "@anthropic-ai/sdk";
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const WMCP = "https://wmcp.sh/mcp/cloudflare";
const token = process.env.WMCP_TOKEN!;

const mcp = new Client({ name: "cf-agency", version: "1.0" });
await mcp.connect(new StreamableHTTPClientTransport(new URL(WMCP), {
  requestInit: { headers: { Authorization: `Bearer ${token}` } }
}));

const { tools } = await mcp.listTools();
const anthropic = new Anthropic();

const msg = await anthropic.messages.create({
  model: "claude-opus-4-5",
  max_tokens: 2048,
  tools: tools.map(t => ({ name: t.name, description: t.description, input_schema: t.inputSchema })),
  messages: [{ role: "user", content: "For every account I have, list zones with their plan and SSL mode." }],
});
// agent calls list_accounts first, then loops list_zones per account_id

Official Cloudflare MCP server vs wmcp.sh-routed.

Capabilitycloudflare/mcp-server-cloudflarewmcp.sh-routed
Single-account flowExcellentEquivalent
Cross-account routingRun one server per accountN accounts in one connection, account_id per call
API token storageOAuth / env varEncrypted vault, per-account namespacing
Default modeRead + writeRead-only; writes opt-in
Audit logCloudflare-sidewmcp.sh per-call + Cloudflare-side preserved
Worker / R2 / KV / D1 coverageFullRead-only subset, common 80%
TransportStreamable HTTP + OAuthStreamable HTTP + OAuth 2.1

Common questions.

Is there an official Cloudflare MCP server?
Yes — cloudflare/mcp-server-cloudflare, actively developed with multiple sub-servers. For a single-account dev that's the right answer. wmcp.sh is not affiliated with Cloudflare and offers a hosted alternative with cross-account routing for agencies.
What's cross-account routing?
Register multiple Cloudflare accounts in one wmcp.sh connection profile. Tools take an account_id parameter, and wmcp.sh routes to the right scoped API token. One endpoint, many client accounts.
Where are tokens stored?
Encrypted per-user vault, namespaced per account id. Decrypted in memory per request, never logged.
Can the agent deploy Workers?
Write tools (deploy Worker, edit DNS, create R2, purge cache) are opt-in per connection. Default is read-only.
Pricing?
Free 100 reads/day anonymous. Managed Starter $499 one-time, Managed Retainer $999/mo, Enterprise $4,999+/mo. See /managed.

Need this in production?

Production multi-account Cloudflare MCP: scoped API tokens per client with read-only or fine-grained write perms, audit retention, SSO, per-account billing tagging in your dashboard. Starter $499 one-time, Managed Retainer $999/mo, Enterprise $4,999+/mo.

→ Managed setup ($499) Submit your MCP server (free)