cloudflare-mcp

A tiny TypeScript MCP server to manage a Cloudflare zone through the Cloudflare API: DNS records, cloudflared tunnels and Email Routing. Zone-agnostic: point it at any zone via env vars.

Requirements

• Node.js 18+

• A Cloudflare API token. Permissions by feature:

  • DNS tools → Zone:DNS:Edit (+ Zone:Read to resolve the zone by name)

  • Tunnel tools → Account:Cloudflare Tunnel:Edit (+ Account:Account Settings:Read to auto-resolve the account id)

  • Email Routing rules → Zone:Email Routing Rules:Edit (:Read is enough for the read-only tools)

  • Email Routing destinations → Account:Email Routing Addresses:Edit

Related MCP server: Cloudflare MCP Server

Configuration

Copy .env.example to .env and fill it in. Never commit .env.

Scripts

npm install
npm run build   # emit dist/
npm run dev     # tsx src/index.ts (stdio)
npm start       # node dist/index.js

Tools

Stand up a tunnel end-to-end

tunnel_create   name=my-dev                                   → returns id + token
tunnel_configure name=my-dev hostname=dev.example.com service=http://localhost:8770
dns_create      type=CNAME name=dev.example.com content=<id>.cfargotunnel.com
# then run it locally (no cert.pem needed):
#   TUNNEL_TOKEN=<token> cloudflared tunnel run

Forward an address end-to-end

email_destination_add   email=you@gmail.com        → verification link sent (click it)
email_rule_create       address=hello destination=you@gmail.com
email_rules_list                                   → confirm hello@example.com → you@gmail.com

A destination must be verified before a rule can forward to it, and the zone needs Email Routing enabled: email_routing_enable adds the MX/SPF/DKIM records, email_routing_dns confirms they are in place.

Token scopes: Account · Email Routing Addresses (destinations) and Zone · Email Routing Rules (rules, enable/disable) live in different scopes; granting one in the wrong scope returns Authentication error (code 10000) while everything else keeps working.

Safety semantics

• DNS: names are not record identities. dns_get, dns_update, and dns_delete accept an exact record id (preferred), or a name that resolves to exactly one record; ambiguous names are rejected instead of selecting the first result. For updates/deletes, pass type when it is needed to make the name unique.

• Tunnels: tunnel_configure and tunnel_ingress replace the current ingress configuration. They refuse to replace existing hostname routes unless replace_existing=true is passed explicitly.

• Email Routing: email_rule_create checks existing literal recipient rules and refuses to create a duplicate instead of adding another forwarding rule. email_rule_delete and email_rule_set_enabled refuse an address that more than one rule matches; pass the exact tag. email_routing_disable requires confirm=true.

Example (via an MCP client)

dns_list                                → all records
dns_get    name=app.example.com         → inspect one record
dns_create type=CNAME name=dev.example.com content=<tunnel-id>.cfargotunnel.com
dns_update name=dev.example.com proxied=true
dns_delete name=old.example.com

Use as an MCP server

Point your MCP client at the built or dev entrypoint over stdio, passing the two env vars. Example (generic MCP config):

{
  "command": "npx",
  "args": ["-y", "tsx", "/absolute/path/to/cloudflare-mcp/src/index.ts"],
  "env": {
    "CLOUDFLARE_API_TOKEN": "<your-token>",
    "CLOUDFLARE_ZONE_ID": "example.com"
  }
}

License

MIT