Cloudflare's own MCP servers

Cloudflare runs a catalog of managed remote MCP servers which you can connect to using OAuth on clients like Claude ↗︎, Windsurf ↗︎, our own AI Playground ↗︎ or any SDK that supports MCP ↗︎.

These MCP servers allow your MCP client to read configurations from your account, process information, make suggestions based on data, and even make those suggested changes for you. All of these actions can happen across Cloudflare's many services including application development, security and performance.

Use the Streamable HTTP endpoint at /mcp for new connections. The servers support the new MCP 2026-07-28 Specification and stateless requests from 2025 Streamable HTTP clients. Historical /sse URLs remain available as aliases for the same Streamable HTTP handler, but they do not serve the deprecated HTTP+SSE transport. Clients configured to force SSE transport must switch to Streamable HTTP or automatic transport detection.

The Cloudflare API MCP server ↗︎ provides access to the entire Cloudflare API — over 2,500 endpoints across DNS, Workers, R2, Zero Trust, and every other product — through just two tools: search() and execute().

It uses the search-and-execute Code Mode pattern, a technique where the model writes JavaScript against a typed representation of the OpenAPI spec and the Cloudflare API client, rather than loading individual tool definitions for each endpoint. The generated code runs inside an isolated Dynamic Worker sandbox.

This approach uses approximately 1,000 tokens regardless of how many API endpoints exist. An equivalent MCP server that exposed every endpoint as a native tool would consume over 1 million tokens — more than the entire context window of most foundation models.

Add the following configuration to your MCP client:

{
	"mcpServers": {
		"cloudflare-api": {
			"url": "https://mcp.cloudflare.com/mcp"
		}
	}
}

When you connect, you will be redirected to Cloudflare to authorize via OAuth and select the permissions to grant to your agent.

For CI/CD or automation, you can create a Cloudflare API token ↗︎ with the permissions you need and pass it as a bearer token in the Authorization header. Both user tokens and account tokens are supported.

For more information, refer to the Cloudflare MCP repository ↗︎.

You can install the Cloudflare Skills plugin ↗︎, which bundles the Cloudflare MCP servers alongside contextual skills and slash commands for building on Cloudflare. The plugin works with any agent that supports the Agent Skills standard, including Claude Code, OpenCode, OpenAI Codex, and Pi.

Install using the plugin marketplace ↗︎:

/plugin marketplace add cloudflare/skills

Install from the Cursor Marketplace, or add manually via Settings > Rules > Add Rule > Remote Rule (Github) with cloudflare/skills.

Install using the npx skills ↗︎ CLI:

npx skills add https://github.com/cloudflare/skills

Clone the cloudflare/skills ↗︎ repository and copy the skill folders into the appropriate directory for your agent:

In addition to the Cloudflare API MCP server, Cloudflare provides product-specific MCP servers for targeted use cases:

Check the GitHub page ↗︎ to learn how to use Cloudflare's remote MCP servers with different MCP clients.