Manage Cloudflare Resources with MCP

The Cloudflare MCP server connects Claude to Cloudflare's developer platform, letting you deploy, configure, and manage resources across Workers, KV, R2, D1, and other Cloudflare services. Cloudflare actually exposes multiple specialized remote MCP servers rather than one monolith: Documentation (up-to-date Cloudflare reference information), Workers Bindings (build Workers with storage, AI, and compute), Workers Builds (manage Cloudflare Workers Builds), Observability (debug and analyze logs and analytics), Radar (global Internet traffic insights and URL scans), Container (spin up sandbox development environments), Browser Rendering (fetch web pages and take screenshots), and AI Gateway (search logs, inspect prompts and responses).

Use it when you're working inside a Cloudflare account and want Claude to deploy or inspect Workers, manage KV namespaces or R2 buckets, query D1 databases, pull Radar traffic insights, or render and screenshot web pages through Cloudflare's browser service. Some features require a paid Cloudflare Workers plan, so it is not usable end-to-end on a free-tier account for every capability listed.

• Deploy and manage Workers
• Interact with KV namespaces
• Manage R2 object storage
• Query D1 databases
• View logs and analytics
• Access Cloudflare Radar data
• Browser automation and screenshots

Authentication happens through Cloudflare OAuth when you connect to a remote server -- you'll be prompted to authorize access to your Cloudflare account. Each server supports the streamable-http transport via its /mcp endpoint, plus a deprecated sse transport via /sse.

Since these are remote MCP servers, connect through mcp-remote:

{
  "mcpServers": {
    "cloudflare-bindings": {
      "command": "npx",
      "args": ["mcp-remote", "https://bindings.mcp.cloudflare.com/mcp"]
    },
    "cloudflare-observability": {
      "command": "npx",
      "args": ["mcp-remote", "https://observability.mcp.cloudflare.com/mcp"]
    }
  }
}

Developers and teams already building on Cloudflare Workers, KV, R2, or D1 who want to drive deployment, configuration, and observability tasks through Claude instead of switching to the Cloudflare dashboard or CLI.