An official Cloudflare collection of remote MCP servers split by product domain, each served over Streamable HTTP with OAuth or API-token authentication — well suited to teams already on Cloudflare who want natural-language account management, provided API tokens are scoped with least privilege given the real account-level permissions involved.
An official Cloudflare-maintained repository providing a set of domain-specific remote MCP servers (Documentation, Workers Bindings, Workers Builds, Observability, sandbox Containers, Browser Rendering, Logpush, AI Gateway, AutoRAG, Audit Logs, DNS Analytics, DEX, CASB, Radar, Blog, Demo Day, and more). Each server exposes the same stateless request handler over Streamable HTTP at its own *.mcp.cloudflare.com/mcp subdomain; the /sse path remains only as a URL compatibility alias and does not use the deprecated HTTP+SSE transport. Any MCP client with remote-server support (e.g. Cursor, Claude, Cloudflare AI Playground) can connect directly to these URLs to read account configuration, process information, and make suggested changes across Cloudflare's application, security, and performance products.
In an MCP client that supports remote servers (e.g. Cursor, Claude Desktop, or Cloudflare AI Playground), add the URL for the desired product-domain server (e.g. https://docs.mcp.cloudflare.com/mcp, https://bindings.mcp.cloudflare.com/mcp) — no local installation is required. Most servers support OAuth login; alternatively, supply a Cloudflare API key (user- or account-owned token) as a Bearer token in the Authorization header. To use a server via the OpenAI Responses API, create a Cloudflare API token scoped with the permissions that specific server requires.