The Dynadot MCP server is a Model Context Protocol (MCP) service provided for the Dynadot domain registrar API3, designed to let users directly manage domains, DNS, contacts, transfers, and other operations through an AI assistant.
Purpose This tool wraps the API capabilities of the Dynadot domain registrar as MCP tools, enabling an AI assistant to perform domain-related tasks. Users can use natural language instructions to have the AI complete operations such as searching for domains, registering domains, updating DNS records, transferring domains, setting up email forwarding, renewing domains, locking/unlocking domains, and checking WHOIS information.
Main capabilities
- Domain search, registration, renewal, and deletion, with support for batch operations (search up to 100 domains at a time and display prices).
- DNS record management: supports A, AAAA, CNAME, MX, TXT, and SRV records, with up to 20 primary records and 100 subdomain records (indexes 0-99).
- Nameserver configuration and DNSSEC settings. The set_dnssec tool can accept key_tag, digest_type, digest, algorithm (from the DNS provider's DS record), or flags, public_key, algorithm (DNSKEY). These are string values. Incomplete or mixed records will be rejected before contacting Dynadot. To disable DNSSEC, simply pass domain and clear: true.
- Contact CRUD operations.
- Domain transfer in and transfer out, with support for initiating a transfer using an authorization code.
- WHOIS privacy, email forwarding, domain locking, and folder organization.
- Marketplace features: auctions, backorders, and listings.
- Account information and balance resources.
- Sandbox mode for testing.
- A total of about 60 tools, covering about 106 commands of the complete Dynadot API3.
How to use Users can give the AI assistant instructions such as: search for available domains, register a new domain, update DNS records, transfer a domain to Dynadot, set up email forwarding, renew a domain, lock/unlock a domain for transfer, and view WHOIS information. The project provides llms.txt as a machine-readable summary, and you can also copy templates/CLAUDE.md or templates/AGENTS.md into the projectto enable automatic MCP discovery. Usage requires setting environment variables (the specific variable names are not yet provided). It can be run directly, or integrated into Claude Code or Claude Desktop. Claude Code: add it to the MCP settings (~/.claude/settings.json or the project's .claude/settings.json). Claude Desktop: add it to the configuration file (~/Library/Application Support/Claude/claude_desktop_config.json). The specific installation commands, environment variable names, and complete configuration examples are not yet provided.
Use cases Suitable for users who need to efficiently manage Dynadot domain assets through an AI assistant, such as batch querying and registering domains, batch managing DNS records, handling domain transfers and renewals, configuring email forwarding and WHOIS privacy, and participating in domain marketplace transactions.
Limitations The materials do not provide the specific environment variable names, complete installation commands, or configuration examples; consult the project documentation before use. The number of tools, number of API commands, and batch operation limits (search 100, 20 primary records, 100 subdomain records) are the clearly stated limitations. DNSSEC settings only accept parameters in specific formats, and incomplete or mixed records will be rejected.
