domain

This MCP server provides natural language domain management capabilities via Dynadot through an MCP-compatible interface. It exposes 10 tools for domain operations, DNS management, transfers, and related domain tasks, enabling AI assistants like Claude Code or Cursor to perform actions such as listing domains, registering new domains, configuring DNS records, and handling transfers using conversational prompts. To use it, configure your MCP client to load the domain-mcp server with the appropriate Dynadot API key, then issue domain-related commands through your AI assistant. The server translates natural language requests into Dynadot API calls and returns structured results that your agent can display or further process.

You can interact with tools like: searching for domains and pricing, registering domains with optional WHOIS privacy, updating DNS records (A, CNAME, MX, etc.), managing domain contacts, enabling auto-renew, and transferring domains. The integration emphasizes safe, type-checked interactions and MCP-compliant request formats so that the AI can reason about domain operations, confirm actions when needed, and present results in a clear, actionable way.

Prerequisites:

• Node.js >= 18
• npm or yarn
• A Dynadot account with an API key

Step 1: Install and run via NPX (recommended)

• Ensure you have your Dynadot API key ready from your Dynadot account settings.
• In your MCP client config, add the server using NPX:

{
  "mcpServers": {
    "domain-mcp": {
      "command": "npx",
      "args": ["-y", "domain-mcp"],
      "env": {
        "DYNADOT_API_KEY": "your-api-key-here"
      }
    }
  }
}

Step 2: Global install (alternative)

• Install the package globally and reference it by name in your config:

npm install -g domain-mcp

{
  "mcpServers": {
    "domain-mcp": {
      "command": "domain-mcp",
      "env": {
        "DYNADOT_API_KEY": "your-api-key-here"
      }
    }
  }
}

Step 3: Local development (for contributions)

• Clone and install, then build:

git clone https://github.com/joachimBrindeau/domain-mcp.git
cd domain-mcp
npm install
npm run build

Configure with an absolute path to the built index.js when running locally:

{
  "mcpServers": {
    "domain-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/domain-mcp/dist/index.js"],
      "env": {
        "DYNADOT_API_KEY": "your-api-key-here"
      }
    }
  }
}

Step 4: Verify installation

• Restart your MCP client and test a few domain-related prompts to ensure the server responds with domain actions and results.

Notes and tips:

• Always keep your Dynadot API key secure; do not hard-code it in shared configurations.
• If you encounter API rate limits or sandbox limitations, set DYNADOT_SANDBOX to "true" to test in sandbox mode (see docs in the repository).
• The npm package name is domain-mcp; use npx domain-mcp or domain-mcp after a global install as appropriate.
• Ensure your MCP client schema can handle the 10 tools exposed by this server and parse the results consistently.
• For contributors, review the TypeScript types and Zod validations in the project to understand the expected payloads and responses.