Use case · PM and QA
Look at MCP without writing any code.
Connect to an MCP server, run its tools through a form, and inspect the results — without writing code or building an agent.
Tools as forms
Schema becomes UI. Click run.
Every MCP tool's JSON Schema becomes a typed form. Required fields are required. Enums become dropdowns. A schema default shows as a placeholder. Click run; see the response. The same form is the documentation.
Debug surface
The MCP log as a debug surface.
Every tool call is captured and inspectable. When something goes wrong, the log tells you which tool was called, with what arguments, what came back, and how long it took. No code involved.
Protocol changes
MCPOrbit speaks MCP revision 2025-11-25.
That is what the shipped build offers at connect time. MCPOrbit also connects to servers on 2025-06-18, 2025-03-26, 2024-11-05 or 2024-10-07. Three transports are supported — stdio, HTTP+SSE and Streamable HTTP — and MCPOrbit serves the roots, sampling and elicitation requests a server sends back. The 2026-07-28 revision is not implemented: it replaces the initialize handshake this build relies on, so a server that speaks only 2026-07-28 will not connect.
