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

Cloudflare account-level tokens are too broad for an agent. Go to dash.cloudflare.com → My Profile → API Tokens → Create Token → Custom token. Grant exactly: Account → Account Settings → Read, Account → Cloudflare Registrar → Edit, Zone → DNS → Edit (for the zone you will configure). Skip "Account: Edit" — the agent does not need it. Save the token to your password manager; you cannot view it again.

Open Claude Desktop → Settings → Developer → Edit Config. Add the Cloudflare MCP under mcpServers, with the token in an env block (not in args — that leaks into process listings). Fully quit Claude (Cmd+Q on macOS) and reopen. The hammer icon at the bottom of the chat should show the Cloudflare server connected with a green dot.

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": ["-y", "@cloudflare/mcp-server-cloudflare"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_scoped_token_here"
      }
    }
  }
}

Start the conversation by asking Claude to check whether your target domain is available. Be specific about the TLD — Cloudflare Registrar supports a curated set (.com, .org, .dev, .ai, etc.) but not every TLD on the internet. If the name is taken, Claude can search for variations and report cost per option.

Use the Cloudflare MCP to check if myapp.dev is available
to register. If it is, return the cost. If not, suggest five
similar available names with their costs.

Registration moves money. Never let the agent register a domain without an explicit confirmation step in your prompt. Spell out the exact name in the confirmation — do not let the agent infer it. The pattern below makes the agent restate the domain and wait for a "yes" before committing.

Register myapp.dev on Cloudflare. Before calling the
register tool, restate the exact domain you are about to
register and the cost, and wait for me to reply "yes" before
proceeding.

Once registered, the domain needs DNS records to point at your deployment. Cloudflare's default name-servers run on the same account, so this usually means adding records inside the zone rather than changing name-servers. Ask Claude to add an A record (for an IP) or a CNAME (for a Vercel / Netlify deployment hostname).

Add an A record on myapp.dev pointing to 76.76.21.21.
Set proxy status to "DNS only" — not proxied.

Name-server propagation takes minutes to hours, so do not ask Claude to verify in the same turn. Instead, run dig manually after a few minutes (`dig myapp.dev A +short`) or come back after coffee. If the record is wrong, ask Claude to delete and re-add it — never let an agent "fix" propagation it has no way to influence.

dig myapp.dev A +short