Feature · Handoff
From bench to production in one click.
Once you've vetted a server in MCPOrbit, install it into your editor with a guided handoff. MCPOrbit validates the target's config file, writes the entry, and surfaces any conflicts before you save.
Three IDEs supported
Same UI. Three trusted targets.
Each IDE has its own MCP config file, in its own format, at its own path. MCPOrbit knows where to find it, how to read it, and how to write the entry without breaking what's already there.
Claude Desktop
MCPOrbit edits the right file at the right path on your OS, adds the server entry, and pings the app to reload.
Cursor
Adds the server to Cursor's MCP config. Validates the existing config first; never silently overwrites.
Windsurf
Adds to Windsurf's config in the same shape Cursor uses; same validation.
Why guided
Why a guided install instead of 'copy this JSON'.
The format of these config files isn't stable. Every IDE versions it differently. Half of the support requests we see in the MCP community are “I copy-pasted this and it broke.” MCPOrbit reads the live file, parses it, and writes a valid mutation. We catch existing entries with the same name. We surface schema mismatches. We show you the diff before we apply it.
- Reads existing config
- Validates JSON before write
- Diff preview
- Backups the previous config to a sibling .bak file
Diff preview
Add to IDE FAQ
Does MCPOrbit edit my file silently?
No. We always show the diff before write. You confirm or cancel.
What if I already have a server with the same name?
MCPOrbit detects the conflict and offers to rename, replace, or cancel.
Can I add to multiple IDEs at once?
Yes. Pick all three from the handoff dialog; MCPOrbit writes all three.
Will you support more IDEs?
Yes, as the ecosystem grows. Open an issue in the repo if there's one missing you care about.
