About
Why MCPOrbit exists.
We were three users of MCP, frustrated by the same friction. We built the tool we wanted. Then it became the tool other people wanted.
MCP shipped in late 2024. The protocol was elegant. The client experience was not. The path from “I heard about an MCP server” to “I'm using it” ran through README files, hand-rolled config edits, and IDE-specific gotchas.
We started building MCPOrbit as an internal tool. The first version was a 200-line Electron app that connected to one server and rendered tool schemas. It wasn't ambitious. It was useful.
Useful is the highest goal here. MCPOrbit is the place you go when you want to look at MCP, evaluate a server, drift-test something, or graduate a server into your IDE. It is not trying to be a platform. It is trying to be a good tool.
Principles
What we hold to.
Stay calm.
No superlatives. No '10x your agents.' MCPOrbit is a tool, not a movement.
Stay free.
MIT licence, no accounts, no telemetry by default. Trust is earned slowly and lost in one HN thread.
Stay aligned.
MCPOrbit tracks the spec. When the protocol changes, we change. We don't fork the protocol; we serve it.
Ship the boring features too.
Code-signing, env vars, copy-as-curl, schema export. The unglamorous parts are what make the glamorous parts trustworthy.
Team
Who builds MCPOrbit.
MCPOrbit is built by Anthropic engineers. We work on the product directly with the MCP community in Discord and GitHub.
Keep going
