Connect to Cloudflare’s recommended Code Mode first, and stay read-only

Who it is for

If you already have a Cloudflare account and want an MCP client such as Cursor or Claude to finish in-account tasks in natural language, this repo matches. Officially there are multiple MCP servers here for connecting Cloudflare services.

The official recommendation is the Code Mode server, for people who need code execution and broad Cloudflare API access. The domain-specific servers in this repo fit people who want only one product direction with typed tools. Do not attach many servers at once the first time.

The current excerpt does not give concrete tool function names. Code Mode is written as reaching a wide API through code execution, so it is not a zero-risk read: it may change account resources. The documentation server fetches Cloudflare’s latest reference information.

First try in 3 minutes

First confirm you can sign in to your own Cloudflare account. The official recommended main path is to point a Streamable HTTP MCP client at the Code Mode address, not to fill in a pile of domain-specific entries beside it:

https://mcp.cloudflare.com/mcp 

That address is https://mcp.cloudflare.com/mcp . The excerpt states every service exposes a stateless Streamable HTTP handler at /mcp and /sse; /sse is only a URL-compatibility alias, not the deprecated HTTP+SSE transport. Do not expect the old GET /sse: the excerpt states leftover GET /sse returns 410 Gone and tells you to switch to Streamable HTTP or to the recommended /mcp.

After connecting, the first time ask only a read-only question, for example account or config information you already intended to check. Code Mode will reach the API through code execution. If the request might create, change, or delete resources, stop and confirm the side effects before running. The excerpt does not write tool names or revoke steps.

The success signal is that the client connects to https://mcp.cloudflare.com/mcp and returns a read-only result, not 410, and not still using old GET /sse. This still goes out to the network and into your Cloudflare account; do not treat it as no network or no privacy boundary.

Use cases

Case 1: Do one cross-API read-only query with Code Mode. The excerpt states Code Mode fits broad Cloudflare API access through code execution; the recommended entry is https://mcp.cloudflare.com/mcp , and the code is at https://github.com/cloudflare/mcp . Confirm the question is a read first. On success you see a result for that question. The concrete execution environment and tool names are not in the current excerpt.

Case 2: You only want the latest docs, not broad code execution. The excerpt states the Documentation server is used to Get up-to-date reference information on Cloudflare; the address is https://docs.mcp.cloudflare.com/mcp . On success you should get documentation reference, not a write against the account. The Workers Bindings server is written as building Workers with storage, AI, and compute primitives; the address is https://bindings.mcp.cloudflare.com/mcp ; that is another product-direction capability and need not be attached the first time.

These two cases correspond to “broad API code execution” and “read-only docs.” Do not merge them into one unconfirmed tool call.

Limits

The main path is https://mcp.cloudflare.com/mcp . Domain-specific services in this repo use *.mcp.cloudflare.com. Transport is uniformly /mcp and /sse as an alias. Leftover GET /sse returns 410.

The official repo is https://github.com/cloudflare/mcp-server-cloudflare . The excerpt does not give OAuth commands, a full product-server list, or a revoke path. Do not invent missing hostnames and tool names. Any code execution that would change Cloudflare resources must be confirmed first.