MCP Cloudflare DNS Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dns_recordsC | List all DNS records for the configured zone |
| get_dns_recordC | Get a specific DNS record by ID |
| create_dns_recordC | Create a new DNS record |
| update_dns_recordC | Update an existing DNS record |
| delete_dns_recordC | 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 5 tools
Each tool has a clearly distinct purpose targeting a specific CRUD operation for DNS records. The verbs (create, delete, get, list, update) are unambiguous and correspond to standard database operations, leaving no room for confusion or overlap.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_dns_record, update_dns_record). The naming is predictable and uniform across all five tools, making them easily identifiable and organized.
With 5 tools, this server is well-scoped for managing DNS records, covering the essential CRUD operations. Each tool serves a clear and necessary function without redundancy, making the count appropriate for the domain.
The tool set provides complete CRUD coverage for DNS records, including create, read (get and list), update, and delete operations. There are no obvious gaps, as all lifecycle actions are covered, ensuring agents can handle full workflows without dead ends.