name.com MCP Server

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.

Features

• 🔄 Complete API Access: Dynamically creates tools for every name.com API endpoint
• 🛡️ Secure Authentication: Uses name.com API credentials with proper authentication
• 🔧 Easy Integration: Simple configuration with popular AI tools
• 🧪 Safe Testing: Defaults to test environment for experimentation
• 🤖 AI-First Design: Built specifically for natural language interaction via MCP
• 🆘 Built-in Help: Ask your AI assistant for help, troubleshooting, and documentation links

Quick Start

Prerequisites

• An AI Tool that supports MCP:
  • Cursor
  • Claude Desktop
  • Other MCP-compatible tools (check their documentation)
• name.com Account with API credentials (sign up free | help getting credentials)

Setup

Simply copy and paste this configuration into your AI tool's MCP config file. This uses name.com's test environment by default, which is perfect for trying things out safely.

{
  "mcpServers": {
    "namecom": {
      "command": "npx",
      "args": ["-y", "namecom-mcp@latest"],
      "env": {
        "NAME_USERNAME": "your-test-username",  // Replace with your test username
        "NAME_TOKEN": "your-test-token"         // Replace with your test api token
      }
    }
  }
}

Important: Replace your-test-username and your-test-token with your actual test environment credentials from name.com. Don't know where to get these? See getting credentials.

For production environment (advanced), just add the API URL:

{
  "mcpServers": {
    "namecom": {
      "command": "npx",
      "args": ["-y", "namecom-mcp@latest"],
      "env": {
        "NAME_USERNAME": "your-prod-username",  // Replace with your production username
        "NAME_TOKEN": "your-prod-token",        // Replace with your production api token
        "NAME_API_URL": "https://mcp.name.com"
      }
    }
  }
}

Important: Replace your-prod-username and your-prod-token with your actual production credentials. These affect your real name.com account and can incur charges!

⚠️ Production Warning: This will affect your real name.com account and may incur charges. See Environment Details for credential requirements.

How to add this configuration to your tool:

Cursor:

1. Open Cursor → Press Cmd+Shift+J (Mac) or Ctrl+Shift+J (Windows)
2. Go to Tools & Integrations → MCP Tools → Add New
3. Add the configuration above → Save and restart Cursor

Claude Desktop:

1. Open Claude Desktop Settings → Developer → Edit Config
2. Add the configuration above → Save and restart 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.

Understanding the Configuration

What each setting does:

• "namecom": The name for this MCP server (you can change this)
• "command": "npx": Uses npx to automatically download and run the latest version
• "args": ["-y", "namecom-mcp@latest"]: Runs the latest version without prompts
• "NAME_USERNAME": Your name.com API username (test credentials recommended)
• "NAME_TOKEN": Your name.com API token (test credentials recommended)
• Optional: Add "NAME_API_URL": "https://mcp.name.com" for production environment

✅ Setup Complete - You're Ready to Go!

Congratulations! Your name.com MCP server is now configured and ready to use with your AI assistant.

Quick Test

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:

• Begin asking any domain-related questions in natural language
• Your AI assistant will automatically use the name.com tools when needed

🚀 Quick Example

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:

1. Ask permission to use the domain search tool
2. Search name.com's test environment safely
3. Show you available options with pricing
4. Help you register if you want (in test mode)

Other things to try:

• "List my current domains"
• "Show me DNS records for my domain"
• "Help me register a new domain"
• "Check if example.com is available"

Environment Details

Understanding the different name.com environments and their credentials:

Test Environment (Default - Recommended)

• URL: https://mcp.dev.name.com (default)
• Credentials: Use your test username and token from name.com
• Safety: Operations won't affect real domains or billing
• Purpose: Safe experimentation and testing

Production Environment (Advanced)

• URL: https://mcp.name.com (set NAME_API_URL=https://mcp.name.com)
• Credentials: Use your production username and token from name.com
• **⚠️ DANGER: All operations affect your real name.com account and domains
• Billing: Domain registrations and services will incur real charges
• Purpose: Live domain management

Credential Matching

Critical: Make sure your credentials match your environment:

• Test environment (mcp.dev.name.com) → Test credentials
• Production environment (mcp.name.com) → Production credentials

Using wrong credentials will result in authentication errors.

Getting name.com API Credentials

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.

1. Log in to your name.com account
2. Go to Account Settings > API Tokens
3. Generate an API token
4. Note: When you generate a token, name.com provides:
   • Test credentials (username/token) for mcp.dev.name.com
   • Production credentials (username/token) for mcp.name.com
5. Copy the correct username and token for the environment you plan to use

Testing & Debugging (Optional)

The following section is for testing and troubleshooting your setup. If everything is working with your AI assistant, you can skip this section.

Basic Testing

Start your AI tool and try these questions:

• "Can you list my domains?"
• "Search for available domains with the name 'example'"
• "Show me the DNS records for my domain"
• "Help me register a new domain"

Your AI tool will request permission to use name.com tools, and the conversation should flow naturally.

---

Advanced Debugging: MCP Inspector

The MCP Inspector is excellent for testing and troubleshooting your MCP server setup if you're experiencing issues.

1. Install the MCP Inspector (if not already installed):

   npm install -g @modelcontextprotocol/inspector
   

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

3. Open the Inspector:

   • The command will output a local URL with an auth token (e.g., http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=...)
   • Open this URL in your browser

4. Test the Connection:

   • Click "Connect" in the left sidebar
   • Once connected, click "List Tools" in the center to see all available name.com API tools
   • Select any tool to test that the endpoints are working through the MCP server
   • If you dont see any errors, but only a couple tools show up, there may have been an issue parsing the OpenAPI spec on startup. Please report this issue.

Security & Performance

• API Token Security: Treat your name.com API token like a password
• Safe Testing: Default test environment provides safe experimentation
• Least Privilege: The server only accesses name.com APIs with the permissions of your API token
• Input Validation: All inputs are validated using Zod schemas
• Error Handling: Errors are handled gracefully without exposing sensitive information
• API Rate Limits: Respects name.com's standard rate limits
• Fast Startup: Tool generation takes ~2-3 seconds on first startup

Troubleshooting

Common Issues

1. Authentication Errors:

   • Verify your NAME_USERNAME and NAME_TOKEN are correct
   • Most Common: Make sure you're using the correct credentials for your environment (see Environment Details)
   • Need new credentials? Get them here

2. API URL Issues: The tool defaults to test environment (mcp.dev.name.com)

3. Tool Generation Fails: The server will fall back to basic tools if OpenAPI spec loading fails

4. First Run Delay:

   • The first run might take a few seconds as npx downloads the package
   • Subsequent runs will be faster due to npm's cache
   • If you see "Installing package..." messages, this is normal for the first run

5. MCP Configuration Issues:

   • Check your MCP config file path and JSON syntax
   • Restart your AI tool (like Claude Desktop) after configuration changes
   • Make sure the args array includes both -y and the package name

6. MCP Inspector Connection Issues:

   # For test environment:
   NAME_USERNAME=your-username NAME_TOKEN=your-token npx @modelcontextprotocol/inspector npx -y namecom-mcp@latest
   
   # For production:
   NAME_USERNAME=your-username NAME_TOKEN=your-token NAME_API_URL=https://mcp.name.com npx @modelcontextprotocol/inspector npx -y namecom-mcp@latest
   

Getting Help

If you run into issues:

1. Check the troubleshooting section above
2. Test with the MCP Inspector first to isolate configuration issues
3. Verify your credentials work with name.com's API directly
4. Check GitHub Issues for known issues
5. Report bugs or request features on GitHub Issues
6. General feedback: name.com API Feedback

For name.com account or API issues:

• name.com Support - Account and billing support
• name.com API Documentation - API reference and guides

FAQ

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: Will npx always download the package? A: No, npm caches the package locally. Only the first run or when a new version is available will require a download.

Q: Do I need to install anything besides my AI tool? A: No! Tools like Cursor and Claude Desktop include everything needed. Just install your preferred AI tool and you're ready to go.

Q: What if I see "command not found: npx" or similar errors? A: This usually means your AI tool isn't properly installed. Try reinstalling your AI tool (Cursor, Claude Desktop, etc.) and make sure to let it complete its setup process.

Q: Why does the first run take longer? A: The first run needs to download the package. Subsequent runs will be faster since the package is cached locally.

MCP Ecosystem

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:

• MCP Inspector: Debug and test MCP servers
• MCP SDK: Build your own MCP servers
• MCP Protocol: Learn more about the Model Context Protocol

License

MIT License - see LICENSE file for details.

Support

• Issues: Report bugs and feature requests on GitHub Issues
• Documentation: See the name.com API Documentation for API details
• MCP Protocol: Learn more about Model Context Protocol
• Feedback: We want to hear from you! Submit feedback about the MCP server or name API here

Changelog

See the GitHub Releases page for version history and updates.