Will it touch my real domains?

Not by default — `NAME_API_URL` defaults to `https://mcp.dev.name.com` (test env). Set it to `https://mcp.name.com` to hit production.

How are the tools organised?

Eighteen grouped tools, each with an `operation` parameter. `ManageDomains` covers list, get, create, renew, search, check, setNameservers, setContacts, purchaseprivacy, getAuthCodeForDomain, getPricingForDomain and zoneCheck; `ManageDNS` covers list, get, create, update and delete; `ManageTransfers` covers list, get, create, cancel, getTransferEligibility, createInternalTransferIn and cancelOutboundTransfer. Earlier versions generated one tool per endpoint; v1.2 consolidated them, and the README still describes the old layout.

Can it register a domain?

Yes — `ManageDomains` with `operation: create`, which the server's own operation text says to use only when the user asks and after confirming contact details. Against the default test environment nothing is charged; against production the account is billed.

Marked experimental by Name.com — verify behaviour after upgrades.

Name.com

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

Score 53(?)Name.comMIT 2Verified Sep 29, 2026Top MCPs for Domains →

Install View on GitHub

Quick answer

What it does

Groups the Name.com API by resource: `ManageDomains` (list, get, create, renew, search, check, setNameservers, setContacts, purchaseprivacy, getAuthCodeForDomain, getPricingForDomain, zoneCheck), `ManageDNS` (list, get, create, update, delete), `ManageTransfers` (list, get, create, cancel, getTransferEligibility, createInternalTransferIn, cancelOutboundTransfer), `ManageDomainInfo` (TLD requirements and claims checks), `ManageOrders`, `ProcessRefund`, `CheckAccountBalance`, plus DNSSEC, email and URL forwarding, vanity nameservers and webhook tools.

Best for

Sandbox-first registration flows
DNS and DNSSEC management
Domain transfers in, with eligibility checks
TLD pricing and requirements lookups

Not for

Operations outside Name.com's API surface
Bulk portfolio operations across multiple registrars

Source: top-mcps.com/mcp/name-com — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "name-com": {
      "command": "npx",
      "args": [
        "-y",
        "namecom-mcp@latest"
      ],
      "env": {
        "NAME_USERNAME": "${NAME_USERNAME}",
        "NAME_TOKEN": "${NAME_TOKEN}",
        "NAME_API_URL": "${NAME_API_URL}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export NAME_USERNAME=your_name_com_username
# export NAME_TOKEN=your_name_com_token
# export NAME_API_URL=https://mcp.name.com
claude mcp add name-com -- npx -y namecom-mcp@latest

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "name-com": {
      "command": "npx",
      "args": [
        "-y",
        "namecom-mcp@latest"
      ],
      "env": {
        "NAME_USERNAME": "${NAME_USERNAME}",
        "NAME_TOKEN": "${NAME_TOKEN}",
        "NAME_API_URL": "${NAME_API_URL}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "name-com": {
      "command": "npx",
      "args": [
        "-y",
        "namecom-mcp@latest"
      ],
      "env": {
        "NAME_USERNAME": "${NAME_USERNAME}",
        "NAME_TOKEN": "${NAME_TOKEN}",
        "NAME_API_URL": "${NAME_API_URL}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "name-com": {
      "command": "npx",
      "args": [
        "-y",
        "namecom-mcp@latest"
      ],
      "env": {
        "NAME_USERNAME": "${NAME_USERNAME}",
        "NAME_TOKEN": "${NAME_TOKEN}",
        "NAME_API_URL": "${NAME_API_URL}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "name-com": {
      "command": "npx",
      "args": [
        "-y",
        "namecom-mcp@latest"
      ],
      "env": {
        "NAME_USERNAME": "${NAME_USERNAME}",
        "NAME_TOKEN": "${NAME_TOKEN}",
        "NAME_API_URL": "${NAME_API_URL}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "namecom-mcp@latest"
          ],
          "env": {
            "NAME_USERNAME": "${NAME_USERNAME}",
            "NAME_TOKEN": "${NAME_TOKEN}",
            "NAME_API_URL": "${NAME_API_URL}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.name-com]
command = "npx"
args = [
  "-y",
  "namecom-mcp@latest",
]
env = { NAME_USERNAME = "${NAME_USERNAME}", NAME_TOKEN = "${NAME_TOKEN}", NAME_API_URL = "${NAME_API_URL}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "name-com": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "namecom-mcp@latest"
        ]
      },
      "env": {
        "NAME_USERNAME": "${NAME_USERNAME}",
        "NAME_TOKEN": "${NAME_TOKEN}",
        "NAME_API_URL": "${NAME_API_URL}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

Name.com doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set NAME_USERNAME, NAME_TOKEN, NAME_API_URL in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tool	Description	Args	Side effects
`ManageDomains`	Domains on the account — operations: list, get, create (registers and bills), renew, search, check, setNameservers, setContacts, purchaseprivacy, getAuthCodeForDomain, getPricingForDomain, zoneCheck.	—	Write
`ManageDomainInfo`	TLD registration requirements (getRequirement, getTldRequirementsV2) and the claims check for a specific domain.	—	Read
`TldPriceList`	Price list per TLD and registration duration.	—	Read
`PremiumDomainLists`	Premium domain lists.	—	Read
`ManageDNS`	DNS records on a domain — operations: list, get, create, update, delete.	—	Write
`ManageDNSSECs`	DNSSEC DS records — operations: list, get, create, delete.	—	Write
`ManageVanityNameservers`	Vanity (glue) nameservers — operations: list, get, create, update, delete.	—	Write
`ManageTransfers`	Transfers in — operations: list, get, create (needs the auth code and purchase price), cancel, getTransferEligibility, createInternalTransferIn, cancelOutboundTransfer.	—	Write
`ManageOrders`	Orders on the account — operations: list, get.	—	Read
`ProcessRefund`	Refund an order or specific order items.	—	Write
`ManageEmailForwardings`	Email forwarding rules — operations: list, get, create, update, delete.	—	Write
`ManageURLForwardings`	URL forwarding rules — operations: list, get, create, update, delete.	—	Write
`ManageWebhookNotifications`	Webhook subscriptions — operations: list, create, modify, delete.	—	Write
`CheckAccountBalance`	Account balance.	—	Read
`Hello`	Connectivity check.	—	Read
`GetHelpResources`	Help resources for the server.	—	Read
`GetFeedbackLinks`	Feedback links.	—	Read
`GetTroubleshootingInfo`	Troubleshooting information for the server.	—	Read

Security & scope

Access scope: Read + write
Sandbox: Defaults to Name.com's test environment (mcp.dev.name.com). Production needs `NAME_API_URL=https://mcp.name.com` set on purpose.
Gotchas: The tools carry no top-level description on `tools/list`; each one's `operation` parameter holds the per-operation text. Clients that only show tool descriptions will show blanks.
`ManageDomains` with `operation: create` registers and bills the connected account, and `ManageTransfers` with `operation: create` starts a transfer that needs the losing registrar's auth code. Keep both behind a confirmation once you point at production.
Name.com marks the server experimental. Verify behaviour after upgrades — the tool layout changed between 1.1 and 1.2.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. domains work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-domains

Compare Name.com against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Name.com MCP vs [Cloudflare MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/name-com
- top-mcps.com listing for Cloudflare

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Name.com MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/name-com (fetch https://top-mcps.com/mcp/name-com.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (NAME_USERNAME, NAME_TOKEN, NAME_API_URL) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 3 updates tracked.

Sep 29, 2026
Entry re-verified by probe on v1.2.1: 18 grouped tools with an operation parameter, replacing the earlier one-tool-per-endpoint description.
Sep 14, 2026
v1.2.1 published to npm
Oct 3, 2025
v1.1.0 released — Release v1.1.0

At a glance

Maintainer: Name.com
Transport: stdio
Auth model: API key
Required secrets: NAME_USERNAMENAME_TOKENNAME_API_URL
Supported clients: ChatGPT
Claude Desktop
Claude Code
Cursor
VS Code
Windsurf
Cline
Continue
Zed
Codex CLI
License: MIT
Language: TypeScript
Latest version: latest
Last verified: Sep 29, 2026

GitHub repo

Rank badge

Maintainer of Name.com? Embed the live badge — it re-renders with the current rank and score on every catalog refresh.

[![Ranked #3 in Domains on Top-MCPs](https://top-mcps.com/badge/name-com.svg)](https://top-mcps.com/mcp/name-com)

Alternatives

Cloudflare →
Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.
GoDaddy →
Manage the largest consumer domain portfolio from inside ChatGPT — search, register, transfer, and DNS via OAuth.
Namecheap →
Search, register, and manage Namecheap domains from inside ChatGPT — OAuth install, no API key.
Porkbun →
At-cost registration and full DNS control from an agent — read-only until you explicitly turn writes on.
Hostinger →
Buy a domain, provision hosting, deploy a site, and set its DNS — one official server covering the whole chain, now through three search-and-execute tools.
Vercel (MCP server) →
Deploy from files or Git, buy and attach domains, edit DNS, and debug deployments on Vercel — the official remote MCP, over OAuth.

Related guides

More Domains MCPs

Other tools in the same category worth evaluating.

Cloudflare

Official

Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.

cloudflareedgeworkersdns

5 minMedium

Porkbun

At-cost registration and full DNS control from an agent — read-only until you explicitly turn writes on.

porkbundomainsregistrardns

5 minLow

Vercel (MCP server)

Official

Deploy from files or Git, buy and attach domains, edit DNS, and debug deployments on Vercel — the official remote MCP, over OAuth.

vercelhostingdeploymentdomains

5 minLow

Compared with Name.com

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Name.comvsCloudflare Name.comvsGoDaddy Name.comvsNamecheap Name.comvsPorkbun

Exploring Top MCPs for Domains? See all Domains MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

Will it touch my real domains?

How are the tools organised?

Can it register a domain?

Status?

What changed

More Domains MCPs

Cloudflare

Porkbun

Vercel (MCP server)

Compared with Name.com