MCP Server Cloudflare

What cloudflare/mcp-server-cloudflare does

cloudflare/mcp-server-cloudflare is a repository of Cloudflare-hosted, domain-specific MCP servers. Rather than presenting one general-purpose interface, it provides separate endpoints for focused tasks such as searching Cloudflare documentation, fetching web pages, running browser actions, starting sandbox environments, and reviewing digital experience data.

The repository also lists older product-focused servers for areas including AI Gateway, audit logs, AutoRAG, DNS analytics, GraphQL analytics, Logpush, observability, Radar, Workers bindings, and Workers Builds. These deprecated services are intended to migrate toward Cloudflare’s recommended API MCP server.

How it works

Every server uses a stateless Streamable HTTP handler at the /mcp path. Requests are handled with a fresh SDK v2 server factory, and modern 2026 requests and stateless 2025 requests use the same request-scoped implementation without an MCP protocol session.

An MCP client connects directly to the relevant remote URL and invokes its tools through natural language. Cloudflare account access, OAuth, credentials, account selection, application caches, and product Durable Objects remain application or security state where a particular service requires them.

The older /sse path is retired. Requests to it return a 410 Gone response that points clients to /mcp.

Setup and configuration

Choose a server URL from the repository’s catalog and add that URL to an MCP client with remote-server support. The listed endpoints include https://docs.mcp.cloudflare.com/mcp for documentation, https://containers.mcp.cloudflare.com/mcp for containers, https://browser.mcp.cloudflare.com/mcp for Browser Run, and https://dex.mcp.cloudflare.com/mcp for Digital Experience Monitoring.

Cloudflare AI Playground can also accept server URLs directly. When using a server through the OpenAI Responses API, provide a Cloudflare API token with the permissions required by that server. For example, the Browser Run server requires an appropriately scoped token created in the Cloudflare dashboard.

Tools and capabilities

The repository includes domain-specific tools for:

• Searching and reading Cloudflare reference documentation
• Fetching web pages, converting them to Markdown, and taking screenshots
• Creating sandbox development environments
• Inspecting critical applications through Digital Experience Monitoring
• Finding SaaS security misconfigurations with Cloudflare One CASB
• Searching and reading Cloudflare Blog content
• Demonstrating a minimal Cloudflare MCP server
• Querying or inspecting older services such as audit logs, DNS analytics, GraphQL data, Radar, and Workers products

These tools are curated and typed for a product area. The separate Cloudflare API MCP server is a better fit when a workflow needs broad coverage across Cloudflare APIs or prefers code execution with a smaller set of general-purpose tools.

Limitations and notes

The repository contains both active domain-specific servers and deprecated endpoints. The catalog recommends migrating deprecated services to https://mcp.cloudflare.com/mcp, maintained in the separate cloudflare/mcp repository.

Tool availability depends on the specific endpoint selected, and account access requires the credentials and permissions appropriate to that Cloudflare service. Clients must use the /mcp endpoint rather than the retired /sse path. Requests that trigger many chained calls, particularly observability workflows, can run into an MCP client’s context-length limit; concise prompts and smaller requests help reduce that risk.