namecheap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAMECHEAP_API_KEY | Yes | API key from Namecheap API Access | |
| NAMECHEAP_SANDBOX | No | Set to 'true' to use sandbox API (optional) | |
| NAMECHEAP_API_USER | Yes | Your Namecheap username | |
| NAMECHEAP_USERNAME | No | Account username if different from API user (optional) | |
| NAMECHEAP_CLIENT_IP | Yes | Whitelisted public IP 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setupA | Configure namecheap-mcp with your Namecheap API credentials. Credentials are saved to ~/.config/namecheap-mcp/.env on your local machine. Run this if other tools report that the server is not configured. |
| auth_statusA | Report the current authentication status of namecheap-mcp: whether credentials are loaded, whether they were accepted by the Namecheap API, where each credential came from (shell env vs config file), and the last error if any. Call this when tools are failing to diagnose whether the problem is a missing config, an unwhitelisted IP, a stale shell export shadowing the config file, or an invalid API key. |
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
auth_status and setup have completely distinct purposes: one checks authentication status, the other configures credentials. No overlap whatsoever.
Both tool names follow the snake_case convention consistently, with clear verbs (auth, setup) and nouns (status).
With only 2 tools, the server is severely under-scoped for a Namecheap API. It lacks essential domain and DNS management tools, making it nearly unusable for actual tasks.
The tool surface covers only authentication setup and status checking, missing all core Namecheap operations like listing domains, managing DNS records, or purchasing services.