muumuu-domain-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-domainsA | Check availability and pricing of one or more domain names across TLDs. Use this before suggesting a domain to purchase. Returns each candidate with its availability state and price in JPY. Does NOT reserve or purchase the domain. |
| list-me-domainsA | List domains owned by the authenticated account. Supports pagination and filtering by state or exact FQDN match. Use this to discover domain IDs needed by other tools (e.g. DNS management). |
| get-me-domainA | Fetch full details of a single owned domain by its Muumuu domain ID, including contract period, auto-renewal status, and nameserver configuration. |
| list-me-dns-recordsA | List DNS records for a specific owned domain (identified by domain ID). Supports filtering by record type or FQDN, with pagination. Read-only view of the authoritative zone. |
| list-me-dns-records-by-fqdnA | List DNS records by specifying the owning domain as an FQDN instead of an internal domain ID. Use this when the caller only knows the domain name (e.g. 'example.com') and not its Muumuu domain ID. |
| create-me-dns-recordA | Create a new DNS record on an owned domain. Changes take effect on Muumuu's authoritative nameservers. Mutating operation: confirm intent with the user before calling. |
| update-me-dns-recordA | Update the value or priority of an existing DNS record. |
| delete-me-dns-recordA | Permanently delete a DNS record from an owned domain. Destructive and NOT reversible — confirm with the user before calling. |
| quote-domain-purchaseA | Get a signed purchase quote for a domain before buying. Returns the final price, availability, credit-card registration state, and a short-lived |
| purchase-domainA | Execute a domain purchase using a |
| get-domain-purchase-statusA | Poll the progress of a domain purchase started by |
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 11 tools
Most tools target distinct resources (domains, DNS records, purchases), but `list-me-dns-records` and `list-me-dns-records-by-fqdn` are very similar, differing only in how the domain is identified. This could cause confusion but is mitigated by descriptions explaining the distinction.
Tool names use a consistent verb-hyphen-noun pattern (e.g., create-me-dns-record, list-me-domains) with a 'me' context prefix. The only minor inconsistency is `get-domain-purchase-status` lacking the 'me' prefix, and `search-domains` does not include 'me' either.
With 11 tools covering domain management, DNS records, and purchase workflow, the count is well-scoped for a domain registrar MCP server. Each tool feels necessary, and there are no redundant or extraneous tools.
The tool surface covers core domain lifecycle (search, quote, purchase, status poll, list owned) and DNS CRUD except for missing an explicit update for domain metadata (e.g., auto-renewal toggle). However, the DNS record tools are complete (create, list, update, delete).