# Name.com

> Register and manage Name.com domains via the official MCP, auto-generated from their OpenAPI.

[Canonical HTML page](https://top-mcps.com/mcp/name-com) · [server.json](https://top-mcps.com/mcp/name-com.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

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

```json
{
  "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}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

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

```shell
# 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
```

### Cursor — `.cursor/mcp.json`

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

```json
{
  "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}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

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

```jsonc
{
  "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}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "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}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "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}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "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}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

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

```shell
# ~/.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}" }
```

### Zed — `~/.config/zed/settings.json`

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

```jsonc
{
  "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}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

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.

```none

```

## At a glance

- **Maintainer:** Name.com
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** NAME_USERNAME, NAME_TOKEN, NAME_API_URL
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Name.com accounts
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-27
- **GitHub stars:** 2 (fetched 2026-06-02T11:55:52.226Z)
- **Score:** 57/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/namedotcom/namecom-mcp

## Quick answer

**What it does.** Dynamically creates MCP tools for every Name.com API endpoint: domain registration, DNS records, transfers, contacts, email and URL forwarding.

**Best for:**
- Sandbox-first registration flows
- DNS record CRUD
- Domain transfers
- Auto-generated coverage of every API endpoint
- Email and URL forwarding

**Not for:**
- Operations outside Name.com's API surface
- Bulk portfolio operations across multiple registrars
- Unattended production runs without flipping `NAME_API_URL`

## Description

The official Name.com MCP is auto-generated from their public OpenAPI — registration, DNS, transfers, email and URL forwarding. Defaults to the test environment so a misfire will not hit real domains or billing.

## Why it matters

Name.com is the only major registrar besides Cloudflare with a vendor-published MCP repo. The test-environment default is a strong safety stance that is rare among registrar tools.

## Key features

- Vendor-published MCP repo
- Auto-generated from Name.com OpenAPI
- Defaults to test environment (mcp.dev.name.com)
- `NAME_USERNAME` + `NAME_TOKEN` auth
- MIT, TypeScript

## FAQ

### 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.

### Why "auto-generated"?

Tools are derived from the Name.com OpenAPI spec at startup, so every documented endpoint is exposed without manual wrapping.

### Status?

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

## Changelog

- **2026-05-27** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-08-01** — Initial directory listing.