cloudflare-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_API_TOKEN | Yes | Cloudflare API token with the necessary permissions (e.g., Zone DNS Edit, Zone Read, Cache Purge). Required to authenticate all requests. | |
| CLOUDFLARE_ACCOUNT_ID | No | Optional Cloudflare account ID used to scope cf_list_zones to a single 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cf_requestB | Call ANY Cloudflare API v4 endpoint. Universal. path e.g. "/zones", "/zones/{id}/dns_records". Use for anything not covered below. |
| cf_verifyB | Verify the API token (status + which it is). |
| cf_list_zonesB | List all zones (domains) with their ids and status. |
| cf_dns_listC | List DNS records for a zone (zone = domain name or zone id). |
| cf_dns_createC | Create a DNS record. Then re-read with cf_dns_list to verify. |
| cf_dns_updateC | Update a DNS record by id (PATCH; only pass fields to change). |
| cf_dns_deleteC | Delete a DNS record by id (gated). |
| cf_purge_cacheB | Purge cache for a zone. {everything:true} gated by confirm; or files:[urls]. |
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
The specific tools (cf_verify, cf_list_zones, cf_dns_list/create/update/delete, cf_purge_cache) each target a distinct resource+action and are easy to tell apart. The only overlap is cf_request, a universal catch-all that can technically do anything the specific tools do, but the description explicitly frames it as a fallback, mitigating most ambiguity.
All tools share the cf_ prefix and snake_case casing, which is clean and predictable. The pattern is mostly verb_noun (list_zones, purge_cache) but cf_dns_list is noun_verb while cf_dns_create/update/delete are noun_verb variants, a minor deviation rather than a real inconsistency.
Eight tools is a well-scoped set: a small set of DNS CRUD operations, zone listing, cache purge, verification, and a universal escape hatch. Each tool earns its place without redundancy.
DNS record lifecycle is fully covered (list, create, update, delete) plus cache purge and token verification, with cf_request backfilling zone management and other endpoints. Only minor gaps exist (e.g. no explicit zone create/delete tool), but the universal tool makes these reachable.