# joachimBrindeau/domain-mcp

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/joachimBrindeau/domain-mcp  
**GitHub Stars:** 13  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/joachimbrindeau-domain-mcp

## Description
Manage Dynadot domains, DNS, WHOIS, nameservers, transfers and aftermarket listings.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "domain-mcp": {
    "command": "npx",
    "args": ["-y","domain-mcp"],
    "env": {
      "DYNADOT_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `DYNADOT_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What joachimBrindeau/domain-mcp does

joachimBrindeau/domain-mcp exposes Dynadot domain-management operations through the Model Context Protocol. It covers domain searches, registration, renewal, deletion, locking, pushing, and inspection. DNS operations include reading and changing records, forwarding, parking, and email settings. It also handles nameservers, transfers, WHOIS contacts, portfolio organization, account data, bulk settings, and renewals.

The repository also describes aftermarket operations such as domain listings, auctions, bids, and marketplace actions. Agent-oriented capabilities include generating domain ideas, auditing a portfolio, and diagnosing DNS issues. Because some operations can be destructive or paid, clients should request confirmation before executing them.

## How it works

An MCP client receives a natural-language request, selects an appropriate composite tool and operation, and sends the request to joachimBrindeau/domain-mcp. The server validates and transforms the input, calls the Dynadot API, and passes the result back to the client. Zod is used for input validation, while responses use a consistent format and include explanatory errors.

The server consolidates more than 100 individual API actions into 10 composite tools, keeping the tool list smaller for clients. The README also mentions additional tools for domain checks, name generation, and tool discovery. This structure is useful for requests such as checking availability, adding an A record, finding upcoming expirations, or reviewing nameservers and WHOIS contacts.

The repository contains two packages. The `domain-mcp` package is the TypeScript MCP server distributed through npm. The separate `domain-agent-kit` package is a portable Agent Plugin for Agent Plugins v1 hosts, including Hermes and Claude Code, with an optional Claude safety adapter.

## Setup and configuration

Run the server with Node.js 18 or newer and a Dynadot API key. A standard stdio configuration uses `npx`:

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

Restart the MCP client after adding the configuration. The repository points to the package guide for client-specific setup, shared HTTP transport, additional environment options, and troubleshooting. Local development uses pnpm; the documented commands include `pnpm install`, `pnpm test`, `pnpm typecheck`, `pnpm check`, and `pnpm build`.

## Tools and capabilities

joachimBrindeau/domain-mcp supports these areas:

- Domain availability, registration, renewal, deletion, locking, pushing, and inspection
- DNS records, forwarding, parking, and email settings
- Nameserver creation, editing, listing, and assignment
- Transfer initiation, status checks, and authorization steps
- WHOIS contact creation and maintenance
- Portfolio folders, account data, bulk settings, and renewal workflows
- Aftermarket listings, auctions, bids, and marketplace operations
- Domain checks, name generation, portfolio audits, and DNS diagnosis

## Limitations and notes

The server is specifically documented around Dynadot, so its operations depend on the Dynadot API and the permissions available to the supplied key. The README does not document support for other registrars. Confirmation behavior is expected from the client or portable plugin for irreversible or paid actions; the server should not be treated as an automatic approval layer.

The project is licensed under MIT. Its documented package setup requires Node.js 18 or later. A separate portable plugin provides an approval and read-back contract, and its optional Claude Code adapter adds a native confirmation hook for selected irreversible actions.

_Full upstream README: https://allmcps.com/mcp/joachimbrindeau-domain-mcp/readme_