Use the same MCP servers in Claude, Cursor and VS Code
Why this beats copying JSON between clients#
Every client keeps MCP servers in a different file and format: mcpServers in Claude Desktop and Cursor, servers in VS Code, mcp_servers TOML in Codex, context_servers in Zed. Copying the same entry into each means editing each one again whenever a key rotates.
With Toolport:
- One place to add and authenticate a server.
- One secret store, the OS keychain, instead of a key in every client config.
- One entry per client (
toolport), written for you, with the old config backed up first.
The three steps#
Add from the catalog, import a client's existing servers, or paste a config.
Open Clients, select the client, optionally choose a profile, and click Connect to Toolport.
The client re-reads its config and serves every Toolport-managed tool through the one toolport server.
Give different clients different servers#
Use profiles. A profile is a named set of enabled servers. Connect Cursor to a "Work" profile and Claude Desktop to "Personal", and each only sees its own servers. See Profiles and clients.
Two accounts for the same service#
Add the service twice, for example "GitHub (work)" and "GitHub (personal)", authenticate each with its own account, and enable one per profile. Tool names are namespaced per server, so the two never collide.
Which clients are supported#
Toolport auto-detects 35 clients, including Claude Desktop, Claude Code, Cursor, VS Code, Codex, Devin Desktop, Zed, Gemini CLI, Copilot CLI, Cline, Roo Code, Continue, Goose and LM Studio. Full list with config paths: Supported clients.
Clients that install Agent Plugins 1.0 packages (VS Code, GitHub Copilot CLI and others) can connect by installing the plugin in packaging/agent-plugin/toolport/ instead. Disconnect that client in the Clients view first, or the gateway connects twice.