Cloudflare MCP Server

Overview

Cloudflare ships a suite of official remote MCP servers covering Workers, R2, KV, D1, DNS, Workers AI, and the broader Cloudflare platform. They run as hosted remote MCP, so any compatible client can connect with an API token and operate Cloudflare end to end through an agent.

Best for

Best for
Teams running anything serious on Cloudflare

Use cases

• Deploy a Worker, set DNS, and ship a route in one agent session
• Inspect and rotate KV or R2 storage through an agent
• Manage DNS records and routing across many zones
• Operate Cloudflare AI gateway and Workers AI workloads

How to use

Tools exposed

• mcp-remote

Tested with

Cursor, Claude

Example client config

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

Notes

Why it matters

Cloudflare is one of the few major platform vendors to ship a full remote MCP surface in 2025. The agent can drive the edge stack end to end without a local server to manage.

How teams use it in production

Use scoped API tokens per project. Wire the relevant Cloudflare MCP surface into a Claude Code session and the agent can deploy Workers, set DNS, and manage storage without leaving the loop.

What to watch

AWS, GCP, and Azure all need similar first-party MCP surfaces. Cloudflare moving first sets the pattern.