Cloudflare MCP Server

Add https://mcp.cloudflare.com/mcp to your MCP client config

Cloudflare’s MCP Suite

Cloudflare runs its own MCP servers as deployed Workers applications. You get Workers, KV, R2, D1, Radar, Logpush, browser rendering, and documentation search — all without installing a local binary. As of mid-2026, Cloudflare maintains more than a dozen distinct endpoints, each scoped to a product area. The primary endpoint at mcp.cloudflare.com covers 2,500+ API operations, formatted for token efficiency so long operation lists don’t exhaust context windows.

For devops-and-infra teams already routing infrastructure through Cloudflare, this integration removes the context switch between Claude and the Cloudflare dashboard. Pair it with the Sentry MCP server to correlate Workers error rates with actual stack traces.

How does it work?

Add the server URL to your MCP client config (Claude Desktop, Claude Code, or Cursor) alongside a Cloudflare API token. Authentication runs over OAuth or API token headers — no environment variable juggling in most clients.

Server catalog

Server	URL	What it covers
General API	mcp.cloudflare.com/mcp	2,500+ Cloudflare API endpoints
Workers Bindings	bindings.mcp.cloudflare.com/mcp	Storage, AI, and compute primitives
Workers Builds	builds.mcp.cloudflare.com/mcp	CI/CD insights and build management
Observability	observability.mcp.cloudflare.com/mcp	Logs and analytics debugging
Radar	radar.mcp.cloudflare.com/mcp	Internet traffic trends and URL scans
Browser Rendering	browser.mcp.cloudflare.com/mcp	Fetch pages, convert to Markdown, screenshot
Documentation	docs.mcp.cloudflare.com/mcp	Up-to-date Cloudflare reference search

Transport and legacy SSE

All servers support streamable-http as the primary transport via the /mcp path. A legacy /sse endpoint remains available but is deprecated. Prefer streamable-http for new integrations.

When to use it

This integration makes most sense when your project runs on Cloudflare Workers and you want Claude to inspect live infrastructure, deploy code changes, query D1 databases, or investigate traffic anomalies — all without opening the dashboard. The Observability server is useful for on-call sessions: it surfaces Workers log data directly in Claude’s context, so “what spiked at 14:00 UTC?” gets an answer without a separate tab.

Teams building on Cloudflare’s developer-tools stack — Workers, KV, R2, D1 — get the most from this integration, especially when combined with the GitHub MCP server for repository-to-deployment workflows.

Frequently asked questions

Does the Cloudflare MCP server support both SaaS and self-hosted?

Cloudflare’s platform is SaaS-only, so all MCP servers target the public Cloudflare API at api.cloudflare.com. There is no self-hosted option. For on-premise infrastructure tooling, the Sentry MCP server supports private deployments.

How do I limit the server to read-only operations?

Scope your Cloudflare API token to read-only permissions for the products you need. The MCP server passes your token to the Cloudflare API verbatim — token permissions are the access control layer. Narrow API token scopes before sharing a token with any automated system.

Is the Workers Bindings server the same as the general API server?

No. The Workers Bindings server provides workflow-oriented tools for building Workers apps: attaching KV namespaces, configuring AI gateway bindings, managing D1 connections. The general API server at mcp.cloudflare.com provides broad coverage but with thinner tool descriptions. Use Bindings for active development, the general API for one-off queries across Cloudflare products.