Developer tools
Cloudflare for AI agents.
Managed auth, ready-made tools.
List zones, manage DNS records and purge cached files in Cloudflare on behalf of each of your users.
About Cloudflare
With the Cloudflare connector, your agent works in each user’s own Cloudflare account. It can list zones, read DNS records, add, change or delete a record, and purge cached files, using only the tools your project allows.
Cloudflare is a platform for DNS, CDN, security and performance services for websites and apps.
Tools
What your agent can do in Cloudflare.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Cloudflare connection.
-
List zones
Readcloudflare_list_zonesList the domains in the user's account.
-
List DNS records
Readcloudflare_list_dns_recordsList the DNS records of a zone.
-
Create a DNS record
Writecloudflare_create_dns_recordAdd a DNS record to a zone.
-
Update a DNS record
Writecloudflare_update_dns_recordChange a DNS record's content or settings.
-
Delete a DNS record
Writecloudflare_delete_dns_recordRemove a DNS record from a zone.
-
Purge the cache
Writecloudflare_purge_cachePurge cached files for a zone, by URL or all of them.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Cloudflare, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read zones and add records, and switch off
cloudflare_delete_dns_recordso it can never remove one. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example DNS records but not cache purges. A call outside them is refused.
Get started
Connect Cloudflare
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Cloudflare
Each end user authorizes their own Cloudflare account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Cloudflare account, once. const connection = await agent200 .user("user_123") .connect("cloudflare"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Cloudflare tools
Name the user, the model and the tools. The model decides which Cloudflare tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "What are the DNS records for example.com", tools: ["cloudflare"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, by connecting their own Cloudflare account. Each connection is their own.
-
What access is requested
The connection acts with the permissions the user grants, such as reading zones, editing DNS or purging the cache. Users can revoke the connection later from their Cloudflare account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Cloudflare connector and how to use it.
Connector: Cloudflare, through Agent200. In code: "cloudflare". What it does: List zones, manage DNS records and purge cached files in Cloudflare on behalf of each of your users. Page: https://www.agent200.com/connectors/cloudflare/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Cloudflare's own page, through the authorization link Agent200 returns. Never ask a user for a Cloudflare password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: cloudflare_list_zones, cloudflare_list_dns_records. Write tools: cloudflare_create_dns_record, cloudflare_update_dns_record, cloudflare_delete_dns_record, cloudflare_purge_cache. Name "cloudflare" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/cloudflare/framework/claude/ https://www.agent200.com/connectors/cloudflare/framework/chatgpt/ https://www.agent200.com/connectors/cloudflare/framework/claude-code/ https://www.agent200.com/connectors/cloudflare/framework/muse/ https://www.agent200.com/connectors/cloudflare/framework/grok-bot/ https://www.agent200.com/connectors/cloudflare/framework/openai-dots/ https://www.agent200.com/connectors/cloudflare/framework/claude-duet/ https://www.agent200.com/connectors/cloudflare/framework/hermes-agent/ https://www.agent200.com/connectors/cloudflare/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/cloudflare.md
Guides
Use Cloudflare with the AI you build on.
Step-by-step setup for Cloudflare with a specific model, assistant or agent framework.
-
Cloudflare + Claude
How to connect Cloudflare to Claude
-
Cloudflare + ChatGPT
How to connect Cloudflare to ChatGPT
-
Cloudflare + Claude Code
How to connect Cloudflare to Claude Code
-
Cloudflare + Muse
How to connect Cloudflare to Muse
-
Cloudflare + Grok Bot
How to connect Cloudflare to Grok Bot
-
Cloudflare + OpenAI Dots
How to connect Cloudflare to OpenAI Dots
-
Cloudflare + Claude Duet
How to connect Cloudflare to Claude Duet
-
Cloudflare + Hermes Agent
How to connect Cloudflare to Hermes Agent
-
Cloudflare + OpenClaw
How to connect Cloudflare to OpenClaw
FAQ
Cloudflare and Agent200, answered.
Who handles the Cloudflare OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Cloudflare.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Cloudflare connection, never another user's. It cannot reach anything the user or Cloudflare has not authorized.
Can I limit what my agent can do in Cloudflare?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.