Cloudflare api

--- name: cloudflare-api description: "Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'." compatibility: claude-code-only allowed-tools: - Read - Write - Edit - Bash - Glob - Grep --- # Cloudflare API Hit the Cloudflare REST API directly when wrangler CLI or MCP servers aren't the right tool. For bulk operations, fleet-wide changes, and features that wrangler doesn't expose. ## When to Use This Instead of Wrangler or MCP | Use case | Wrangler | MCP | This skills | |----------|---------|-----|-----------| | Deploy a Worker | Yes | Yes | No | | Create a D1 database | Yes | Yes | No | | Bulk update 50 DNS records | Slow (one at a time) | Slow (one tool call each) | Yes : batch script | | Custom hostnames for white-label | No | Partial | Yes | | Email routing rules | No | Partial | Yes | | WAF/firewall rules | No | Yes but verbose | Yes : direct API | | Redirect rules in bulk | No | One at a time | Yes : batch script | | Zone settings across 20 zones | No | 20 separate calls | Yes : fleet script | | Cache purge by tag/prefix | No | Yes | Yes (when scripting) | | Worker route management | Limited | Yes | Yes (when bulk) | | Analytics/logs query | No | Partial | Yes : GraphQL | | D1 query/export across databases | One DB at a time | One DB at a time | Yes : cross-DB scripts | | R2 bulk object operations | No | One at a time | Yes : S3 API + batch | | KV bulk read/write/delete | One at a time | One at a time | Yes : bulk endpoints | | Vectorize query/delete | No | Via Worker only | Yes : direct API | | Queue message injection | No | Via Worker only | Yes : direct API | | Audit all resources in account | No | Tedious | Yes : inventory script | Rule of thumb: Single operations → MCP or wrangler. Bulk/fleet/scripted → API directly. ## Auth Setup ### API Token (recommended) Create a scoped token at: Dashboard → My Profile → API Tokens → Create Token ``bash # Store it export CLOUDFLARE_API_TOKEN="your-token-here" # Test it curl -s "https://api.cloudflare.com/client/v4/user/tokens/verify" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" | jq '.success' ` **Token scopes**: Always use minimal permissions. Common presets: - "Edit zone DNS" : for DNS operations - "Edit zone settings" : for zone config changes - "Edit Cloudflare Workers" : for Worker route management - "Read analytics" : for GraphQL analytics ### Account and Zone IDs `bash # List your zones (find zone IDs) curl -s "https://api.cloudflare.com/client/v4/zones?per_page=50" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" | jq '.result[] | {name, id}' # Get zone ID by domain name ZONE_ID=$(curl -s "https://api.cloudflare.com/client/v4/zones?name=example.com" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" | jq -r '.result[0].id') ` Store IDs in environment or a config file : don't hardcode them in scripts. ## Workflows ### Bulk DNS Operations **Add/update many records at once** (e.g. migrating a domain, setting up a new client): `bash # Pattern: read records from a file, create in batch while IFS=',' read -r type name content proxied; do curl -s -X POST "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ -H "Content-Type: application/json" \ -d "{\"type\":\"$type\",\"name\":\"$name\",\"content\":\"$content\",\"proxied\":$proxied,\"ttl\":1}" \ | jq '{name: .result.name, id: .result.id, success: .success}' sleep 0.25 # Rate limit: 1200 req/5min done < dns-records.csv ` **Export all records from a zone** (backup or migration): `bash curl -s "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records?per_page=100" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ | jq -r '.result[] | [.type, .name, .content, .proxied] | @csv' > dns-export.csv ` **Find and replace across records** (e.g. IP migration): `bash OLD_IP="203.0.113.1" NEW_IP="198.51.100.1" # Find records pointing to old IP RECORDS=$(curl -s "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records?content=$OLD_IP" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" | jq -r '.result[].id') # Update each one for RECORD_ID in $RECORDS; do curl -s -X PATCH "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records/$RECORD_ID" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ -H "Content-Type: application/json" \ -d "{\"content\":\"$NEW_IP\"}" | jq '.success' done `` ### Custom Hostnames (White-Label Client Do