Cloudflare’s official MCP servers are hosted, remote endpoints. The recommended one is the Code Mode server at https://mcp.cloudflare.com/mcp, which gives Claude broad access across Cloudflare’s APIs. Cloudflare also runs domain-specific servers for documentation, Workers bindings, builds, observability, browser rendering, AI Gateway and more. The older npm package @cloudflare/mcp-server-cloudflare was last published in March 2025. For developers running infrastructure on Cloudflare, this collapses dashboard tab-switching into single prompts.
Why use it
Cloudflare’s dashboard is good but spread across many product surfaces. Claude with the MCP server can answer “what’s the status of my last Workers deploy?” or “how much R2 storage am I using?” without you opening four tabs.
For solo founders running on Cloudflare’s stack (which is plenty), it’s one of the higher-leverage integrations.
What it actually does
The Code Mode server exposes the Cloudflare API through code execution, so Claude works with a small set of general tools rather than one tool per endpoint. The domain-specific servers give curated tools for one product area, such as observability, Workers bindings or Radar.
Practical patterns:
- “Show me my last five Workers builds and their status.”
- “Search my Worker logs for errors in the last hour.”
- “List my Workers and tell me which ones have no recent deploys.”
Gotchas
Broad permissions are powerful. Access that can edit Workers can deploy code; access that can edit DNS can take your site down. Default to read-only and grant write only where needed.
Some operations are async. Workers deployments, R2 uploads, and zone-level changes can take seconds to propagate. The server returns the queued state; Claude needs to poll or wait.
Pair with GitHub for an end-to-end deploy loop: open a PR with code, merge it, watch the Cloudflare deploy, run a smoke test. Each step is a tool call.
