@namemyapp/mcp
Enables AI agents to check domain availability, generate brandable names, and create one-click purchase URLs for domains via namemy.app.
README
@namemyapp/mcp
Model Context Protocol (MCP) server for namemy.app — gives Claude Desktop, Claude Code, Cursor, Windsurf, Continue.dev, ChatGPT, and any MCP-aware client live domain availability and one-click buy URLs.
Three ways to connect:
| Mode | Endpoint | Auth | Best for |
|---|---|---|---|
| Remote OAuth | https://mcp.namemy.app/mcp |
OAuth 2.1 + PKCE | Claude.ai web · ChatGPT · directory listings |
| Remote direct | https://mcp.namemy.app/direct |
Bearer namemy.app key | Claude Desktop · curl · custom scripts |
| Local stdio | npx -y @namemyapp/mcp |
Env var key | Claude Code plugin · restricted networks |
The remote OAuth endpoint is the recommended path for hosted clients. Use direct or stdio if your client doesn't speak OAuth. This npm package is the stdio mirror.
What it does
Your AI agent can already suggest names. This server lets it:
- Check domain availability across registrars with unified retail pricing
- Hand the user a one-click buy URL that drops them into namemy.app's checkout — sign-up + payment in one flow, your agent never touches a card
- Generate brandable names with availability fused in (authed mode)
- Buy domains server-to-server (authed mode)
- Set DNS records, generate logos, legal docs, brand kits (authed mode)
Install — Claude.ai web / Cursor / ChatGPT (remote, OAuth)
Use the OAuth-protected endpoint when the client supports it (Claude.ai web/mobile connectors, ChatGPT Apps, Cursor's remote MCP, anything that follows MCP protected-resource discovery):
https://mcp.namemy.app/mcp
The client opens a browser tab where you paste your namemy.app API key once — after that the connector refreshes its own OAuth tokens. OAuth metadata is at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource.
Install — Claude Desktop / scripts (remote, direct bearer)
For clients that don't do OAuth (Claude Desktop's basic remote MCP, curl, custom scripts), point at the direct endpoint and pass your API key as a bearer token:
{
"mcpServers": {
"namemyapp": {
"transport": "http",
"url": "https://mcp.namemy.app/direct",
"headers": { "Authorization": "Bearer nma_live_..." }
}
}
}
Restart Claude Desktop. Ask: "is codeflow.ai available?"
Install — Claude Desktop (local stdio fallback)
{
"mcpServers": {
"namemyapp": {
"command": "npx",
"args": ["-y", "@namemyapp/mcp"],
"env": { "NAMEMYAPP_AGENT_SOURCE": "claude-desktop" }
}
}
}
Install — Claude Code
/plugin install namemyapp
The bundled plugin ships a SKILL that triggers on naming/domain prompts plus three slash commands (/check-domain, /name-app, /buy-domain). Or wire just the MCP server in ~/.claude.json with the same JSON snippet as Claude Desktop.
Install — Cursor / Windsurf / Continue.dev
Same JSON shape:
{
"mcpServers": {
"namemyapp": {
"command": "npx",
"args": ["-y", "@namemyapp/mcp"],
"env": { "NAMEMYAPP_AGENT_SOURCE": "cursor" }
}
}
}
- Cursor:
~/.cursor/mcp.json(or workspace.cursor/mcp.json) - Windsurf:
~/.codeium/windsurf/mcp_config.json - Continue.dev:
~/.continue/config.jsonunderexperimental.modelContextProtocolServers
Full install matrix: https://namemy.app/agents/install.
Two modes
| Mode | Trigger | Tools exposed |
|---|---|---|
| public | no NAMEMYAPP_API_KEY |
buy_link (URL builder, no network call) |
| authed | NAMEMYAPP_API_KEY=nma_live_... |
All 12 tools wrapping /api/v1/* |
Public mode is the zero-friction path — npx -y @namemyapp/mcp works without any signup. Get a free key at https://namemy.app/app/api-keys for the full surface.
Tools
buy_link — always available
Build a one-click purchase URL.
{ domain: "codeflow.ai", priceUsd?: 13.20 }
// → { domain, buyUrl, source }
check_domain — authed
Live single-domain availability + price.
{ domain: "codeflow.ai" }
// → { domain, available, bestPrice, comparison, buyUrl }
generate_names — authed
AI brand name generation with availability fused in.
{ description: "AI task manager", tlds?, count?, industry? }
// → { meta, results: [{ name, tldOptions: [{ domain, available, price, buyUrl }] }] }
Other authed tools
buy_domain (server-to-server), list_domains, set_dns_record, brand_conflict_check, generate_logo, generate_legal_docs, generate_brand_kit, generate_social_kit.
Environment variables
| Var | Default | Purpose |
|---|---|---|
NAMEMYAPP_API_KEY |
— | Bearer token for authed mode |
NAMEMYAPP_API_URL |
https://namemy.app |
Override for staging / self-hosted |
NAMEMYAPP_AGENT_SOURCE |
mcp |
Attribution tag stamped on every API call + buyUrl |
Attribution
Every API call sends X-Agent-Source header and ?source= query param. namemy.app records this on every Purchase row and pushes attribution events to PostHog so we can credit the agent that drove the conversion.
Transport
Stdio (this package) and Streamable HTTP. Two remote endpoints:
https://mcp.namemy.app/mcp— OAuth 2.1 (auth code + PKCE, dynamic client registration via RFC 7591). Clients discover via/.well-known/oauth-authorization-server.https://mcp.namemy.app/direct— rawAuthorization: Bearer <namemy.app-api-key>.
Source + license
MIT. Source at https://github.com/Rakesh1002/namemyapp/tree/main/packages/mcp.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.