Log inSubmit server
Namecheap API MCP logo

Namecheap API MCP

Manage Namecheap domains, DNS, forwarding, locks, contacts, SSL details, availability, and pricing through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Namecheap API MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "namecheap-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "namecheap-api-mcp"
      ],
      "env": {
        "NAMECHEAP_API_USER": "YOUR_VALUE_HERE",
        "NAMECHEAP_API_KEY": "YOUR_VALUE_HERE",
        "NAMECHEAP_CLIENT_IP": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

namecheap-api-mcp MCP server exposes Namecheap account, domain, DNS, forwarding, registrar-lock, SSL, and pricing operations as MCP tools. It runs through stdio with credentials and a whitelisted public IPv4 address supplied as environment variables, using either npx or a locally built Node.js entry point. Read operations cover account and domain data, while write operations change reversible configuration without handling purchases or other charged actions. Reach for it when an MCP-compatible client needs to inspect or update Namecheap-managed domains and DNS.

Use cases

  • Check domain availability and premium pricing
  • Inspect domain expiry, locks, and auto-renew settings
  • Read and update Namecheap DNS records
  • Manage email forwarding rules
  • Review SSL certificate status and expiry

Key features

  • Domain inventory and availability checks
  • DNS and nameserver inspection
  • Reversible DNS configuration writes
  • Email forwarding management
  • Registrar lock control
  • SSL certificate and pricing lookup

Tools16

What Namecheap API MCP lets your agent do. Expand a tool for its parameters.

Self-reported~258 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · namecheap-api-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads215Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Tools exposed16Callable tools this server registers over MCP.

How Namecheap API MCP works

What namecheap-api-mcp MCP server does

namecheap-api-mcp MCP server connects an MCP-compatible AI client to the Namecheap API. It provides account connection checks, domain inventory, individual domain details, availability checks, contacts, registrar-lock status, DNS records, nameservers, email forwarding, product pricing, and SSL certificate listings.

The server also exposes configuration changes for DNS hosts, nameservers, forwarding rules, and registrar locks. Its write surface is intentionally limited to configuration: it does not register or renew domains, reactivate domains, transfer domains, buy or activate SSL certificates, add funds, or modify account and address data.

How it works

The package communicates with Namecheap using the credentials and client IP supplied through environment variables. Namecheap requires the public IPv4 address running the server to be whitelisted, so the API access settings and runtime network location must match. The server parses Namecheap’s XML error responses and reports API error numbers and messages even when the HTTP response itself is successful.

Domain availability checks accept up to 50 domains in one request and can include premium pricing. Domain listings support pagination and search. Pricing results should be cached by the calling workflow when appropriate.

set_dns_hosts replaces the complete host-record collection rather than applying a single-record patch. Before using it, read the existing records, merge the intended change, and submit the full resulting set; records left out of the request are deleted.

Setup and configuration

Enable Namecheap API access under the account’s API Access settings, copy the API key, and whitelist the public IPv4 address of the machine that will run the process. Production API access also has Namecheap eligibility requirements: an account must have at least 20 domains, a balance of at least $50, or $50 in lifetime spending.

The standard launch configuration uses npx -y namecheap-api-mcp and sets NAMECHEAP_API_USER, NAMECHEAP_API_KEY, and NAMECHEAP_CLIENT_IP. NAMECHEAP_USERNAME is optional and defaults to the API user; it is relevant when using reseller sub-users. NAMECHEAP_ENVIRONMENT defaults to production and can be set to sandbox.

Alternatively, clone the repository, install dependencies, run the build, and point the client at dist/index.js. A local .env file can be used with Node’s native --env-file option. Credentials are read from environment variables and are not hard-coded, logged, or written to disk by the server.

Tools and capabilities

Read tools include:

  • check_connection for credential, whitelist, and balance verification.
  • list_domains and get_domain_info for domain inventory and details.
  • check_domains for availability and premium pricing.
  • get_domain_contacts, get_registrar_lock, and get_nameservers for account configuration data.
  • get_dns_hosts and get_email_forwarding for DNS and forwarding inspection.
  • get_pricing and list_ssl_certificates for product prices and certificate status.

Configuration tools include set_dns_hosts, set_default_dns, set_custom_nameservers, set_email_forwarding, and set_registrar_lock. These changes do not directly charge the account according to the documented safety model.

Limitations and notes

namecheap-api-mcp MCP server requires IPv4 for the whitelisted client address; IPv6 is not supported for this requirement. The Namecheap API places the key in the query string by design, but the server does not log request URLs or the key. Error output exposes only the Namecheap error number and message.

The server cannot perform purchases, registrations, renewals, transfers, reactivations, SSL activation, balance funding, or account/address mutations. Treat DNS replacement as destructive even though it is configuration-only: omitted records are removed by Namecheap. The API key should be treated as a secret and kept out of client configuration files that may be shared.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Namecheap API MCP

namecheap-api-mcp is an MCP server that connects AI clients to the Namecheap API for domain, DNS, contacts, registrar-lock, SSL, and pricing operations. Its main tools check connections, list and inspect domains, manage DNS and forwarding configuration, control registrar locks, and retrieve certificate and product details.

Install it by configuring your MCP client to run `npx -y namecheap-api-mcp`, or clone the repository, run `npm install`, and build it with `npm run build`. Set the required environment variables and point a local client at `dist/index.js` when using the cloned package.

It requires `NAMECHEAP_API_USER`, `NAMECHEAP_API_KEY`, and `NAMECHEAP_CLIENT_IP`. The first two identify the Namecheap API account and key; the third must be the machine’s whitelisted public IPv4 address. `NAMECHEAP_USERNAME` and `NAMECHEAP_ENVIRONMENT` are optional.

It can change DNS configuration, but `set_dns_hosts` replaces all records for the domain. Read the current records with `get_dns_hosts`, merge the desired change, and submit the complete record set because omitted records are deleted.

Yes. The README identifies Claude Code as a supported use case, and the server is designed for MCP-compatible AI tools. Configure Claude Code to launch the package with `npx` and provide the required Namecheap environment variables.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNamecheap API MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/namecheap-api-mcp?style=directory)](https://allmcps.com/mcp/namecheap-api-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/namecheap-api-mcp"><img src="https://allmcps.com/api/badge/namecheap-api-mcp?style=directory" alt="Namecheap API MCP on AllMCPs" /></a>