create_dns_record
Create a new DNS record
LABSCO SUMMARY
The zone lives in configuration rather than in a parameter, so a record cannot be created in the wrong one.
No tool here takes a zone id, which puts a hard limit on what a mistaken call can reach — and means covering a second zone is a second instance rather than a second argument. Within that zone the surface is complete: create, read, update and delete, with the proxied flag and TTL on the write calls, so the orange cloud is a decision the agent makes rather than one someone has to finish in the dashboard.
What it is
A Cloudflare DNS client scoped to a single configured zone, with create, read, update and delete over its records — the everyday DNS work, done from the conversation rather than the dashboard.
What you get
- list_dns_records for the configured zone, filterable by name and type, and get_dns_record by its record id.
- create_dns_record taking a type, name, content, TTL, priority and the proxied flag.
- update_dns_record over the same fields by record id, and delete_dns_record.
- The record types you would expect a zone to need: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA and PTR.
Requirements
A Cloudflare API token with rights to edit DNS — the Zone:Edit template, or a custom token with Zone:Read and Zone:Edit — and the zone ID from that domain's dashboard sidebar. Both go into the environment. Scoping the token to the one zone is worth doing, because nothing here takes a zone as an argument.
Setup effort
One command plus a key — npx -y @thelord/mcp-cloudflare, then supply credentials
USE CASES
01
Pointing a hostname at a new server
Find the existing record, update its content, and confirm what the zone now holds — no dashboard tab.
02
Turning proxying on or off for a record
Flip the proxied flag on the record itself, rather than leaving it as a manual step after the change.
03
Adding the verification record a service asked for
Create the TXT or CNAME record with the TTL the provider wants, and read it back to confirm it landed.
04
Clearing out records that outlived the service behind them
List the zone, work out which are dead, and delete them by id.
5 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
get_dns_record
Get a specific DNS record by ID
list_dns_records
List all DNS records for the configured zone
update_dns_record
Update an existing DNS record
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected.
Requires
- npx on PATH
- CLOUDFLARE_API_TOKEN in your environment
- CLOUDFLARE_ZONE_ID in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @thelord/mcp-cloudflareMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"cloudflare": {
"command": "npx",
"args": [
"-y",
"@thelord/mcp-cloudflare"
],
"env": {
"CLOUDFLARE_API_TOKEN": "<YOUR_CLOUDFLARE_API_TOKEN>",
"CLOUDFLARE_ZONE_ID": "<YOUR_CLOUDFLARE_ZONE_ID>"
}
}
}
}
