Name.com is an MCP server that connects AI assistants to the Name.com registrar API. It allows developers, domain investors, system administrators, and site owners to handle domain infrastructure directly through natural language prompts. The server dynamically generates tools from the Name.com OpenAPI specification, exposing capabilities across the provider's entire API surface. Users can perform domain availability checks, register domain names, adjust DNS configurations, handle transfers, and manage both email and URL forwarding settings. By default, the server interfaces with the Name.com test environment to provide a safe testing space that avoids accidental billing or live domain changes. It can also be targeted at the production API when live operations are required. With integrated input validation and standard credential authentication, the server enables automated registrar workflows within any client application that implements the Model Context Protocol.
Category: Cloud & Infrastructure
Tags: dns, domains, name.com, registrar
npx and namecom-mcp@latest: json { "mcpServers": { "namecom": { "command": "npx", "args": ["-y", "namecom-mcp@latest"], "env": { "NAME_USERNAME": "your-test-username", "NAME_TOKEN": "your-test-token" } } } } 4. If targeting production, also include "NAME_API_URL": "https://mcp.name.com" under the env block and supply production credentials. 5. Save the configuration and restart your MCP client.Part of MCP Servers
You can install and run it using npx by adding the package namecom-mcp to your MCP client configuration file. You will need to specify your NAME_USERNAME and NAME_TOKEN in the environment variables block, and optionally provide NAME_API_URL if you want to target production rather than the default test environment.
It exposes the full Name.com OpenAPI specification to AI tools. This enables searching domain availability, buying domains, inspecting and editing DNS records, initiating domain transfers, and configuring email or URL forwarding rules through conversational prompts.
It is designed to work with any client supporting the Model Context Protocol, including Claude Desktop and Cursor. You can also test and debug the server using the official Model Context Protocol Inspector tool.
Yes, it is released as an open-source project distributed under the MIT License on GitHub under the namedotcom organization repository.
No. The server defaults to the Name.com developer test environment at mcp.dev.name.com, which requires test credentials and does not incur live charges. To perform live operations that affect your real account, you must explicitly set the production API URL.