Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Brandable business names with live domain availability + one-click buy URLs.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
NAMEMYAPP_API_KEY, NAMEMYAPP_AGENT_SOURCE标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.namemy.app/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"namemyapp": {
"command": "npx",
"args": [
"-y",
"@namemyapp/mcp"
],
"env": {
"NAMEMYAPP_API_KEY": "your-value",
"NAMEMYAPP_AGENT_SOURCE": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http namemyapp https://mcp.namemy.app/mcpclaude mcp add namemyapp --env NAMEMYAPP_API_KEY=your-value --env NAMEMYAPP_AGENT_SOURCE=your-value -- npx -y @namemyapp/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"namemyapp": {
"url": "https://mcp.namemy.app/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"namemyapp": {
"command": "npx",
"args": [
"-y",
"@namemyapp/mcp"
],
"env": {
"NAMEMYAPP_API_KEY": "your-value",
"NAMEMYAPP_AGENT_SOURCE": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"namemyapp": {
"type": "http",
"url": "https://mcp.namemy.app/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"namemyapp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@namemyapp/mcp"
],
"env": {
"NAMEMYAPP_API_KEY": "your-value",
"NAMEMYAPP_AGENT_SOURCE": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.namemy.app/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
NAMEMYAPP_AGENT_SOURCE env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Rakesh1002 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:NAMEMYAPP_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.1.10)于17天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, OpenTakeoff
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
Your AI agent can already suggest names. This server lets it:
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.
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?"*
{
"mcpServers": { "namemyapp": { "command": "npx", "args": ["-y", "@namemyapp/mcp"], "env": { "NAMEMYAPP_AGENT_SOURCE": "claude-desktop" } } } }
/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.
Same JSON shape:
{
"mcpServers": { "namemyapp": { "command": "npx", "args": ["-y", "@namemyapp/mcp"], "env": { "NAMEMYAPP_AGENT_SOURCE": "cursor" } } } }
~/.cursor/mcp.json (or workspace .cursor/mcp.json)~/.codeium/windsurf/mcp_config.json~/.continue/config.json under experimental.modelContextProtocolServersFull install matrix: https://namemy.app/agents/install.
| 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.
buy_link — always availableBuild a one-click purchase URL.
{ domain: "codeflow.ai", priceUsd?: 13.20 }
// → { domain, buyUrl, source }
check_domain — authedLive single-domain availability + price.
{ domain: "codeflow.ai" }
// → { domain, available, bestPrice, comparison, buyUrl }
generate_names — authedAI brand name generation with availability fused in.
{ description: "AI task manager", tlds?, count?, industry? }
// → { meta, results: [{ name, tldOptions: [{ domain, available, price, buyUrl }] }] }
buy_domain (server-to-server), list_domains, set_dns_record, brand_conflict_check, generate_logo, generate_legal_docs, generate_brand_kit, generate_social_kit.
| 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 |
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.
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 — raw Authorization: Bearer .MIT. Source at https://github.com/Rakesh1002/namemyapp/tree/main/packages/mcp.