How to buy a domain directly from Claude

The namemy.app MCP server (@namemyapp/mcp) gives Claude live access to a multi-registrar domain availability check and a buy-URL builder. It runs over stdio (the standard MCP transport) and ships in two modes: zero-config public mode (no API key, just buy_link works) and authed mode (API key in env, full 12-tool surface including AI name generation, owned-domain DNS, and server-to-server purchase). Most users start with public mode — it's a single npx command in one config file.

Step-by-step

1. STEP 1

   Open the Claude Desktop config

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. Create the file if it doesn't exist.

2. STEP 2

   Add the namemy.app MCP server

   Drop this into the mcpServers object. The npx -y means npm pulls the latest version on first run.

   {
     "mcpServers": {
       "namemyapp": {
         "command": "npx",
         "args": ["-y", "@namemyapp/mcp"],
         "env": { "NAMEMYAPP_AGENT_SOURCE": "claude-desktop" }
       }
     }
   }

3. STEP 3

   (Optional) Add an API key for the full surface

   Without a key, only the buy_link tool is exposed. Add NAMEMYAPP_API_KEY to env to unlock generate_names, check_domain (bulk), buy_domain (server-to-server), set_dns_record, and 7 more tools. Get a free key at namemy.app/app/api-keys.

   "env": {
     "NAMEMYAPP_API_KEY": "nma_live_...",
     "NAMEMYAPP_AGENT_SOURCE": "claude-desktop"
   }

4. STEP 4

   Restart Claude Desktop

   Fully quit and relaunch (Cmd+Q on macOS). The namemyapp MCP server appears in Claude's tool list — you'll see a small icon in the chat input that confirms it's connected.

5. STEP 5

   Ask

   Try one of the example prompts above. Claude will call buy_link (or check_domain in authed mode) and return clickable URLs. Click any URL to land in namemy.app's checkout.

What the agent will say back

Here are 10 candidates. I checked the three TLDs for each and only the available ones are shown.

| Name | Domain | Price | Buy |
|------|--------|-------|-----|
| threadsweep | threadsweep.com | $11.87 | https://namemy.app/checkout?domain=threadsweep.com&source=mcp |
| actionly | actionly.ai | $13.20 | https://namemy.app/checkout?domain=actionly.ai&source=mcp |
| tldr.bot | tldr.bot | $11.50 | https://namemy.app/checkout?domain=tldr.bot&source=mcp |

Click any link — namemy.app handles checkout in your browser.

FAQ

Do I need to install Node.js for npx -y to work?

Yes — Node 20+ is required (the same version Claude Desktop's MCP runtime needs). If you already have a recent Node, you're set. The package itself is tiny (~50 KB).

What's the difference between Claude Desktop and Claude Code?

Same MCP server works in both. For Claude Code you can also use /plugin install namemyapp which bundles the server, a SKILL that auto-triggers on naming prompts, and three slash commands (/check-domain, /name-app, /buy-domain).

Will Claude actually buy the domain for me?

No — and that's intentional. Claude hands you a buy URL; you complete checkout in your browser. This keeps your card details out of the AI conversation and avoids fraud / KYC issues. Sign-up + payment + WHOIS contact happens in one flow on namemy.app.

Can I use this with Claude on the web (claude.ai)?

claude.ai doesn't currently support MCP servers — only the desktop and Code clients do. For browser-based Claude, use namemy.app's REST API directly: curl https://namemy.app/api/public/domains/check?name=foo.com.

Does the public mode track me?

We hash your IP (sha256 + salt) for rate limiting and abuse triage — never stored as plaintext. Conversion attribution uses the source parameter you pass, not your IP.

What if I want to register many domains in one shot?

Authed mode's check_domains_bulk tool takes up to 100 domains per call. Public mode's bulk POST takes up to 50. Both return a buyUrl per available result.