Update
Cloudflare: DNS records, zone settings, cache and Workers with your own API token
TL;DR
Cloudflare is now a connected platform: 18 reads and 9 writes with an API token you create in your Cloudflare profile. The token's permissions are the limit — what it may not do is answered with the exact permission to add. By default every change waits for your approval; deleting a DNS record, deploying Worker code and security settings always wait for a person.
What changed
- Connect with a token: paste an API token on the Cloudflare card; it is checked with Cloudflare before it is saved and stored encrypted. Each Cloudflare account it reaches becomes its own connection, with what the token can and cannot do there.
- Zone-only tokens work: a token with zone permissions only (Cloudflare's "Edit zone DNS" template) connects through its zones; its account areas are reported as a missing permission, never as empty.
- DNS named precisely: records need the zone permission named just "DNS". DNS Settings, DNS Views and DNS Firewall are account permissions and do not reach records — the card and the refusal say so.
- Reads: zones, DNS records and the BIND export, zone settings, rulesets, traffic by day, Workers and routes, Pages, R2, KV, D1 and registered domains.
- Changes: DNS records, zone settings, cache purges, Worker routes and Worker deploys. They follow your approval setting — by default each waits for your approval card, and auto-approve is opt-in.
- Always a person: deleting a DNS record, deploying a Worker, removing a Worker route, purging everything, TLS and security settings (HSTS included), taking a record off the proxy, DNS batches and pausing a zone or changing its plan.
- Never reachable: users, members, API tokens, billing and subscriptions, adding a zone or deleting one.
- Over MCP and REST: cloudflare__<tool>, plus cloudflare__raw_request for any other Cloudflare API v4 request, bound to the connected account and its own zones.
Keep an agent to some domains with a Forbidden Rule: Forbidden Rules can name domains and resources. Setup and every tool: Cloudflare guide · Cloudflare platform page · Cloudflare MCP server · Cloudflare playbook.
Frequently asked questions
- Does Agent Planners support Cloudflare?
- Yes. It connects with your own Cloudflare API token and covers DNS records, zone settings, cache, rulesets, traffic, Workers and routes, and reads Pages, R2, KV, D1 and registered domains.
- Can the agent delete DNS records or deploy Workers on its own?
- No. Deleting a record, deploying a Worker, removing a route, purging everything and security settings always wait for a person, under auto-approve and from an MCP client too.