AI & Automation

Domain MCP Server

Connect AI agents to your domain portfolio. Search availability, audit and edit DNS, manage nameservers, and check account data — through natural language, with scoped permissions and guardrails built in.

Connect your agent Talk to our team

Teams are giving AI agents real operational work — not just drafting and summarizing, but acting on systems. For domain and DNS management, that shift runs into a wall: the agent can reason about what needs to change, but it can't safely execute the change without a tool that understands your registrar.

The 101domain MCP Server is that tool. It lets an agent operate on your domain portfolio directly, with the same scoped access model as the API — so automation stays controlled and auditable.

What is the 101domain MCP Server?

The Model Context Protocol (MCP) is an open standard that lets AI agents call external tools in a structured, permissioned way. An MCP server publishes a set of tools; a connected agent — in Claude, or any MCP-compatible client — can invoke them on the user's behalf.

The 101domain MCP Server publishes domain-management tools backed by the 101domain API. Once connected, an agent can search for available names, audit and modify DNS, replace nameservers, and look up account and TLD data — all from natural-language instructions, without the user writing any API calls.

What your AI agent can do

The server exposes domain operations as agent tools, including:

  • Search availability and pricing for up to 50 domains at a time.
  • Audit DNS — retrieve nameserver and DNS record information for any managed domain.
  • Create, edit, and delete DNS records from natural-language descriptions.
  • Replace nameservers, with the agent reporting whether the change applied immediately or is pending registry processing.
  • Look up account balance, products, and TLD requirements to inform decisions.

DNS write operations require the dns_write scope on the connected key. For the full tool list and descriptions, see the 101domain MCP Server Tools reference.

Why a registrar MCP matters for corporate teams

Letting an AI agent touch production DNS is a real risk if access isn't controlled. The 101domain MCP Server is built so that agent automation stays inside the boundaries you set:

  • Scoped access. Connect a read-only key for auditing and reporting, or grant dns_write only when the agent genuinely needs to make changes.
  • Guardrails against unintended changes. Permissions are enforced at the key level, so an agent can't exceed what its scope allows.
  • Auditable operations. Changes run through the same registrar service as the API, keeping a consistent record.
  • Managed-service backing. The same team of domain experts that supports your portfolio supports the platform the agent is acting on.

For guidance on constraining agent behavior, see How to stop your AI agent from making unintended changes and Essential security practices for MCP clients.

Connecting an agent

  1. Generate an API key with the scopes your agent needs at creation. To read DNS, include dns_read; to make DNS changes, include dns_write. Scopes are set at creation and can't be added later.
  2. Add the 101domain MCP Server to your MCP-compatible client using the server URL: mcp.101domain.com
  3. Authenticate with your scoped key and start issuing natural-language instructions.

Step-by-step walkthroughs are in the MCP Server Guide.

Put your domain portfolio within reach of your AI agents

Connect an MCP-compatible client today, or talk to our team about agent access for your portfolio.

Connect your agent Talk to our team