create_dns_record
Create a new DNS record.
LABSCO SUMMARY
DNS edits from the assistant, with deletion behind a switch you have to throw on purpose.
Reads and safe writes work with the token alone; deleting a record and purging an entire zone's cache require CF_ALLOW_DESTRUCTIVE=true as well, so the worst outcomes are not one hallucinated argument away. Updates apply only the fields you pass, which means changing a TTL does not silently rewrite the record's content.
What it is
A Cloudflare operations server covering zones, DNS records, cache and page rules, with the destructive actions held behind a separate flag.
What you get
- Zones on the account listed and filtered by name, and one zone opened for its details
- A zone's key security and performance settings — SSL mode, security level, minification, always-https, brotli
- DNS records listed for a zone, filtered by name or record type, and one fetched by record ID
- Records created with content, TTL, proxied state, priority and a comment
- Records updated with only the fields you pass — the rest are left as they are
- Record deletion, which refuses to run unless CF_ALLOW_DESTRUCTIVE=true
- Cache purged for a zone, either by specific URLs or everything
- Page rules listed for a zone, optionally filtered by status
Requirements
A Cloudflare API token in CF_API_TOKEN, scoped for Zone DNS Edit, Zone Read and Cache Purge — CLOUDFLARE_API_TOKEN is accepted as an alternate name. Deleting a record and purging the whole cache additionally need CF_ALLOW_DESTRUCTIVE=true, which is deliberately a separate decision from having the token. Run it with uvx mcp-cloudflare-dns over stdio, from the PyPI package mcp-cloudflare-dns, currently 0.1.1; MCP_TRANSPORT=sse with MCP_HOST and MCP_PORT switches to remote hosting. Cloudflare 429 and 5xx responses are retried with backoff. The project describes its release posture as beta.
Setup effort
One command plus a key — python -m pip install mcp-cloudflare-dns, then supply credentials
USE CASES
01
Pointing a subdomain somewhere new
Find the zone, look up the existing record, then update its content — nothing else on the record changes.
02
Adding the records a new service needs
Create them with the type, content, TTL and proxied state set, and a comment saying why.
03
Checking a zone is configured the way you think
Read its security and performance settings — SSL mode, security level, always-https.
04
Clearing stale content after a deploy
Purge the specific URLs rather than the whole zone.
05
Auditing what is on a domain
List the DNS records by type and the page rules alongside them.
06
Removing a record you are sure about
Fetch it by ID to confirm what it is, then delete it — the call refuses unless the destructive flag is set.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
delete_dns_record
Delete a DNS record. Requires CF_ALLOW_DESTRUCTIVE=true.
get_dns_record
Get a specific DNS record by zone ID and record ID.
get_zone
Get details for a specific Cloudflare zone by ID.
get_zone_settings
Get key security and performance settings for a zone. Returns SSL mode, security level, minification, always-https, brotli, etc.
list_dns_records
List DNS records for a zone.
list_page_rules
List page rules for a zone.
list_zones
List all Cloudflare zones on this account.
purge_cache
Purge Cloudflare cache for a zone.
update_dns_record
Update an existing DNS record. Only the fields you provide will be changed.
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. delete_dns_record and full cache purges stay listed but decline unless CF_ALLOW_DESTRUCTIVE=true.
Requires
- uvx on PATH
- CF_API_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
python -m pip install mcp-cloudflare-dnsMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"cloudflare-dns": {
"command": "uvx",
"args": [
"mcp-cloudflare-dns"
],
"env": {
"CF_API_TOKEN": "<YOUR_CF_API_TOKEN>"
}
}
}
}
