namecom-mcp
Advanced tools
A Model Context Protocol (MCP) server for Name.com API integration, providing AI assistants with domain management capabilities
A Model Context Protocol (MCP) server that provides access to the complete Name.com API for domain management operations. This server automatically generates tools from the Name.com OpenAPI specification, giving AI assistants access to all Name.com API functions including domain registration, DNS management, transfers, email forwarding, URL forwarding, and more.
⚠️ Experimental Tool: This MCP server is currently experimental and defaults to Name.com's test environment (
mcp.dev.name.com) which requires test environment credentials. While you can configure it to use the production environment, we recommend using the test environment for initial experimentation.
This MCP server works with any AI tool that supports the Model Context Protocol (MCP). You can use it for domain management tasks through natural conversation with your preferred AI assistant. The server dynamically creates tools for every available Name.com API endpoint, so you have access to the full range of domain management capabilities.
Step 1: Install the package
npm install -g namecom-mcp
Step 2: Choose your configuration method
The npm install command installed the Name.com MCP server on your computer. Now your AI tool needs to know where to find it and how to authenticate with Name.com. Choose one of the following configuration methods:
This approach uses Name.com's test environment by default. To get started, add the configuration below to your AI tool's MCP config file. Instructions for locating the MCP config files for a few common AI tools are provided after the configuration examples.
{
"mcpServers": {
"namecom": {
"command": "namecom-mcp",
"env": {
"NAME_USERNAME": "your-test-username",
"NAME_TOKEN": "your-test-token"
}
}
}
}
For production environment (advanced), add the API URL:
{
"mcpServers": {
"namecom": {
"command": "namecom-mcp",
"env": {
"NAME_USERNAME": "your-prod-username",
"NAME_TOKEN": "your-prod-token",
"NAME_API_URL": "https://mcp.name.com"
}
}
}
}
⚠️ Production Warning: This will affect your real Name.com account and may incur charges. See Environment Details for credential requirements.
Important: Use the right credentials for your environment - test credentials for test environment, production credentials for production.
How to add this configuration to your tool:
Cursor:
Claude Desktop:
Other MCP-Compatible Tools: This server is designed to work with any MCP-compatible tool. Check your tool's documentation for MCP configuration steps, as the exact process varies by tool.
📖 Note: The steps above may change as tools update. Please check the official documentation for Claude Desktop and Cursor if these steps don't match, and report any outdated instructions.
🔄 Important: Restart your AI tool after configuration changes if you experience connection issues.
Use this method if:
Create a .env file in your working directory:
# For test environment (default)
NAME_USERNAME=your-test-username
NAME_TOKEN=your-test-token
# For production environment (advanced)
# NAME_USERNAME=your-prod-username
# NAME_TOKEN=your-prod-token
# NAME_API_URL=https://mcp.name.com
Important: Make sure to use the correct credentials for your chosen environment - test credentials for test environment, production credentials for production environment.
Step 3: You're done! 🎉
Start your AI tool and begin asking domain-related questions. Your AI assistant will automatically use the Name.com tools when needed.
What each setting does:
"namecom": The name for this MCP server (you can change this)"command": "namecom-mcp": Tells your AI tool to run the package you installed"NAME_USERNAME": Your Name.com API username (test credentials recommended)"NAME_TOKEN": Your Name.com API token (test credentials recommended)"NAME_API_URL": "https://mcp.name.com" for production environmentCongratulations! Your Name.com MCP server is now configured and ready to use with your AI assistant.
Start your AI tool and ask: "Can you check if example.com is available?"
If your AI assistant responds and searches for domains, you're all set! 🎉
What you can do now:
Now that you're set up, here's what you can do:
Ask your AI assistant:
"Can you search for available domains with 'myawesomeproject' in the name?"
Your AI assistant will:
Other things to try:
Understanding the different Name.com environments and their credentials:
https://mcp.dev.name.com (default)https://mcp.name.com (set NAME_API_URL=https://mcp.name.com)Critical: Make sure your credentials match your environment:
mcp.dev.name.com) → Test credentialsmcp.name.com) → Production credentialsUsing wrong credentials will result in authentication errors.
If you need to generate new API credentials or want to understand the different environments:
IMPORTANT: Name.com provides different credentials for test vs production environments. Make sure you're using the correct credentials for your chosen environment.
mcp.dev.name.commcp.name.comThe following section is for testing and troubleshooting your setup. If everything is working with your AI assistant, you can skip this section.
Start your AI tool and try these questions:
Your AI tool will request permission to use Name.com tools, and the conversation should flow naturally.
The MCP Inspector is excellent for testing and troubleshooting your MCP server setup if you're experiencing issues.
Install the MCP Inspector (if not already installed):
npm install -g @modelcontextprotocol/inspector
Run the Inspector with your credentials:
NAME_USERNAME=your-test-username NAME_TOKEN=your-test-token npx @modelcontextprotocol/inspector namecom-mcp
For production environment (advanced):
NAME_USERNAME=your-prod-username NAME_TOKEN=your-prod-token NAME_API_URL=https://mcp.name.com npx @modelcontextprotocol/inspector namecom-mcp
Open the Inspector:
http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=...)Test the Connection:
Authentication Errors:
NAME_USERNAME and NAME_TOKEN are correctAPI URL Issues: The tool defaults to test environment (mcp.dev.name.com)
Tool Generation Fails: The server will fall back to basic tools if OpenAPI spec loading fails
Package Not Found:
npm install -g namecom-mcpnpm uninstall -g namecom-mcp && npm install -g namecom-mcpMCP Configuration Issues:
namecom-mcp (no npx needed)MCP Inspector Connection Issues:
NAME_USERNAME=your-username NAME_TOKEN=your-token npx @modelcontextprotocol/inspector namecom-mcpFor npm installation or permission issues, see the official documentation:
If you run into issues:
For Name.com account or API issues:
Q: What AI tools work with this? A: Any tool that supports MCP - Claude Desktop, Cursor, Continue, and many others.
Q: Is it safe to test? A: Yes! The default test environment won't affect real domains or billing.
Q: Can I use this with production domains?
A: Yes, set NAME_API_URL=https://mcp.name.com and use production credentials. ⚠️ This will affect your real account and may incur charges.
Q: Why am I getting authentication errors? A: Usually mismatched credentials - test credentials work with test environment, production credentials with production environment. See Environment Details for credential requirements.
Q: How much does it cost? A: The MCP server is free. You only pay for actual Name.com services you use.
Q: Does it work offline? A: No, it needs internet access to communicate with Name.com's API.
This server is part of the growing Model Context Protocol ecosystem. The MCP is rapidly gaining adoption across AI tools, and this Name.com server works with any MCP-compatible tool, giving you flexibility in choosing your preferred AI assistant for domain management tasks.
Related MCP Resources:
MIT License - see LICENSE file for details.
See the GitHub Releases page for version history and updates.
FAQs
A Model Context Protocol (MCP) server for Name.com API integration, providing AI assistants with domain management capabilities
The npm package namecom-mcp receives a total of 213 weekly downloads. As such, namecom-mcp popularity was classified as not popular.
We found that namecom-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
ECMAScript 2025 introduces Iterator Helpers, Set methods, JSON modules, and more in its latest spec update approved by Ecma in June 2025.
Security News
A new Node.js homepage button linking to paid support for EOL versions has sparked a heated discussion among contributors and the wider community.
Research
North Korean threat actors linked to the Contagious Interview campaign return with 35 new malicious npm packages using a stealthy multi-stage malware loader.