How-to
Export a server's schema as OpenAPI
Open a connected server's Tools panel and click Export OpenAPI. Writes an OpenAPI 3.0.0 JSON document, one POST path per tool.
Select a connected server and open its Tools panel. Click Export OpenAPI at the bottom of the tool list, then choose where to save. The button is disabled until the server has listed at least one tool.
MCPOrbit writes an OpenAPI 3.0.0 document as JSON. Every tool becomes one path — POST /tools/<name> — carrying the tool's own input schema as the request body, its description as the summary, and a single 200 response. There is no version toggle and no YAML output.
One limitation worth knowing before you import the file anywhere. Each tool's input schema is copied through exactly as the MCP server published it, with no conversion to the subset of JSON Schema that OpenAPI 3.0 accepts. Servers built on the MCP TypeScript SDK stamp a $schema keyword on every tool schema, and a schema that carries one is not valid under OpenAPI 3.0. In MCPOrbit 1.1.72 that has two visible consequences: schema validators reject the exported document, and Postman accepts the file but imports every request with an empty body. Deleting the $schema lines from the exported file resolves both.
This doc is in progress.
