Cursor guide

How to buy a domain from Cursor

You're scaffolding a new project in Cursor and the name lives in a TODO. You want Cursor to help you settle on a name AND grab the domain — without breaking flow into a registrar tab.

Cursor supports MCP servers in mcp.json — workspace-scoped or global. Add the @namemyapp/mcp server and Cursor's chat gains live domain availability + a buy-URL builder. The bundled buy_link tool works without an API key (zero-config public mode). Add NAMEMYAPP_API_KEY to unlock all 12 tools.

Try this prompt

I'm scaffolding a TUI for managing Postgres migrations. Suggest 6 short brandable names and check the .dev / .com / .io for each.

Step-by-step

  1. STEP 1

    Open or create the Cursor MCP config

    Global: ~/.cursor/mcp.json. Workspace-scoped: <project>/.cursor/mcp.json. Create the file if it doesn't exist.

  2. STEP 2

    Add the namemy.app MCP server

    Drop this into mcpServers. Restart Cursor (or reload the workspace).

    {
      "mcpServers": {
        "namemyapp": {
          "command": "npx",
          "args": ["-y", "@namemyapp/mcp"],
          "env": { "NAMEMYAPP_AGENT_SOURCE": "cursor" }
        }
      }
    }
  3. STEP 3

    (Optional) Add an API key

    For AI name generation, owned-domain DNS, and server-to-server purchase, add NAMEMYAPP_API_KEY in env. Public-mode buy_link works without it.

  4. STEP 4

    Ask in chat

    Open Cursor's chat panel (Cmd+L) and ask 'find me a .dev domain for the migration TUI'. Cursor calls the tool and prints clickable URLs. Click any one to land in checkout.

What the agent will say back

Here are the candidates that are actually free:

| Name | Domain | Price | Buy |
|------|--------|-------|-----|
| migra | migra.dev | $14.80 | https://namemy.app/checkout?domain=migra.dev&source=cursor |
| schemashift | schemashift.com | $11.87 | https://namemy.app/checkout?domain=schemashift.com&source=cursor |
| planroll | planroll.io | $39.00 | https://namemy.app/checkout?domain=planroll.io&source=cursor |

Click any link to register on namemy.app.

FAQ

Workspace or global mcp.json — which is better?
Workspace-scoped is cleaner for project-specific keys. Global means every Cursor session has the tool available. We recommend global for the no-auth buy_link primitive and workspace for projects that need a paid API key.
Will the agent edit my code AND buy a domain?
It will hand you a buy URL — clicking it takes you to namemy.app's checkout. Code edits and domain purchase stay separate (intentional, see security notes on the install page).
Does this conflict with other Cursor MCP servers?
No — MCP servers are namespaced. namemyapp tools appear under the namemyapp prefix and don't collide with anything else (e.g. github, postgres, sqlite servers).

Install in 2 minutes

Paste-ready configs for every coding agent, plus the no-auth public REST API.

Open install instructions →

Related guides