@namemyapp/mcp — the Model Context Protocol server for domains

@namemyapp/mcp is a Model Context Protocol server that exposes namemy.app's domain availability, name generation, branding, legal, and logo tools to any MCP-aware client — Claude Desktop, Claude Code, Cursor, Windsurf, Continue.dev, your own runtime. It speaks stdio (the standard MCP transport), ships under MIT, and weighs ~50 KB. Two operating modes: public (no API key, only buy_link is exposed) and authed (NAMEMYAPP_API_KEY env var, all 12 tools).

Step-by-step

1. STEP 1

   Install via npx

   Add this to your MCP client's config (Claude Desktop, Cursor, Windsurf, Continue.dev — same JSON shape). The npx -y means npm pulls the latest version on first run; cache hit on subsequent starts.

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

2. STEP 2

   Pick a mode

   Public mode (no env): exposes only buy_link — a pure URL builder, no network call, always works. Authed mode (NAMEMYAPP_API_KEY env): exposes all 12 tools wrapping /api/v1/* — generate_names, check_domain, buy_domain, list_domains, set_dns_record, brand_conflict_check, generate_logo, generate_legal_docs, generate_brand_kit, generate_social_kit.

3. STEP 3

   Tools at a glance

   Public mode: buy_link. Authed mode adds: generate_names (AI name gen with availability), check_domain (single + bulk), buy_domain (server-to-server purchase via API key), list_domains, set_dns_record, brand_conflict_check (USPTO + live web), generate_logo, generate_legal_docs, generate_brand_kit, generate_social_kit.

4. STEP 4

   Source attribution

   Set NAMEMYAPP_AGENT_SOURCE in env (defaults to 'mcp'). Every API call sends X-Agent-Source header AND ?source= query param. namemy.app records on every Purchase row and pushes attribution events to PostHog.

   "env": {
     "NAMEMYAPP_API_KEY": "nma_live_...",
     "NAMEMYAPP_AGENT_SOURCE": "my-product-name"
   }

What the agent will say back

Calling namemyapp.check_domain({ domain: "codeflow.ai" })...

{
  "domain": "codeflow.ai",
  "available": true,
  "bestPrice": {
    "registrar": "dynadot",
    "retailPrice": "$13.20",
    "retailRenewal": "$14.50",
    "currency": "usd"
  },
  "buyUrl": "https://namemy.app/checkout?domain=codeflow.ai&price=13.20&source=mcp&ref=key_..."
}

codeflow.ai is available — $13.20. Click the buyUrl above to register on namemy.app.

FAQ

Does it support the streaming HTTP transport (Streamable HTTP)?

Yes — live at https://mcp.namemy.app/mcp (OAuth 2.1 + PKCE) and https://mcp.namemy.app/direct (Bearer namemy.app API key). MCP 2025-03-26 spec, Streamable HTTP transport. Use the OAuth endpoint for Claude.ai web, ChatGPT Apps, Cursor's remote MCP. Use /direct for Claude Desktop and command-line scripts. The npm stdio package is the local fallback.

What's the rate limit?

Public mode (buy_link) has no API limit — it makes no network call. Authed mode hits /api/v1/* which is 100 req/min/key by default and a daily quota tied to your subscription tier (free tier: 1000 calls/day across endpoints).

Can I run this in a container / serverless function?

Stdio transport requires a long-lived process (the MCP client controls the lifecycle). For serverless / web contexts, use the REST API directly: /api/public/* (no auth) or /api/v1/* (Bearer auth). Same data, different transport.

How do I debug what the server is doing?

stderr is not consumed by the MCP client — the server logs there. Or use @modelcontextprotocol/inspector: `npx -y @modelcontextprotocol/inspector node dist/index.js` shows every tool call + response.

Open source?

Yes — MIT licensed, source at github.com/Rakesh1002/namemyapp/tree/main/packages/mcp. PRs welcome.