# 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.

- Page: https://www.agent200.com/connectors/cloudflare/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `cloudflare`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

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/

## About

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.

## Cloudflare tools

- **List zones** (`cloudflare_list_zones`, read): List the domains in the user's account.
- **List DNS records** (`cloudflare_list_dns_records`, read): List the DNS records of a zone.
- **Create a DNS record** (`cloudflare_create_dns_record`, write): Add a DNS record to a zone.
- **Update a DNS record** (`cloudflare_update_dns_record`, write): Change a DNS record's content or settings.
- **Delete a DNS record** (`cloudflare_delete_dns_record`, write): Remove a DNS record from a zone.
- **Purge the cache** (`cloudflare_purge_cache`, write): Purge cached files for a zone, by URL or all of them.

## Limits you can set

**Turn single tools on or off.** Let the agent read zones and add records, and switch off `cloudflare_delete_dns_record` so 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "What are the DNS records for example.com"
- "Point the blog subdomain to this IP address"
- "Purge the cache for our pricing page"

## Guides: Cloudflare with your AI framework

- [Cloudflare + Claude](https://www.agent200.com/connectors/cloudflare/framework/claude.md): Connect Cloudflare to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Cloudflare + ChatGPT](https://www.agent200.com/connectors/cloudflare/framework/chatgpt.md): Give ChatGPT access to Cloudflare through Agent200: managed OAuth, ready-made tools and one API key.
- [Cloudflare + Claude Code](https://www.agent200.com/connectors/cloudflare/framework/claude-code.md): Have Claude Code build a Cloudflare agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Cloudflare + Muse](https://www.agent200.com/connectors/cloudflare/framework/muse.md): Connect Cloudflare to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Cloudflare + Grok Bot](https://www.agent200.com/connectors/cloudflare/framework/grok-bot.md): Connect Cloudflare to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Cloudflare + OpenAI Dots](https://www.agent200.com/connectors/cloudflare/framework/openai-dots.md): Give OpenAI Dots access to Cloudflare through Agent200: managed OAuth, ready-made tools and one API key.
- [Cloudflare + Claude Duet](https://www.agent200.com/connectors/cloudflare/framework/claude-duet.md): Connect Cloudflare to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Cloudflare + Hermes Agent](https://www.agent200.com/connectors/cloudflare/framework/hermes-agent.md): Connect Cloudflare to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Cloudflare + OpenClaw](https://www.agent200.com/connectors/cloudflare/framework/openclaw.md): Connect Cloudflare to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### 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.

## Related connectors

- [GitHub](https://www.agent200.com/connectors/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/connectors/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Bitbucket](https://www.agent200.com/connectors/bitbucket.md): List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
- [Jira](https://www.agent200.com/connectors/jira.md): Search, create and transition Jira issues for the connected user.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
