MCP Cloudflare DNS Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_EMAIL | No | Optional: email for legacy API key authentication. | |
| CLOUDFLARE_ZONE_ID | No | Optional: default zone ID when not specified per tool. | |
| CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API token with Zone:DNS 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 |
|---|---|
| list_zonesA | List all Cloudflare zones (domains) on the account. Use this to discover zone IDs when the user refers to a domain by name. |
| list_dns_recordsA | List all DNS records for a zone. Call list_zones first to resolve a domain name to a zone_id if needed. |
| get_dns_recordA | Get a specific DNS record by ID |
| create_dns_recordA | Create a new DNS record. Call list_zones first to resolve a domain name to a zone_id if needed. |
| update_dns_recordC | Update an existing DNS record |
| delete_dns_recordB | Delete a DNS record |
| export_dns_zoneA | Export all DNS records for a zone as a JSON array. Useful for backups and bulk operations. Call list_zones first to resolve a domain name to a zone_id if needed. |
| import_dns_zoneA | Import DNS records from a JSON array, creating each record in the zone. Returns a success/failure summary with partial failure handling. |
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 8 tools
Most tools have clearly distinct purposes: list_zones handles domain discovery, the record CRUD tools map to specific operations, and import/export handle bulk workflows. The only mild overlap is between list_dns_records and export_dns_zone, both of which retrieve all records, but their descriptions clarify that one is for standard listing and the other for backup/bulk operations.
All tool names follow a consistent snake_case verb_noun pattern: list/gets/create/update/delete/export/import paired with clear resource names (zones, dns_record, dns_zone). No mixed conventions or vague verbs.
Eight tools is well-scoped for a DNS management server: one zone discovery tool, four record CRUD operations, one single-record lookup, and two bulk export/import tools. Each tool earns its place without redundancy or bloat.
The tool surface provides full CRUD coverage for DNS records (list, get, create, update, delete), zone discovery via list_zones, and bulk workflows via import/export with partial failure handling. The only absent operations are zone-level create/delete, which are reasonably out of scope for a DNS record-focused server.