MCP Server Cloudflare

What cloudflare/mcp-server-cloudflare MCP server does

The cloudflare/mcp-server-cloudflare MCP server provides a collection of domain-specific remote MCP servers for Cloudflare. These servers let an MCP client read account configuration, process account data, make suggestions, and apply suggested changes where the selected product supports those operations.

Available areas include Workers bindings for storage, AI, and compute primitives; Workers Builds management and insights; application observability; browser page fetching, Markdown conversion, and screenshots; Logpush job health; AI Gateway logs; AutoRAG instances; audit logs; DNS analytics; Digital Experience Monitoring; Cloudflare One CASB; Radar; the Cloudflare Blog; and a demonstration server. The repository description also identifies Workers, KV, R2, and D1 among the supported Cloudflare services.

Use these servers when a workflow is centered on one Cloudflare product area and benefits from curated, typed tools. Cloudflare’s separate Code Mode server is intended for broader API coverage through code execution.

How it works

Each domain-specific server exposes a stateless Streamable HTTP handler. The recommended endpoint path is /mcp. The repository also exposes /sse as a compatibility alias, but it does not use the deprecated HTTP-plus-SSE transport.

A legacy SSE GET /sse request returns HTTP 410 with migration guidance: configure the existing URL for Streamable HTTP or move to /mcp. Modern 2026 requests and stateless 2025 requests use the same request-scoped implementation without an MCP protocol session. OAuth, credentials, account selection, application caches, and product Durable Objects remain application or security state when needed.

The cloudflare/mcp-server-cloudflare MCP server is accessed remotely, so an MCP client with remote-server support can connect directly to one of the published URLs. Cloudflare AI Playground also accepts these server URLs.

Setup and configuration

Choose the endpoint that matches the Cloudflare area you need and add that URL to an MCP client capable of remote connections. Examples include Cursor and Claude. The published endpoints include https://bindings.mcp.cloudflare.com/mcp for Workers Bindings, https://observability.mcp.cloudflare.com/mcp for observability, https://browser.mcp.cloudflare.com/mcp for Browser Run, and other product-specific hosts listed by the project.

Operations that access a Cloudflare account require an API token with the permissions needed by the selected server. When using a server through the OpenAI Responses API, provide an API token with the scopes required for that server. The repository gives Browser Run as an example and directs users to create the token in the Cloudflare dashboard.

Tools and capabilities

• Query and manage Workers Builds.
• Work with Workers storage, AI, and compute bindings.
• Inspect logs and analytics for application debugging.
• Fetch web pages, convert them to Markdown, and take screenshots.
• Query audit logs, DNS analytics, AutoRAG, Radar, or AI Gateway data.
• Review SaaS security configuration through Cloudflare One CASB.
• Search and read Cloudflare Blog content.

Limitations and notes

Some capabilities may require a paid Cloudflare Workers plan and the appropriate account subscription. Permissions also depend on the API token scopes configured for the selected server.

Long chains of tool calls, especially with observability, can exceed Claude’s context limit and interrupt a response. Concise requests and splitting multi-tool work into smaller calls can reduce this risk.

The repository contains domain-specific servers, while the recommended Code Mode server is maintained separately at cloudflare/mcp. The cloudflare/mcp-server-cloudflare MCP server therefore may not be the best choice when one workflow needs broad coverage across many Cloudflare APIs.