Cloudflare MCP server
The Cloudflare MCP servers give AI agents access to a Cloudflare account through hosted endpoints: read Workers logs and builds, manage bindings, check DNS analytics, search the docs and render web pages.
Connect Cloudflare
Code Mode server, broad API access (recommended by Cloudflare)
https://mcp.cloudflare.com/mcpDocumentation server
https://docs.mcp.cloudflare.com/mcpObservability server, Workers logs and analytics
https://observability.mcp.cloudflare.com/mcpWorkers Bindings server
https://bindings.mcp.cloudflare.com/mcpAdd any of these URLs as a remote server in your client and sign in with Cloudflare when prompted; Cloudflare AI Playground also accepts them. Other servers follow the same pattern, such as builds.mcp.cloudflare.com/mcp and radar.mcp.cloudflare.com/mcp. For OpenAI's Responses API, create an API token in the dashboard with the scopes that server needs.
What the Cloudflare MCP server does
Cloudflare runs a set of hosted MCP servers, one per product area, that connect AI agents to a Cloudflare account. The domain servers in this repo cover Workers Bindings for storage, AI and compute, Workers Builds, Observability for logs and analytics, Browser Run for fetching pages as markdown and screenshots, Logpush, AI Gateway logs, AutoRAG, DNS Analytics, Digital Experience Monitoring, Cloudflare One CASB, Radar and the Cloudflare docs.
Cloudflare recommends a separate Code Mode server at mcp.cloudflare.com/mcp, kept in the cloudflare/mcp repo, for broad access across Cloudflare's APIs through a small set of general tools that write and run code. The domain servers fit better when you work in one product and want typed, guided tools. Agents can read configuration, suggest changes, and make those changes in your account.
Every Cloudflare server speaks Streamable HTTP at a /mcp path, with /sse kept only as an alias; legacy SSE clients get an error. Sign-in is OAuth, or an API token with the right scopes when calling from OpenAI's Responses API. The repo had 4,342 GitHub stars on 2026-10-01 and was pushed the same day.
When to use Cloudflare
- A Worker is throwing errors and you want the agent to read its logs and find the cause.
- You want the agent to set up KV, R2, D1 or AI bindings for a new Worker.
- You need current Cloudflare docs while writing Workers code.
- You want a summary of DNS performance or a Workers Builds failure.
When to pick something else
- Long chained queries in small context windows: Cloudflare warns the Observability server can trigger many tool calls and hit the client's context limit, so keep requests narrow.
- Unreviewed changes: the servers can modify account settings and resources, so confirm each write.
What Cloudflare needs
- A Cloudflare account; a paid Workers plan for some features
- An MCP client that supports remote servers, or an API token for API-based clients
What the Cloudflare MCP server costs
Free to connect and open source under Apache-2.0; some features need a paid Workers plan, and the products the tools use are billed under your Cloudflare plan.
Current prices: github.com . We do not list prices: vendors change them often, so check the publisher's own page.
Other MCP servers for cloud and devops
- AWS: The AWS MCP servers give AI agents access to AWS: a managed AWS MCP Server for API calls and docs, plus more than 50 open-source servers for services like CDK, EKS, Lambda and DynamoDB.
- Kubernetes: The Kubernetes MCP server gives AI agents direct access to Kubernetes and OpenShift clusters: list and edit any resource, read pod logs, exec into pods, view events and install Helm charts.
- Sentry: The Sentry MCP server gives AI coding agents access to your Sentry account: search errors and events, read issue details and stack traces, look at performance data and triage issues while fixing code.
- Terraform: The Terraform MCP server gives AI agents current Terraform Registry data on providers, modules and policies, and with a token manages HCP Terraform and Terraform Enterprise workspaces, runs and plans.