- Home
- MCP servers
- name.com
name.com
- javascript
2
GitHub Stars
javascript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"namedotcom-namecom-mcp": {
"command": "npx",
"args": [
"-y",
"namecom-mcp@latest"
],
"env": {
"NAME_TOKEN": "your-test-token",
"NAME_API_URL": "https://mcp.name.com",
"NAME_USERNAME": "your-test-username"
}
}
}
}You set up this MCP server to give any AI assistant access to the complete name.com API for domain management, using MCP to translate natural language requests into precise actions like domain search, registration, DNS changes, and transfers.
How to use
Interact with your AI tool and ask natural language questions about domains. The MCP server automatically exposes tools for name.com API endpoints, so you can perform tasks such as checking availability, listing domains, managing DNS records, and initiating registrations through your AI assistant. Start with a simple question like asking your AI to check if a domain is available, then expand to more complex operations as you gain confidence.
How to install
Prerequisites: you need an AI tool that supports MCP and a name.com account with API credentials.
Install and run the MCP server configuration using the test environment first to keep experimentation safe.
Create or paste the following MCP configuration into your tool. Use the test credentials for initial testing.
{
"mcpServers": {
"namecom": {
"command": "npx",
"args": ["-y", "namecom-mcp@latest"],
"env": {
"NAME_USERNAME": "your-test-username",
"NAME_TOKEN": "your-test-token"
}
}
}
}
Security and environment details
The server uses your API credentials to access name.com APIs with the permissions of your token. You should treat NAME_USERNAME and NAME_TOKEN like a password and use the safest environment available for testing.
For production use, specify the production API URL and credentials in the environment configuration.
Getting credentials and environment setup
To generate API credentials, log in to your name.com account and navigate to API Tokens. Create a token and choose the test credentials for mcp.dev.name.com or production credentials for mcp.name.com, depending on the environment you plan to use.
Testing & troubleshooting
Test basic capabilities by asking your AI tool to list domains or check availability. If you encounter issues, use the MCP Inspector to verify connectivity and tool availability.