Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Namecheap API MCP

by lanternrowversion 1.0.1i★ –iRuns on your computer
Registry nameio.github.lanternrow/namecheap-api-mcp

Install

Overview

Description from the maker (original English)

Namecheap API — domains, DNS, contacts, registrar lock, SSL listing, and pricing.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: NAMECHEAP_API_USER, NAMECHEAP_API_KEY, NAMECHEAP_CLIENT_IP

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: NAMECHEAP_API_USER, NAMECHEAP_API_KEY, NAMECHEAP_CLIENT_IP, NAMECHEAP_USERNAME, NAMECHEAP_ENVIRONMENT

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "namecheap-api": {
      "command": "npx",
      "args": [
        "-y",
        "namecheap-api-mcp"
      ],
      "env": {
        "NAMECHEAP_API_USER": "your-value",
        "NAMECHEAP_API_KEY": "your-value",
        "NAMECHEAP_CLIENT_IP": "your-value",
        "NAMECHEAP_USERNAME": "your-value",
        "NAMECHEAP_ENVIRONMENT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add namecheap-api --env NAMECHEAP_API_USER=your-value --env NAMECHEAP_API_KEY=your-value --env NAMECHEAP_CLIENT_IP=your-value --env NAMECHEAP_USERNAME=your-value --env NAMECHEAP_ENVIRONMENT=your-value -- npx -y namecheap-api-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "namecheap-api": {
      "command": "npx",
      "args": [
        "-y",
        "namecheap-api-mcp"
      ],
      "env": {
        "NAMECHEAP_API_USER": "your-value",
        "NAMECHEAP_API_KEY": "your-value",
        "NAMECHEAP_CLIENT_IP": "your-value",
        "NAMECHEAP_USERNAME": "your-value",
        "NAMECHEAP_ENVIRONMENT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "namecheap-api": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "namecheap-api-mcp"
      ],
      "env": {
        "NAMECHEAP_API_USER": "your-value",
        "NAMECHEAP_API_KEY": "your-value",
        "NAMECHEAP_CLIENT_IP": "your-value",
        "NAMECHEAP_USERNAME": "your-value",
        "NAMECHEAP_ENVIRONMENT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • NAMECHEAP_API_USER required env
    Namecheap account username (API user)
  • NAMECHEAP_API_KEY secret required env
    Namecheap API key from Profile -> Tools -> API Access
  • NAMECHEAP_CLIENT_IP required env
    Whitelisted public IPv4 of the machine running this server
  • NAMECHEAP_USERNAME env
    Username a command runs on behalf of. Defaults to NAMECHEAP_API_USER; differs only for reseller sub-users.
  • NAMECHEAP_ENVIRONMENT env
    API environment: "production" (default) or "sandbox"

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account lanternrow, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32509 servers in this category
  • Published to the registry more recently than 15% of the other 32509 servers in this category
  • Basic checks equal to or better than 100% of the other 32509 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Namecheap API MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: NAMECHEAP_API_USER, NAMECHEAP_API_KEY, NAMECHEAP_CLIENT_IP

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Fomu MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Fomu MCP

by gabrielmahia

Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

namecheap-api-mcp

MCP server for the [Namecheap API](https://www.namecheap.com/support/api/intro/) — 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](https://lanternrow.com/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
  1. Go to Profile → Tools → [Namecheap API Access](https://ap.www.namecheap.com/settings/tools/apiaccess/) and toggle it ON. (Production access requires account eligibility: 20+ domains, OR a $50+ balance, OR $50+ lifetime spend.)
  2. Copy your API key.
  3. 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
{

"mcpServers": { "namecheap": { "command": "npx", "args": ["-y", "namecheap-api-mcp"], "env": { "NAMECHEAP_API_USER": "your_username", "NAMECHEAP_API_KEY": "your_api_key", "NAMECHEAP_CLIENT_IP": "your.whitelisted.ip.v4" } } } }

Option: clone and build
git clone https://github.com/lanternrow/namecheap-api-mcp.git

cd namecheap-api-mcp npm install npm run 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

VariableRequiredDescription
NAMECHEAP_API_USERYesYour Namecheap account username (API user).
NAMECHEAP_API_KEYYesAPI key from Profile → Tools → API Access. Secret.
NAMECHEAP_CLIENT_IPYesThe whitelisted public IPv4 of this machine.
NAMECHEAP_USERNAMENoDefaults to NAMECHEAP_API_USER; differs only for reseller sub-users.
NAMECHEAP_ENVIRONMENTNoproduction (default) or sandbox.

Tools

Read
ToolDescription
check_connectionVerify credentials + IP whitelist; returns the account balance summary.
list_domainsList domains with expiry, lock, auto-renew, and WhoisGuard status (paged/searchable).
get_domain_infoDetailed info for one domain.
check_domainsCheck availability + premium pricing (up to 50 at once).
get_domain_contactsRegistrant / Tech / Admin / AuxBilling contacts.
get_registrar_lockRegistrar lock status.
get_dns_hostsAll DNS host records for a domain.
get_nameserversNameservers and whether Namecheap DNS is in use.
get_email_forwardingEmail forwarding rules.
get_pricingNamecheap pricing for a product type (cache the results).
list_ssl_certificatesSSL certificates with type, host, status, expiry.
Safe writes (configuration only — no charges)
ToolDescription
set_dns_hostsReplace all host records (destructive: omitted records are deleted — send the full set).
set_default_dnsSwitch a domain to Namecheap's default nameservers.
set_custom_nameserversPoint a domain at custom nameservers.
set_email_forwardingSet email forwarding rules.
set_registrar_lockLock / unlock a domain at the registrar.

Notes & gotchas

  • `set_dns_hosts` is destructive by API design. Namecheap's setHosts deletes 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

Ask PopNx