Cloudflare DNS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_ZONE_ID | No | Default zone ID (can be provided per request) | |
| CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API token with Zone:Read and DNS:Edit permissions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cloudflare_list_zonesA | List all DNS zones accessible to the API token |
| cloudflare_get_zoneB | Get details for a specific DNS zone |
| cloudflare_list_dns_recordsB | List DNS records for a zone |
| cloudflare_create_dns_recordC | Create a new DNS record in a zone |
| cloudflare_update_dns_recordC | Update an existing DNS record |
| cloudflare_delete_dns_recordB | Delete a DNS record |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct action (create, delete, get, list, update) on specific resources (DNS records or zones), with no overlap in functionality.
All tools follow a consistent 'cloudflare_verb_noun' pattern using snake_case, making them predictable and easy to differentiate.
Six tools is well-scoped for a DNS management server, covering essential CRUD operations without unnecessary bloat or gaps.
The set provides full CRUD for DNS records plus zone listing and details, covering the core lifecycle needs for DNS management.