cloudflare-dns-core-openapi
Core Cloudflare API for listing authorized zones, reading zone details, listing DNS records, and creating, updating, or deleting DNS records. The user supplies a scoped Cloudflare API token at connection time; no credential is included. Require confirmation before DNS changes. Official documentation: https://developers.cloudflare.com/api/
Connect this API to an AI agent Browse all specs
What you can do with cloudflare-dns-core-openapi via MCP
Every endpoint below becomes a governed tool your AI agent (Claude, ChatGPT, or a customer-facing VX agent) can call — with scoped permissions, sandbox testing, and audit logs.
| Method | Path | Operation | Description |
|---|---|---|---|
| GET | /zones |
listCloudflareZones | List zones |
| GET | /zones/{zone_id} |
getCloudflareZone | Get zone details |
| GET | /zones/{zone_id}/dns_records |
listCloudflareDnsRecords | List DNS records |
| POST | /zones/{zone_id}/dns_records |
createCloudflareDnsRecord | Create a DNS record |
| GET | /zones/{zone_id}/dns_records/{dns_record_id} |
getCloudflareDnsRecord | Get a DNS record |
| PUT | /zones/{zone_id}/dns_records/{dns_record_id} |
updateCloudflareDnsRecord | Update a DNS record |
| DELETE | /zones/{zone_id}/dns_records/{dns_record_id} |
deleteCloudflareDnsRecord | Delete a DNS record |
Authentication
bearerAuth
Bearer token — sent as Authorization: Bearer <token>
Use a scoped API token with only the DNS permissions required for the selected zones.
Usage guide
Getting credentials
- Create or sign in to a Cloudflare account.
- Open the Cloudflare dashboard and create a scoped API token from the API Tokens section.
- Grant only the permissions required for the selected zones. Use read-only zone and DNS permissions for inspection; add DNS edit permission only when changes are required.
- When VX Agent asks for authentication, provide the Cloudflare API token using Bearer authentication.
- Use the fixed API base URL
https://api.cloudflare.com/client/v4.
Keep the API token private. Do not paste it into the Swagger file, marketplace description, prompts, or chat messages.
How to use this API
Use this API to inspect authorized Cloudflare zones and manage DNS records. It is useful for domain configuration, DNS troubleshooting, verification records, email setup, CDN routing, and infrastructure operations.
A typical workflow is:
- Use
GET /zonesto find the zone that the connected account is authorized to manage. - Use
GET /zones/{zone_id}to inspect the selected zone and confirm its status. - Use
GET /zones/{zone_id}/dns_recordsto review existing DNS records. Filter by record type or name whenever possible. - Use
GET /zones/{zone_id}/dns_records/{dns_record_id}to inspect one record before changing it. - Use
POST /zones/{zone_id}/dns_recordsto create an A, AAAA, CNAME, MX, TXT, NS, or SRV record after confirming all values. - Use
PUT /zones/{zone_id}/dns_records/{dns_record_id}to replace an existing record only after explicit confirmation. - Use
DELETE /zones/{zone_id}/dns_records/{dns_record_id}only after the user confirms the exact zone, record ID, name, type, and deletion reason.
Before changing DNS, verify the zone ID, record ID, record type, name, content, TTL, priority, and proxy status. Use proxied=false for record types that cannot be proxied, such as MX and most TXT records. Use a narrow query and pagination when reviewing many records.
Safety and usage notes
DNS changes can immediately interrupt websites, APIs, email delivery, domain verification, SSL validation, and other production services. Always ask for confirmation immediately before creating, replacing, or deleting a DNS record.
Prefer a read-only token for inspection. Never create, rotate, edit, or delete Cloudflare API tokens through an unreviewed workflow. Do not modify nameservers, SSL settings, zone activation, or other account settings unless the user explicitly requests and confirms the exact change.
Do not expose API tokens, private zone information, verification records, internal hostnames, or infrastructure details. Use a test zone when possible and record the previous DNS value before making a change.
A 401 response usually indicates an invalid or expired API token. A 403 response usually indicates insufficient zone or DNS permissions. A 404 response may indicate an invalid zone ID or DNS record ID. A 400 response may indicate an invalid record type, content, TTL, priority, or proxy configuration.
Official documentation: Cloudflare API Reference and DNS Records API.
How to use this spec
- Create a free VX Agents account (sandbox tools included).
- Open the marketplace and connect “cloudflare-dns-core-openapi” to an agent.
- Expose it as an MCP server for Claude/ChatGPT, or chat with it directly.