domain-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWED_ZONE | No | The only DNS zone allowed to be managed. Defaults to 'iveseenu.com'. | iveseenu.com |
| CLOUDFLARE_ZONE_ID | No | Optional Cloudflare Zone ID for the allowed zone. If not provided, the tool will query the active zone and cache the result. | |
| CLOUDFLARE_API_TOKEN | No | Cloudflare API token used for authentication. Do not put it in config files, source code, or MCP client configuration. | |
| CLOUDFLARE_API_TOKEN_FILE | No | Path to a regular file whose contents is the Cloudflare API token. The file must have permissions 0600 and contain only the token. |
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_dnsA | List allowlisted Cloudflare DNS records, optionally filtered by type or name. |
| get_dnsA | Get DNS records for one allowlisted name. |
| create_dnsB | Create one A, AAAA, CNAME, or TXT record. Prefer dry_run first. |
| update_dnsA | Update exactly one A, AAAA, CNAME, or TXT record and verify it afterwards. |
| upsert_dnsA | Idempotently create, update, or return NOOP for one DNS record. Prefer dry_run first. |
| delete_dnsA | Delete exactly one DNS record. confirm_delete must be true; prefer dry_run first. |
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
The verbs clearly separate list/get/create/update/upsert/delete, and descriptions clarify each tool's scope. Minor overlap exists between list_dns with a name filter and get_dns, and create_dns vs upsert_dns could be confused by an agent not reading carefully, but the intended boundaries are discernible.
All tools follow a consistent verb_dns pattern: list, get, create, update, upsert, delete. This makes the tool surface highly predictable and easy to reason about.
Six tools cover the core DNS record lifecycle without unnecessary bulk. The count is well-scoped for a focused domain-manager server.
The set provides full CRUD plus idempotent upsert and post-update verification, which covers the primary workflow. However, descriptions repeatedly instruct agents to prefer dry_run first, but no dry_run tool is exposed, leaving a notable referenced capability missing.