@archawat/mcp-cloudflare
v1.0.1
Published
MCP server for managing Cloudflare DNS records across multiple domains from one API token
Maintainers
Readme
@archawat/mcp-cloudflare
Model Context Protocol (MCP) server for managing Cloudflare DNS across multiple zones (domains) from a single API token. Built for bulk workflows — flipping proxy on/off across many records, auditing DNS across zones, and batched record updates.
Features
- Multi-zone from one token — pass a domain name like
"example.com"and the server resolves the zone for you. Zone IDs also accepted. - Bulk operations —
bulk_toggle_proxy,bulk_update_dns_record, andbulk_list_dns_recordsrun concurrently and share a per-invocation zone-ID cache so repeated zones don't cost extra lookups. - Safe defaults — new A/CNAME records are created with
proxied: false(DNS-only, grey cloud). Proxy is opt-in. - Auto-pagination —
list_dns_recordsfetches every page in parallel unless you ask for a specific one.
Install
No local install required — use npx or bunx to run it on demand.
Claude Code / Claude Desktop (.mcp.json)
Via npx (Node):
{
"mcpServers": {
"cloudflare": {
"command": "npx",
"args": ["-y", "@archawat/mcp-cloudflare"],
"env": { "CLOUDFLARE_API_TOKEN": "cf-token-here" }
}
}
}Via bunx (Bun):
{
"mcpServers": {
"cloudflare": {
"command": "bunx",
"args": ["-y", "@archawat/mcp-cloudflare"],
"env": { "CLOUDFLARE_API_TOKEN": "cf-token-here" }
}
}
}Claude Code CLI
claude mcp add cloudflare -s user \
-e CLOUDFLARE_API_TOKEN="cf-token-here" \
-- npx -y @archawat/mcp-cloudflareGlobal install (fastest cold-start)
npm install -g @archawat/mcp-cloudflare
# or: bun add -g @archawat/mcp-cloudflareThe global bin is named mcp-cloudflare (unscoped), so:
{
"mcpServers": {
"cloudflare": {
"command": "mcp-cloudflare",
"env": { "CLOUDFLARE_API_TOKEN": "cf-token-here" }
}
}
}API Token
Create a Cloudflare token at https://dash.cloudflare.com/profile/api-tokens with:
Zone:ReadZone:DNS:Edit
Scope the token to the zones you want to manage, or grant "All zones".
Tools
| Tool | Purpose |
|---|---|
| list_zones | Discover which domains the token can manage. |
| list_dns_records | List records in a zone; auto-paginates across all pages unless page is set. |
| bulk_list_dns_records | List records across many zones in one call. Concurrent per-zone. |
| create_a_record | Create an A record. proxied defaults to false. |
| create_cname_record | Create a CNAME record. proxied defaults to false. |
| toggle_proxy | Flip proxy on/off by record ID, or by name (+ optional type). |
| bulk_toggle_proxy | Flip proxy for many records in one call (shared proxied value). |
| update_dns_record | Patch content, ttl, proxied, or comment on a record. |
| bulk_update_dns_record | Patch many records in one call with per-item fields. |
| delete_dns_record | Delete a record by ID. Destructive. |
All tools accept either a domain name ("example.com") or a 32-char zone ID as the zone argument.
Bulk result shape
Bulk tools return per-item results; a single failure doesn't abort the batch:
{
"succeeded": 10,
"failed": 1,
"results": [
{ "zone": "example.com", "ok": true, "record": { "id": "…", "proxied": true } },
{ "zone": "other.com", "ok": false, "error": "No proxyable record found for 'www.other.com'." }
]
}isError: true is set on the tool response whenever any item fails, while still returning every result.
Development
Requires Bun (recommended) or Node 18+.
bun install
bun run dev # run src/index.ts with --watch
bun run start # run src/index.ts once
bun run typecheck # tsc --noEmit
bun run build # emit dist/ for publishingTo run the dev copy as the MCP server instead of the published package, point .mcp.json at your local build:
{
"mcpServers": {
"cloudflare": {
"command": "bun",
"args": ["/abs/path/to/mcp-cloudflare/src/index.ts"],
"env": { "CLOUDFLARE_API_TOKEN": "cf-token-here" }
}
}
}The server speaks stdio — your MCP client spawns the process and communicates over stdin/stdout.
License
MIT
