How to Buy a Domain From Claude (Cloudflare MCP, Step by Step)

The hosted Cloudflare MCP authorizes in one of two ways. Over OAuth, the consent screen lets you pick permissions — include Cloudflare Registrar and DNS edit on the zone you will configure, nothing account-wide. With an API token, create one at dash.cloudflare.com → My Profile → API Tokens with Registrar write permission plus Zone → DNS → Edit for that zone, and hand it to the client as a bearer token. Tokens with client IP filtering are not accepted by the hosted server. Either way, skip "Account: Edit" — the agent does not need it.

The server lives at https://mcp.cloudflare.com/mcp. In Claude Desktop on a Pro, Max, Team or Enterprise plan, add it under Settings → Connectors → Add custom connector and finish the sign-in in the browser; otherwise bridge it through mcp-remote in claude_desktop_config.json (below), then fully quit and reopen Claude. In Claude Code, run `claude mcp add --transport http cloudflare https://mcp.cloudflare.com/mcp`, then `/mcp` to sign in. Do not install `@cloudflare/mcp-server-cloudflare` from npm for this: that older local server covers Workers, KV, R2 and D1 and has no DNS or Registrar tools.

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.cloudflare.com/mcp"]
    }
  }
}

The hosted server exposes three tools — search, execute and docs — over the whole Cloudflare API. Claude searches the spec for the Registrar API endpoints on your account (domain-search and domain-check), then calls them with execute. Be specific about the TLD: the Registrar API beta covers a curated subset of Cloudflare Registrar extensions, and search results are scoped to those. If the name is taken, ask for variations with the price domain-check returns.

Use the Cloudflare MCP. Through the Registrar API on my
account, check whether myapp.dev is available to register
and what it costs. If it is taken, suggest five similar
available names with their prices.

Registration charges the account's default payment method and is non-refundable once it completes. Never let the agent register without an explicit confirmation in your prompt: make Claude restate the exact domain and the price it was quoted, and wait for a literal "yes". Most clients also prompt before an execute call that writes — leave that on.

Register myapp.dev through the Registrar API. Before you
call the registrations endpoint, restate the exact domain
and the price domain-check returned, and wait for me to
reply "yes" before proceeding.

A domain registered at Cloudflare resolves through Cloudflare's nameservers, so pointing it somewhere means records inside the zone, not a nameserver change. Ask Claude to add the CNAME or A record with the value your host gave you — most hosts show it on their custom-domain screen — and keep it "DNS only" (not proxied) unless the host says otherwise. Claude reaches the DNS records endpoints the same way: search, then execute.

On the zone myapp.dev, list the current DNS records first.
Then add a CNAME for www pointing at cname.vercel-dns.com,
DNS only (not proxied). Do not change any other record.

Resolvers cache answers, so a record Claude re-reads five seconds after writing it can still look old. Wait a few minutes, then check from outside: `dig` on the command line, or the IntoDNS MCP's check_dns_propagation, which asks nine resolvers and shows where they disagree. If the record is wrong, ask Claude to delete and re-add it — never let it "fix" propagation it has no way to influence.

dig www.myapp.dev CNAME +short