@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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。