
Namecheap Api Mcp
io.github.lanternrowPublished by GitHub account lanternrowv1.0.1Updated Oct 24, 2026
Namecheap API — domains, DNS, contacts, registrar lock, SSL listing, and pricing.
Overview
Lets an assistant read and safely reconfigure Namecheap domains, DNS records, nameservers, email forwarding, and registrar locks.
- What you can do
- Wraps the Namecheap API for domain administration. Read tools cover domain lists and details, availability and premium pricing checks, contacts, registrar lock status, DNS host records, nameservers, email forwarding, pricing, and SSL certificate listings. Safe-write tools replace DNS host records, switch to default or custom nameservers, set email forwarding, and lock or unlock a domain. It deliberately excludes anything that spends money or is irreversible.
- When to use it
- Useful when an assistant should inspect or adjust DNS, nameservers, forwarding, or registrar locks for domains held at Namecheap, or check availability and pricing. It is not intended for registration, renewal, transfers, SSL purchase, or account changes.
- Requirements
- Runs locally via npx or Node.js from the npm package namecheap-api-mcp. Requires Namecheap API access enabled, the environment variables NAMECHEAP_API_USER, NAMECHEAP_API_KEY, and NAMECHEAP_CLIENT_IP (a whitelisted public IPv4), plus optional NAMECHEAP_USERNAME and NAMECHEAP_ENVIRONMENT. Network access to the Namecheap API is needed.
Installation
In SourceWeft
- Open Namecheap Api Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
namecheap-api-mcp
MCP server for the Namecheap API — manage domains, DNS, contacts, registrar locks, and view SSL certificates and pricing, straight from your AI assistant.
Built for Claude Code and any MCP-compatible AI tool.
Part of The SEO Engine toolkit by Rex Jones — AI-powered SEO and social media tooling for agencies and businesses.
Safety model
This server ships read + safe-write tools only. It can read your account and change DNS / nameserver / forwarding / lock configuration (all reversible), but it deliberately excludes anything that spends money or is irreversible: no domain registration, renewal, reactivation, transfers, SSL purchase/activation, add-funds, or account/address mutation. You can fork and add those if you need them.
Quick start
1. Enable Namecheap API access
- Go to Profile → Tools → Namecheap API Access and toggle it ON. (Production access requires account eligibility: 20+ domains, OR a $50+ balance, OR $50+ lifetime spend.)
- Copy your API key.
- Whitelist the public IPv4 of the machine that will run this server (the API rejects any non-whitelisted IP with error
1011150).
2. Configure your MCP client
Option: clone and build
Then point your client at node /path/to/namecheap-api-mcp/dist/index.js. For local credentials you can keep a gitignored .env (copy .env.example) and launch with Node's native flag: node --env-file=.env dist/index.js.
Environment variables
Tools
Read
Safe writes (configuration only — no charges)
Notes & gotchas
set_dns_hostsis destructive by API design. Namecheap'ssetHostsdeletes every record not included in the call. Always read current records first (get_dns_hosts), merge your change, then send the complete set.- Errors return HTTP 200. The Namecheap API signals failure in the XML body (
Status="ERROR"), not the HTTP status. This server parses that and throws a real error with the Namecheap error number + message. - IPv4 only for the whitelisted client IP.
Security
- Credentials are read from environment variables only — never hard-coded, logged, or written to disk by this server.
- The API key travels in the query string (Namecheap's design); this server never logs the request URL or key, and error messages surface only the Namecheap error number and text.
License
MIT © Rex Jones
Source: README.md at commit 0c70f57
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.