Cloudflare MCP Server

About

Cloudflare ships two different things under this name. The mcp-server-cloudflare repo provides 16 remote, domain-specific MCP servers rather than one monolith — Documentation, Workers Bindings (storage/AI/compute primitives), Workers Builds, Observability (logs/analytics), Container sandboxes, Browser Rendering (fetch pages, convert to markdown, screenshots), Logpush health, AI Gateway (prompt/response search), AI Search, Audit Logs, DNS Analytics, Digital Experience Monitoring, Cloudflare One CASB, Radar, GraphQL analytics and the Agents SDK docs server, each on its own `*.mcp.cloudflare.com/mcp` hostname. Separately, the Cloudflare API MCP server at mcp.cloudflare.com/mcp (repo: cloudflare/mcp) exposes the whole 2,500+ endpoint Cloudflare API through just two tools, `search` and `execute`, using the Code Mode pattern — model-written JavaScript runs in an isolated Dynamic Worker, costing ~1,000 tokens of context against the ~1.17M an equivalent native-tool server would need. Pick a domain server when you want a readable, curated tool list for one product area; pick the API server for breadth or for endpoints nobody wrote a tool for. All endpoints are Streamable HTTP on `/mcp` and support the MCP 2026-07-28 spec; the historical `/sse` URLs remain as aliases for the same Streamable HTTP handler but no longer serve the deprecated HTTP+SSE transport, so clients pinned to SSE must switch. Auth is OAuth on connect, or a scoped Cloudflare API token as a bearer header for CI. Clients without native remote-MCP support bridge via `npx mcp-remote https://<subdomain>.mcp.cloudflare.com/mcp`.

Installation

claude mcp add --transport http cloudflare-api https://mcp.cloudflare.com/mcp

Connecting to Cloudflare MCP

1. 1.The API server — one URL, OAuth on first use

   There is nothing to install and no package to pin. Add the URL, and on connect you are redirected to Cloudflare to authorize and choose which permissions the agent gets. Use the /mcp Streamable HTTP endpoint for anything new.

   json

   {
     "mcpServers": {
       "cloudflare-api": {
         "url": "https://mcp.cloudflare.com/mcp"
       }
     }
   }

2. 2.A product-specific server — same shape, different hostname

   Every one of the sixteen follows the pattern https://<subdomain>.mcp.cloudflare.com/mcp. Nothing stops you adding several at once; each authorizes separately, and each adds its own tools to the context, which is the cost you are trading against the API server's two.

   shell

   claude mcp add --transport http cloudflare-observability https://observability.mcp.cloudflare.com/mcp
   claude mcp add --transport http cloudflare-bindings https://bindings.mcp.cloudflare.com/mcp

3. 3.Clients that cannot speak remote MCP

   Older clients that only launch local processes need a bridge. mcp-remote runs as a stdio child and proxies to the remote endpoint, handling the OAuth browser flow on your behalf. Swap the subdomain for whichever server you want.

   json

   {
     "mcpServers": {
       "cloudflare": {
         "command": "npx",
         "args": ["mcp-remote", "https://bindings.mcp.cloudflare.com/mcp"]
       }
     }
   }

4. 4.CI, where no browser exists

   OAuth is not an option in automation. Create a Cloudflare API token scoped to what the job needs and send it as a bearer token in the Authorization header — both user tokens and account tokens are accepted. This is the one place a long-lived credential belongs.

   http

   Authorization: Bearer <cloudflare-api-token>

5. 5.Or install the skills plugin instead of wiring servers by hand

   cloudflare/skills bundles the MCP servers together with contextual skills and slash commands for building on Cloudflare. It works with any agent supporting the Agent Skills standard — Claude Code, OpenCode, OpenAI Codex and Pi. Cursor takes it from its marketplace, or via Settings → Rules → Add Rule → Remote Rule (GitHub) with cloudflare/skills.

   shell

   # Claude Code
   /plugin marketplace add cloudflare/skills
   
   # any agent, via the skills CLI
   npx skills add https://github.com/cloudflare/skills

Why the API server shows only two tools

Code Mode replaces a tool-per-endpoint listing with a sandbox the model writes JavaScript into. Cloudflare publishes the arithmetic: 2,594 endpoints as native MCP tools costs roughly 1,170,000 tokens of context with full schemas, or ~244,000 with required parameters only. Code Mode costs about 1,000 tokens, and stays there no matter how many endpoints exist — more than the entire context window of most models, reduced to a rounding error.

What people use it for

Which one should you use?

The useful comparison here is mostly internal — Cloudflare against itself.

Categories

Works With

Frequently Asked Questions

Related Guides