Integrations
Everything MCPOrbit plugs into.
Transports, registries, model providers, and IDE targets — every external surface MCPOrbit talks to, in one map.
Built for the MCP ecosystem
- Speaks MCP revision 2025-11-25
- Reads .well-known/mcp.json (Server Cards)
- Runs locally
- Code-signed for macOS
- Free · No account
Transports
Speak the protocol any server speaks.
MCPOrbit supports all three MCP transports — stdio for local processes, streamable-http for remote servers, and sse for older HTTP servers. You choose the transport when you create the connection; MCPOrbit does not switch between them for you. No half-implementations, no transport-specific feature gaps.
- stdio (process spawn, stdin/stdout JSON-RPC)
- streamable-http (HTTP POST + SSE for long-lived streams)
- Auto-detection from Server Cards
- MCPOrbit supports sse for older HTTP servers
Registries
Bring all your servers.
The Official Registry and Smithery both ship out of the box. Server Cards make any domain a peer registry. Both adapters implement the same contract, and MCPOrbit enables them by default.
Official MCP Registry
registry.modelcontextprotocol.ioThe canonical, curated list of MCP servers. Search and paginate — all from inside the app.
Learn more →Server Cards (decentralised)
.well-known/mcp.jsonAny domain that publishes a card is a registry of one (or many). MCPOrbit treats it as a peer of the Official Registry.
Learn more →Pluggable adapters
registry.smithery.aiThe adapter interface ships with two registries behind it — Official and Smithery's 11,000+ server index. Server Cards cover the same ground for a single domain, without an adapter.
Learn more →Model providers
Eight providers ship today. Any OpenAI-compatible endpoint is the ninth.
IDE targets
Three IDEs today. More as the ecosystem demands.
Claude Desktop
MCPOrbit shows the path — ~/Library/Application Support/Claude/claude_desktop_config.json — and generates the block to merge into it. Restart Claude Desktop to load the server.
Cursor
Same block, merged into ~/.cursor/mcp.json. Reload the window with Cmd+Shift+P → Developer: Reload Window.
Windsurf
Same block again, in ~/.codeium/windsurf/mcp_config.json. Restart Windsurf to load the server.
More IDEs are on the way.
Built for
The workflows MCPOrbit is built to support.
Four workflow shapes the product is designed around, sketched in the voice of the user-type. These are illustrations of intent, not accounts of anyone's use.
Pattern · server author
I publish a .well-known/mcp.json on my domain. My users install MCPOrbit, paste my URL, and see every tool I ship. I never have to write installation docs again.
Pattern · agent dev
I evaluate every server in MCPOrbit before it touches our agent. Comparison mode against our prompt suite catches behaviour changes before they land in production.
Pattern · PM/QA
I run a candidate server's tools through a form and read the MCP log, without building an agent first. What I test today is what our engineers integrate tomorrow.
Pattern · security
I scan the schemas of every tool a candidate server exposes and use OpenAPI export to feed our review pipeline. The bench is MCPOrbit; the artefact is OpenAPI.
Integrations FAQ
Is there a Hiver/Slack/Asana-style integration?
No, and there won't be. MCPOrbit integrates with the MCP ecosystem, not with business SaaS. The MCP servers themselves are the bridge to your other tools.
Do you plan a public API?
Not today. MCPOrbit's surface is the desktop app. The public API surface is the MCP protocol itself.
Can I use MCPOrbit to build my own integration platform?
Not through a registry adapter — MCPOrbit compiles its two registry adapters in and never loads one from disk. Publish a Server Card at your domain and MCPOrbit discovers the servers it lists, with no adapter involved.
Linux/Windows support?
On the roadmap. macOS today.
