Dynadot MCP Server

MCP server for Dynadot domain registrar — domain search, registration, DNS, and transfers. Exposed over MCP by the dynadot mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

MCP (Model Context Protocol) server for the Dynadot domain registrar API. Manage domains, DNS records, contacts, transfers, and more — all from your AI assistant.

• 60 tools — covering the full Dynadot API3 (~106 commands)
• Domain search, registration, renewal, deletion
• DNS record management (A, AAAA, CNAME, MX, TXT, SRV)
• Nameserver configuration and DNSSEC
• Contact CRUD operations
• Domain transfers (in/out)

Its toolset

Everything the assistant can do here goes through one of these:

• Contacts — The Contacts tool exposed by this server
• Transfers — The Transfers tool exposed by this server
• Settings — The Settings tool exposed by this server
• Folders — The Folders tool exposed by this server
• Account — The Account tool exposed by this server
• Marketplace — The Marketplace tool exposed by this server

Configuration

You will need one environment variable: DYNADOT_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

The server ships on npm as dynadot-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dynadot's toolset — Contacts, Transfers, Settings and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mikusnuz; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the dynadot mcp server does with a few real requests.