namecheap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAMECHEAP_URL | No | Namecheap API URL. Defaults to https://api.namecheap.com/xml.response in Direct API mode. In Bearer Proxy mode, this is the proxy endpoint URL. | |
| NAMECHEAP_USER | No | Namecheap username. | |
| NAMECHEAP_TOKEN | No | Bearer token for the proxy. | |
| NAMECHEAP_API_KEY | No | Namecheap XML API key. | |
| NAMECHEAP_CLIENT_IP | No | Whitelisted client IPv4 address. |
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 |
|---|---|
| domainsB | Manage Namecheap domain portfolio, availability & pricing checks, registration, renewal, nameservers, contacts, transfer lock, and account balances. |
| dnsB | Read, add/update (safe read-merge-write), or delete DNS host records and email forwarding settings on a Namecheap domain. |
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 2 tools
The two tools target mostly distinct areas: domain portfolio/account/registration operations versus DNS records and email forwarding. There is minor boundary overlap around nameservers, which sit in the domains tool while DNS configuration is handled separately, but an agent can generally choose correctly.
Both names are concise, lowercase resource nouns following the same convention. The naming is predictable and easy to map to the server's domain.
Two broad tools can cover a lot of functionality, but the surface feels thin for full Namecheap domain and DNS lifecycle management. The tools are heavily aggregated, which may reduce discoverability and force agents to rely on long natural-language descriptions for action selection.
The set covers most core domain portfolio, registration, renewal, nameserver, contact, transfer-lock, balance, DNS record, and email-forwarding operations. Some lifecycle gaps remain, such as domain transfer initiation/status, privacy protection management, and DNSSEC controls.