namemyapp
Brandable business names with live domain availability + one-click buy URLs.
Install namemyapp in your MCP client
namemyapp is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.
- Locate your client's MCP config file.
- Cursor:
~/.cursor/mcp.json - Claude Desktop (macOS):
~/Library/Application Support/Claude/claude_desktop_config.json - Claude Desktop (Windows):
%APPDATA%\Claude\claude_desktop_config.json - VS Code:
Settings → Extensions → MCP - Windsurf:
Settings → MCP Servers
- Cursor:
- Add namemyapp to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing
mcpServersobject. - Restart your client so it picks up the new server.
- Verify — ask the assistant to list available tools; namemyapp's tools should appear.
{
"mcpServers": {
"namemyapp": {
"command": "npx",
"args": [
"-y",
"@namemyapp/mcp"
],
"env": {
"NAMEMYAPP_API_KEY": "<your-namemyapp-api-key>",
"NAMEMYAPP_AGENT_SOURCE": "<your-namemyapp-agent-source>"
}
}
}
}Install namemyapp in Cursor
Open ~/.cursor/mcp.json in your editor, paste the snippet above into mcpServers, save, and restart Cursor. namemyapp will show up in the assistant's tool list on next launch.
Install namemyapp in Claude Desktop (macOS)
Open ~/Library/Application Support/Claude/claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (macOS). namemyapp will show up in the assistant's tool list on next launch.
Install namemyapp in Claude Desktop (Windows)
Open %APPDATA%\Claude\claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (Windows). namemyapp will show up in the assistant's tool list on next launch.
Install namemyapp in VS Code
Open Settings → Extensions → MCP in your editor, paste the snippet above into mcpServers, save, and restart VS Code. namemyapp will show up in the assistant's tool list on next launch.
npm package: @namemyapp/mcp
Required environment variables
namemyapp needs the following environment variables set before it can run. Add them to the env block of your mcpServers entry, or export them in your shell before launching the client.
NAMEMYAPP_API_KEYNAMEMYAPP_AGENT_SOURCE
Transport
namemyapp supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.
More build.protocol_tooling.mcp MCP servers
Other Model Context Protocol servers in the same space as namemyapp. Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.
deckbase-mcp-server
MCP server for Deckbase - exposes docs, template blocks, and project context
openarchieven-mcp-server
MCP server for the Open Archives genealogical search engine.
bulk-url-checker
Validate up to 75,000 URLs per job (status, redirects, response times). OAuth 2.1.
SafeAgent
Execution guard for AI agents — prevents duplicate tool calls on retry.
GeoLabel
Turn GPS coordinates into place name, category, and live opening hours via OpenStreetMap.
forge-mcp
MCP server for Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge
multi-scraper-mcp
12 web scraping tools for AI agents: Reddit, Amazon, eBay, Google Maps, Yelp, YouTube, TikTok
HoShy
Search Rakuten Ichiba products and compare prices via Claude. Zero setup, no API key needed.
Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.