Cloudflare MCP Server
Operate Cloudflare DNS, Workers, R2, KV, tunnels, WAF, and Zero Trust from your agent instead of clicking through dashboards for every change.
Overview
Cloudflare MCP Server is an Operate-phase MCP server that exposes 84 tools for DNS, Tunnels, WAF, Zero Trust, R2, KV, and Workers on your Cloudflare account.
What is this MCP server?
- 84 MCP tools covering DNS, Tunnels, WAF, Zero Trust, R2, KV, and Workers
- stdio via npx @itunified.io/mcp-cloudflare (registry version 2026.4.10-1)
- CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID environment configuration
- Broad Cloudflare API surface for agents in Claude Code, Cursor, and Codex
- 84 tools documented in server description
- Server version 2026.4.10; npm package version 2026.4.10-1
- stdio transport with runtime hint npx
What problem does it solve?
You manage Cloudflare across many products but your agent cannot apply DNS, edge, or storage changes without you writing custom API calls each time.
Who is it for?
Indie devs with apps on Cloudflare who want agent-assisted DNS, Workers, R2, KV, tunnel, WAF, and Zero Trust operations.
Skip if: Builders not on Cloudflare, or production changes without a properly scoped API token and review process.
What do I get? / Deliverables
After you add the server with API token and account ID, your agent can invoke MCP tools across the listed Cloudflare services from chat.
- MCP tool access across DNS, Tunnels, WAF, Zero Trust, R2, KV, and Workers
- Agent-operable Cloudflare changes using official API credentials
Recommended MCP Servers
Journey fit
Running and adjusting production edge infrastructure matches Operate, where solo builders maintain what they already shipped on Cloudflare. Infra is the right shelf for account-level DNS, storage, compute, and security controls exposed as dozens of MCP tools.
How it compares
Wide Cloudflare API MCP layer, not a single-purpose DNS skill or hosting tutorial.
Common Questions / FAQ
Who is io.github.itunified-io/cloudflare for?
It is for developers operating Cloudflare accounts who want MCP clients to run many Cloudflare operations via one npm stdio server.
When should I use io.github.itunified-io/cloudflare?
Use it when you repeatedly tune DNS, Workers, R2, KV, tunnels, WAF, or Zero Trust and prefer agent-driven changes with token auth.
How do I add io.github.itunified-io/cloudflare to my agent?
Configure npx @itunified.io/mcp-cloudflare with CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID in your MCP client stdio server block.