Manage domains and DNS records through the Name.com REST API
namecom-mcp
MCP server for the name.com REST API v4. Provides 8 tools for domain search, availability checking, DNS record management, and nameserver configuration.
Tools
| Tool | Description |
|---|---|
namecom_search |
Search for available domains by keyword, optionally filtered by TLD |
namecom_check_availability |
Bulk-check up to 50 specific domain names |
namecom_list_domains |
List all domains in your account |
namecom_get_domain |
Get full details for a specific domain |
namecom_list_records |
List DNS records for a domain |
namecom_create_record |
Create a DNS record (A, AAAA, CNAME, MX, TXT, NS, SRV) |
namecom_delete_record |
Delete a DNS record by ID |
namecom_set_nameservers |
Set custom nameservers for a domain |
Setup
1. Get API credentials
- Log into name.com
- Go to Account > API Settings (or https://www.name.com/account/settings/api)
- Generate a new API token
- Note your username and the generated token
2. Install
cd /path/to/namecom-mcp
npm install
3. Add to Claude Code
Add the following to your Claude Code MCP configuration file (~/.claude/claude_desktop_config.json or the Claude Code settings):
{
"mcpServers": {
"namecom": {
"command": "node",
"args": ["/absolute/path/to/namecom-mcp/src/index.js"],
"env": {
"NAMECOM_USERNAME": "your-namecom-username",
"NAMECOM_TOKEN": "your-api-token"
}
}
}
}
Replace /absolute/path/to/namecom-mcp with the actual path where you cloned/installed this server.
On Windows with WSL or Git Bash you may need to adjust the path format.
4. Restart Claude Code
After saving the config, restart Claude Code. You should see the namecom tools available.
Rate Limits
name.com enforces: 20 requests/second, 3000 requests/hour. The server does not implement client-side rate limiting — avoid bulk operations in tight loops.
Environment Variables
| Variable | Required | Description |
|---|---|---|
NAMECOM_USERNAME |
Yes | Your name.com account username |
NAMECOM_TOKEN |
Yes | Your name.com API token |
The server will exit with an error message if either variable is missing.
Example Usage (in Claude)
Search for available domains for a baby product startup:
namecom_search keyword="babyzen" tldFilter=["com","io","co"]
Check if specific domains are available:
namecom_check_availability domainNames=["babyzen.com","babyzen.io","babyzen.co"]
List all my domains:
namecom_list_domains
Add a CNAME record pointing www to Vercel:
namecom_create_record domainName="example.com" host="www" type="CNAME" answer="cname.vercel-dns.com"
Point a domain to Cloudflare nameservers:
namecom_set_nameservers domainName="example.com" nameservers=["ns1.cloudflare.com","ns2.cloudflare.com"]
API Reference
- name.com API v4 docs
- Base URL:
https://api.name.com - Auth: HTTP Basic (username:token)
Tools (8)
namecom_searchSearch for available domains by keyword, optionally filtered by TLDnamecom_check_availabilityBulk-check up to 50 specific domain namesnamecom_list_domainsList all domains in your accountnamecom_get_domainGet full details for a specific domainnamecom_list_recordsList DNS records for a domainnamecom_create_recordCreate a DNS record (A, AAAA, CNAME, MX, TXT, NS, SRV)namecom_delete_recordDelete a DNS record by IDnamecom_set_nameserversSet custom nameservers for a domainEnvironment Variables
NAMECOM_USERNAMErequiredYour name.com account usernameNAMECOM_TOKENrequiredYour name.com API tokenConfiguration
{"mcpServers": {"namecom": {"command": "node", "args": ["/absolute/path/to/namecom-mcp/src/index.js"], "env": {"NAMECOM_USERNAME": "your-namecom-username", "NAMECOM_TOKEN": "your-api-token"}}}}