cloudflare-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API token with Zone.Read and DNS.Edit permissions | |
| CLOUDFLARE_ACCOUNT_ID | No | Optional Cloudflare account ID to scope zone listing to a specific account |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_zonesA | List zones (domains) visible to this API token. |
| get_zoneA | Fetch one zone's details by its Cloudflare zone ID. |
| list_dns_recordsA | List DNS records in a zone, optionally filtered by type, name, or content. type is a record type such as A, AAAA, CNAME, MX, TXT, NS, CAA, SRV, etc. name is an exact record name (e.g. 'www.example.com'). content filters by the record's value (e.g. an IP address). |
| get_dns_recordA | Fetch one DNS record's details by its ID within a zone. |
| create_dns_recordA | Create a DNS record in a zone. type is one of A, AAAA, CNAME, MX, TXT, NS, CAA, SRV, etc. name is the record name (e.g. 'www.example.com' or '@' for the zone apex). content is the record's value (an IP for A/AAAA, a hostname for CNAME/MX, etc.). ttl is in seconds; 1 means "automatic". proxied routes traffic through Cloudflare's proxy (orange cloud) — only valid for A/AAAA/CNAME records. priority is required for MX and some SRV/URI records. |
| update_dns_recordA | Partially update an existing DNS record. Only the fields you pass are changed. |
| delete_dns_recordC | Delete a DNS record from a zone. This is irreversible. |
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 7 tools
Each tool has a clearly distinct purpose: zone retrieval vs. listing, and DNS records are fully separated into get/list/create/update/delete. No overlapping functionality.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_zone, list_dns_records, update_dns_record), making the API predictable and easy to navigate.
Seven tools are well-scoped for managing zones and DNS records, covering the essential operations without unnecessary bloat.
The set provides full CRUD for DNS records and read operations for zones, which covers the typical Cloudflare management workflow. No obvious gaps for common use cases.