Buy & manage domains from any AI chat: availability, register, DNS, email forwarding, AI bot stats.
Buy and manage internet domains from inside any AI chat.
MCPDomain is the first domain registrar exposed as a Model Context Protocol server. Ask Claude, ChatGPT, or Cursor to find a domain — they can check availability, register it, set up free email forwarding, configure DNS, and show you which AI bots are crawling it, all without leaving the chat.
Hosted endpoint:
https://mcpdomain.ai/mcp— plug into any remote-MCP-capable client, no install needed. Local stdio:npm install -g mcpdomain— see below.
You: Find me a .com for a sourdough bakery in Brooklyn.
Claude: sweetcrumbs.com is taken, but these are available:
- brooklynsourdough.com — $14.99
- crumbsbrooklyn.com — $14.99
- doughbk.com — $14.99
Want me to register one?
You: Yes, brooklynsourdough.com, and forward hello@ to my gmail.
Claude: Here's your checkout link: https://mcpdomain.ai/c/ord_abc123
Once you pay, I'll set up email forwarding automatically.
That's the entire flow. No registrar UI, no DNS dashboard, no MX-record copy-paste.
hello@yourdomain.com → your existing
inbox. No mail server. No MX setup.| Tool | What it does |
|---|---|
check_domain_availability | Is this exact name free? What's it cost? |
suggest_available_domains | Brandable name ideas, real-time verified. |
register_new_domain | Start a registration, returns a Stripe checkout URL. |
configure_domain_email | Catch-all or per-alias email forwarding. |
configure_domain_dns | A / CNAME / MX / TXT, with presets for common hosts. |
get_my_domain_details | Status, expiry, DNS, email forwards, AI-bot stats. |
transfer_existing_domain | Move a domain in from another registrar. |
Tool prompts (the text the LLM actually reads) live in
mcp-server/src/tool-descriptions.ts.
Point any remote-MCP-capable client at:
https://mcpdomain.ai/mcp
No install. No keys.
npm install -g mcpdomain
Claude Desktop — edit your claude_desktop_config.json:
{
"mcpServers": {
"mcpdomain": {
"command": "npx",
"args": ["-y", "mcpdomain"]
}
}
}
Cursor — Settings → MCP → Add:
{
"mcpdomain": {
"command": "npx",
"args": ["-y", "mcpdomain"]
}
}
OpenClaw — one line, via McPorter:
npm install -g mcporter
mcporter install mcpdomain --target openclaw
That writes the server to ~/.openclaw/workspace/config/mcporter.json
automatically. If you prefer editing it manually, drop the same
mcpServers block from the Claude Desktop snippet above into that file.
More client recipes are in the npm README.
Claude / ChatGPT / Cursor
│ MCP
▼
mcpdomain (stdio package)
│ HTTPS
▼
mcpdomain.ai (Cloudflare Worker + D1)
│ XML API
▼
OpenSRS / Tucows registrar
Most of the logic — orders, Stripe checkout, DNS, email forwarding, bot-intel logging — lives in the Cloudflare Worker, not in the local package. That keeps the npm install tiny and the client free of API keys.
Source layout:
mcp-server/ ← the npm package (this is `mcpdomain` on npm)
src/ ← TypeScript source
Dockerfile ← container build for HTTP transport
worker/ ← Cloudflare Worker (server-side)
src/ ← endpoints, admin dashboard, OpenSRS adapter
migrations/ ← D1 schema
git clone https://github.com/danboabes/mcpdomain.git
cd mcpdomain/mcp-server
npm install
npm run dev # runs the MCP server over stdio via tsx
To run the HTTP transport locally:
npm run dev:http
The MCP Inspector from Anthropic is the fastest way to poke at tools while iterating.
Prices the agent quotes are what you pay at checkout — wholesale + a small flat margin, no "first year free" bait, no auto-renew price hikes. Current TLD prices are on mcpdomain.ai.
Whois privacy is on by default wherever the TLD supports it. The bot-intel feature logs AI crawler traffic only, never visitor PII. Payments go through Stripe — we never see card details.
MIT — see LICENSE.
https://mcpdomain.ai/mcpSource-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y mcpdomainMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-danboabes-mcpdomain": {
"command": "npx",
"args": [
"-y",
"mcpdomain"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemcpdomainnpmMCPDomain works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.