Integrations
Cloudflare integration
Your Cloudflare account.One question away.
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.
Give this to your agent
set up https://corespeed.io/SKILL.mdConnect Cloudflare after setup. Access follows the connected account and its permissions.
From the whole APIto the one call you need.
Requests you can make once Cloudflare is connected. The data is fictional.
- CursorAnswer
API search
Purge cached files
- POST /zones/{zone_id}/purge_cache
- Body: the list of URLs to purge.
Find the right endpoint
Found, not called
- Cloudflareacme.dev · DNS
- Aapi.acme.dev → 203.0.113.10Old IP
- Astatus.acme.dev → 203.0.113.10Old IP
- CNAMEwww.acme.dev → acme.pages.devProxied
Audit your DNS
No record changed
Approval requestWaiting
Cursor for you
cloudflare__execute
“Point api.acme.dev at 203.0.113.24”
Policy: Ask before any DNS change.
ApproveDeny
Hold a change for a person
Waiting for you
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.
Reads fromCloudflare
All connectors →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.
cloudflare__searchok
GET /zones/{zone_id}/dns_records
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 guidesClaude CodeCodexCursor