company_to_domain — Namewhere MCP Tool
company_to_domain
(company to domain) is one of 1 tool on the
Namewhere
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call company_to_domain from your client
- Claude Code Namewhere company_to_domain run in your project directory
- Claude Desktop Namewhere company_to_domain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Namewhere company_to_domain ~/.cursor/mcp.json
- VS Code Namewhere company_to_domain .vscode/mcp.json
- Zed Namewhere company_to_domain ~/.config/zed/settings.json
- Windsurf Namewhere company_to_domain ~/.codeium/windsurf/mcp_config.json
- Cline Namewhere company_to_domain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Namewhere company_to_domain ~/.gemini/settings.json
- Grok Namewhere company_to_domain .mcp.json (in your project root)
- ChatGPT Namewhere company_to_domain Settings → Connectors → Advanced → Developer mode
- Claude.ai Namewhere company_to_domain Settings → Connectors → Add custom connector
- LangChain Namewhere company_to_domain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http namewhere https://namewhere.cybermaxtools.com/mcp?via=mcp-registry
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.