Name: Cloudflare API MCP Server
Author: Cloudflare

Cloudflare's recommended MCP server covers its full API of about 2,500 endpoints with just a few tools: Claude writes short scripts that search the API spec and then run the calls in a sandbox, which keeps token use low. It works across Workers, DNS, R2, D1, KV, firewall rules and other products, and it can also search Cloudflare's developer docs.

Who it is for

Website owners who manage DNS on Cloudflare
Developers building on Workers and Pages
Ops teams automating Cloudflare settings

Prompts to try

Once it is connected, ask in plain words. Claude decides when to use the server and asks before it changes anything important.

Prompt 1

List the DNS records for example.com and point the www record to my new server at 203.0.113.10.

Prompt 2

Create an R2 bucket called site-backups and a KV namespace called feature-flags.

Prompt 3

Which of my Workers have not been deployed in the last 90 days?

How to connect it

In Claude Code

$claude mcp add --transport http cloudflare-api https://mcp.cloudflare.com/mcp

In the Claude desktop app

Customize > Connectors > + Add > Add custom connector, URL: https://mcp.cloudflare.com/mcp

Hosted address: https://mcp.cloudflare.com/mcp

Good to know

For automation, send a Cloudflare API token as a Bearer header; the older bindings, builds and observability servers (including the Developer Platform connector in Claude's directory) are deprecated in favor of this one.

Unlock the setup steps

Free. Leave your email once to open the setup steps for all 150 servers, and get the best new connectors each month.

How we checked it

Checked Cloudflare's MCP servers docs page (updated 2026-10-12), the cloudflare/mcp repo (Apache-2.0, last commit 2026-10-13) and the deprecation table in cloudflare/mcp-server-cloudflare; the endpoint answers with an OAuth challenge.

Source: developers.cloudflare.com/agents/model-context-protocol/cloudflare/servers-for-cloudflare/

Cloudflare API MCP Server