# Your Cloudflare account. One question away.

Source: https://corespeed.io/integrations/cloudflare

Connect Cloudflare to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent searches Cloudflare's API and documentation, then runs short scripts against the API for DNS, Workers, R2, Zero Trust and more. It acts with the account and permissions you choose on Cloudflare's own consent screen, and approvals can hold each script before it runs.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Cloudflare after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Ask about your zones. Skip the dashboard tour

Your agent finds the endpoint in Cloudflare's API, calls it with your grant, and reports what it found.

You ask your agent: "List the DNS records for acme.dev and find the ones that still point at the old load balancer, 203.0.113.10. Do not change any record."

It calls CoreSpeed:

- `cloudflare__search`: ok, 702 ms
- `cloudflare__execute`: ok, 958 ms

It reads from: Cloudflare.

### DNS audit: Three records left behind.

Three records still point at the old load balancer. The rest are proxied as expected.

**Still on 203.0.113.10**

- api.acme.dev (A)
- status.acme.dev (A)
- legacy.acme.dev (A)

**Next**

- Confirm the new address before changing any record.

_Illustrative zone · Fictional data · No record changed_

All connectors: https://corespeed.io/docs/connectors

## From the whole API to the one call you need

Requests you can make once Cloudflare is connected. The data is fictional.

### Find the right endpoint

Purge a URL from cache · Search the API spec

- Endpoint: POST /zones/{zone_id}/purge_cache
- Body: The URLs to purge
- Found, not called

### Audit your DNS

acme.dev · records · Read through the API

- Old address: 3 records
- Proxied: 38 records
- No record changed

### Hold a change for a person

Update a record · A change waits for you

- Record: api.acme.dev
- Policy: Ask before any DNS change
- Waiting for you

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Cloudflare**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Which Cloudflare products can my agent use?

Any Cloudflare API endpoint your grant allows, from DNS and Workers to R2 and Zero Trust. The agent finds an endpoint with search, then calls it with execute.

### Do I need to create a Cloudflare API token?

No. You sign in to Cloudflare and choose the account and permissions on its consent screen. The connection holds exactly that grant.

### Can my agent change DNS or Workers?

Yes, if your grant allows it. Each script runs as one execute call, which approvals can hold for a person before any of its requests run. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/cloudflare

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [AWS for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/aws): Let your agent call any AWS API with your IAM credentials. Writes and secret reads can wait for a person.
- [Google Cloud for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gcp): Debug Cloud Run from its logs, find idle spend, and read billing inside your agent, with your own Google account.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Cloudflare's MCP servers: https://developers.cloudflare.com/agents/model-context-protocol/mcp-servers-for-cloudflare/
- Cloudflare API MCP server: https://github.com/cloudflare/mcp
- Cloudflare API: https://developers.cloudflare.com/fundamentals/api/

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)