namecheap_get_domain_listLABSCO SUMMARY
Three domain operations, and the risky fourth is missing on purpose.
Leaving registration out is a design decision rather than an omission, and the per-tool switches let you go further — turn off namecheap_set_custom_dns and the agent can look but not touch. The real gate is upstream: Namecheap's API eligibility rules mean most personal accounts cannot use this at all.
What it is
An MCP server over the Namecheap API covering three domain operations. The author kept it to what he uses and left registration out on purpose, on the view that an agent should not be buying domains.
What you get
namecheap_get_domain_list— every domain on the account with expiry dates, auto-renewal status and DNS configuration; takes no parametersnamecheap_check_domain_availability— pass an array ofdomainsand get availability for eachnamecheap_set_custom_dns— set 1 to 12 nameservers on adomain; note that URL forwarding, email forwarding and dynamic DNS stop working once custom nameservers are in place- Each tool can be switched off independently with
NAMECHEAP_ENABLE_GETLIST,NAMECHEAP_ENABLE_CHECKandNAMECHEAP_ENABLE_SETCUSTOM NAMECHEAP_SANDBOX=truepoints everything at Namecheap's sandbox for testing
Requirements
Namecheap API access, which the registrar only grants to accounts holding at least 20 domains, with $50 on the balance and $50 spent in the last 2 years — check that before anything else. Then enable API access in the dashboard, get your key, and whitelist your IP. Four variables are required: NAMECHEAP_API_USER, NAMECHEAP_API_KEY, NAMECHEAP_USERNAME and NAMECHEAP_CLIENT_IP, which must be the whitelisted address. Clone, npm install, npm run build, then register node dist/index.js. Package version 1.0.0. MIT.
Setup effort
Build from source — git clone https://github.com/johnsorrentino/mcp-namecheap.git
USE CASES
01
Seeing which domains are about to expire
Pull the full domain list with expiry dates and auto-renew status and let the model flag what needs attention.
02
Testing a batch of name ideas
Check a list of candidate domains for availability in one call rather than one search box at a time.
03
Pointing a domain at a new host
Set the nameservers for the domain, knowing forwarding services stop working once you do.
3 tools
Listed in project docs. Your client may show a different list.
namecheap_check_domain_availabilitynamecheap_set_custom_dnsBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- node on PATH
- NAMECHEAP_API_KEY in your environment
- NAMECHEAP_API_USER in your environment
- NAMECHEAP_USERNAME in your environment
- NAMECHEAP_CLIENT_IP in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/johnsorrentino/mcp-namecheap.git
cd mcp-namecheap
npm install
npm run buildMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"namecheap": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_NAMECHEAP>/dist/index.js"
],
"env": {
"NAMECHEAP_API_USER": "<YOUR_NAMECHEAP_API_USER>",
"NAMECHEAP_API_KEY": "<YOUR_NAMECHEAP_API_KEY>",
"NAMECHEAP_USERNAME": "<YOUR_NAMECHEAP_USERNAME>",
"NAMECHEAP_CLIENT_IP": "<YOUR_NAMECHEAP_CLIENT_IP>"
}
}
}
}<YOUR_PATH_TO_MCP_NAMECHEAP> is the full path of your clone (dist/index.js exists after npm run build), and <YOUR_NAMECHEAP_CLIENT_IP> the IP address you whitelisted in the Namecheap dashboard.
