Namecheap API MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 78 installs a week from npm. Last commit 29 Jun 2026.
Namecheap API — domains, DNS, contacts, registrar lock, SSL listing, and pricing.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const run = (cmd) => execSync(cmd, { stdio: "inherit" });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add namecheap-api-mcp -e 'NAMECHEAP_API_USER=<NAMECHEAP_API_USER>' -e 'NAMECHEAP_API_KEY=<NAMECHEAP_API_KEY>' -e 'NAMECHEAP_CLIENT_IP=<NAMECHEAP_CLIENT_IP>' -- npx -y namecheap-api-mcp{
"mcpServers": {
"namecheap-api-mcp": {
"command": "npx",
"args": [
"-y",
"namecheap-api-mcp"
],
"env": {
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>",
"NAMECHEAP_API_USER": "<NAMECHEAP_API_USER>",
"NAMECHEAP_CLIENT_IP": "<NAMECHEAP_CLIENT_IP>"
}
}
}
}[mcp_servers.namecheap-api-mcp]
command = "npx"
args = ["-y", "namecheap-api-mcp"]
env = { NAMECHEAP_API_USER = "<NAMECHEAP_API_USER>", NAMECHEAP_API_KEY = "<NAMECHEAP_API_KEY>", NAMECHEAP_CLIENT_IP = "<NAMECHEAP_CLIENT_IP>" }{
"mcpServers": {
"namecheap-api-mcp": {
"command": "npx",
"args": [
"-y",
"namecheap-api-mcp"
],
"env": {
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>",
"NAMECHEAP_API_USER": "<NAMECHEAP_API_USER>",
"NAMECHEAP_CLIENT_IP": "<NAMECHEAP_CLIENT_IP>"
}
}
}
}{
"servers": {
"namecheap-api-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"namecheap-api-mcp"
],
"env": {
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>",
"NAMECHEAP_API_USER": "<NAMECHEAP_API_USER>",
"NAMECHEAP_CLIENT_IP": "<NAMECHEAP_CLIENT_IP>"
}
}
}
}Put your own values in place of
<NAMECHEAP_API_USER> (Namecheap account username (API user)), <NAMECHEAP_API_KEY> (Namecheap API key from Profile -> Tools -> API Access), <NAMECHEAP_CLIENT_IP> (Whitelisted public IPv4 of the machine running this server).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
NAMECHEAP_USERNAME (Username a command runs on behalf of. Defaults to NAMECHEAP_API_USER; differs only for reseller sub-users), NAMECHEAP_ENVIRONMENT (API environment: "production" (default) or "sandbox").
Alternatives to Namecheap API MCP
same job, measured the same wayMCP server for Namecheap — check availability, list domains, and get pricing
Manage domains, DNS records, contacts, marketplace listings, and more via the Spaceship API
Check domain availability and live registry pricing, or search for available names.
MCP server for DNSimple — domains, DNS zone records, availability, pricing and contacts.
Tech stack, WHOIS, DNS, SSL, hosting and SEO checks for lists of domains.
Domain availability and prices from 40+ registrars, name checks, DNS setup, and a domain broker
Domain registrar for AI agents. Search, register, and manage domains via API.
Check domain availability across 600+ TLDs on Namecheap with pricing and purchase links
Namecheap API MCP — questions
Answers built from our own checks of this server.