LABSCO SUMMARY
One narrow server per product beats one that does everything.
Connecting only to observability, or only to Radar, keeps the tool list short and typed for the work at hand. When the job genuinely spans products, the Code Mode server is the other shape — broad API coverage through code execution rather than a long menu.
What it is
A catalogue of sixteen managed remote servers Cloudflare runs for its own products, each a URL you connect to individually with curated, typed tools for that area. Broad API coverage is a separate thing: the Code Mode server at mcp.cloudflare.com lives in the cloudflare/mcp repository and works by code execution instead.
What you get
- Application debugging: logs and analytics through the observability server at
observability.mcp.cloudflare.com/mcp, and Logpush job health atlogs.mcp.cloudflare.com/mcp - Workers development: storage, AI and compute primitives at
bindings.mcp.cloudflare.com/mcp, and build insight atbuilds.mcp.cloudflare.com/mcp - Current Cloudflare reference material at
docs.mcp.cloudflare.com/mcp, and posts from the Cloudflare Blog atblog.mcp.cloudflare.com/mcp - A sandbox development environment at
containers.mcp.cloudflare.com/mcp, and page fetching, markdown conversion and screenshots atbrowser.mcp.cloudflare.com/mcp - AI Gateway logs with their prompts and responses at
ai-gateway.mcp.cloudflare.com/mcp, and AutoRAG instances queried atautorag.mcp.cloudflare.com/mcp - Security and compliance: audit logs at
auditlogs.mcp.cloudflare.com/mcp, SaaS misconfiguration findings atcasb.mcp.cloudflare.com/mcp, and per-application insight atdex.mcp.cloudflare.com/mcp - DNS performance and debugging at
dns-analytics.mcp.cloudflare.com/mcp, and global internet measurements atradar.mcp.cloudflare.com/mcp - Streamable HTTP on every server at both
/mcpand/sse, the latter as a URL alias onto the same handler
Requirements
A Cloudflare account, authorised over OAuth when you connect — the browser opens so you choose which permissions the agent gets. For an unattended integration such as the OpenAI Responses API, create a Cloudflare API token scoped to what that particular server needs and pass it as a bearer token. Some features need a paid Workers plan. One migration note: a legacy GET /sse request now returns 410 Gone with the two ways forward — configure the existing URL for Streamable HTTP, or move to the /mcp URL.
Setup effort
Follow the published steps
USE CASES
01
Working out why an app is erroring in production
Connect to the observability server and read the logs and analytics from the conversation you are already debugging in. Keep the queries specific — chained tool calls on this server are the ones most likely to run long.
02
Building a Worker with the right primitives
Use the Workers bindings server to reach storage, AI and compute primitives, and the builds server to see how the deploy went. Two narrow servers rather than one broad one.
03
Keeping a coding agent on current Cloudflare guidance
Point it at the documentation server so answers come from current reference material rather than from training data. Cloudflare's platform moves fast enough for that to matter.
04
Checking global conditions before blaming your own stack
Query Radar for internet-wide measurements. When traffic drops, the first useful question is whether it dropped for everyone, and this answers it without a support ticket.
05
Answering an audit question
Query the audit log server for what changed in the account and generate the report, and use the CASB server to surface SaaS misconfigurations. Both are read-oriented, which is what an audit wants.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client with remote-server (Streamable HTTP) support
- A Cloudflare account; some features need a paid Workers plan
INSTALLATION
Connect your client
Server setup
Choose the servers for the product areas you need. Each one is its own URL (docs, bindings, builds, observability, containers, browser, logs, ai-gateway, autorag, auditlogs, dns-analytics, dex, casb, radar, blog, demo-day at <YOUR_NAME>.mcp.cloudflare.com/mcp), so add only those.
Add them to a client with remote-server support, as in the block below. When you connect, Cloudflare opens in your browser so you authorize over OAuth and pick the permissions the agent gets.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"cloudflare-docs": {
"url": "https://docs.mcp.cloudflare.com/mcp"
},
"cloudflare-bindings": {
"url": "https://bindings.mcp.cloudflare.com/mcp"
},
"cloudflare-builds": {
"url": "https://builds.mcp.cloudflare.com/mcp"
},
"cloudflare-observability": {
"url": "https://observability.mcp.cloudflare.com/mcp"
},
"cloudflare-containers": {
"url": "https://containers.mcp.cloudflare.com/mcp"
},
"cloudflare-browser": {
"url": "https://browser.mcp.cloudflare.com/mcp"
},
"cloudflare-logs": {
"url": "https://logs.mcp.cloudflare.com/mcp"
},
"cloudflare-ai-gateway": {
"url": "https://ai-gateway.mcp.cloudflare.com/mcp"
},
"cloudflare-autorag": {
"url": "https://autorag.mcp.cloudflare.com/mcp"
},
"cloudflare-auditlogs": {
"url": "https://auditlogs.mcp.cloudflare.com/mcp"
},
"cloudflare-dns-analytics": {
"url": "https://dns-analytics.mcp.cloudflare.com/mcp"
},
"cloudflare-dex": {
"url": "https://dex.mcp.cloudflare.com/mcp"
},
"cloudflare-casb": {
"url": "https://casb.mcp.cloudflare.com/mcp"
},
"cloudflare-radar": {
"url": "https://radar.mcp.cloudflare.com/mcp"
},
"cloudflare-blog": {
"url": "https://blog.mcp.cloudflare.com/mcp"
},
"cloudflare-demo-day": {
"url": "https://demo-day.mcp.cloudflare.com/mcp"
}
}
}All sixteen servers are listed; delete the ones you don't need. Some features need a paid Workers plan. For unattended use (for example the OpenAI Responses API), create a Cloudflare API token scoped to that server and send it as a Bearer token instead of OAuth.