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
- Tracks the MCP spec
- Ships SEP-1649 (Server Cards)
- MIT licensed
- Code-signed for macOS
- Free · No account
Transports
Speak the protocol any server speaks.
MCPOrbit supports both MCP transports — stdio for local processes, and streamable-http (with SSE fallback) for remote servers. 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
- Fallback to SSE for older HTTP servers
Registries
Bring all your servers.
The Official Registry ships out of the box. Server Cards make any domain a peer registry. Pluggable adapters are the next chapter.
Official MCP Registry
registry.modelcontextprotocol.ioThe canonical, curated list of MCP servers. Search, filter, paginate, add — 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
future · 2026Adapter interface ships today; community-built adapters (npm registry-style indexes, internal company directories) are expected to land in 2026.
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 edits the right file at the right path on your OS, adds the 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.
Ask for the IDE you want, on [email protected].
In practice
How teams turn MCPOrbit into an integration platform.
Patterns we see in the wild, written in the voice of the user-type. Not testimonials — the underlying shape of a workflow.
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 drift before it lands in production.”
Pattern · PM/QA
“I run drift tests weekly against the servers our agent depends on. When a vendor changes a tool description, I see it before our customer sees it.”
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?
Yes — the pluggable registry adapter contract is exactly that. Build an internal directory of your company's MCP servers; ship it as an adapter; install MCPOrbit; point it at the adapter.
Linux/Windows support?
On the roadmap. macOS today.
