transfer_existing_domain — MCPDomain MCP Tool
transfer_existing_domain
(transfer existing domain) is one of 7 tools on the
MCPDomain
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call transfer_existing_domain from your client
- Claude Code MCPDomain transfer_existing_domain run in your project directory
- Claude Desktop MCPDomain transfer_existing_domain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MCPDomain transfer_existing_domain ~/.cursor/mcp.json
- VS Code MCPDomain transfer_existing_domain .vscode/mcp.json
- Zed MCPDomain transfer_existing_domain ~/.config/zed/settings.json
- Windsurf MCPDomain transfer_existing_domain ~/.codeium/windsurf/mcp_config.json
- Cline MCPDomain transfer_existing_domain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MCPDomain transfer_existing_domain ~/.gemini/settings.json
- Grok MCPDomain transfer_existing_domain .mcp.json (in your project root)
- ChatGPT MCPDomain transfer_existing_domain Settings → Connectors → Advanced → Developer mode
- Claude.ai MCPDomain transfer_existing_domain Settings → Connectors → Add custom connector
- LangChain MCPDomain transfer_existing_domain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcpdomain https://mcpdomain.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.