Feature · Schema & Export
The boring stuff, done right.
Schemas you can read, exports you can ship, and environment variables that follow you across every connection.
Schema explorer
The form is the documentation.
Every tool a server exposes ships with a JSON Schema. MCPOrbit renders that schema as a readable form — required fields, defaults, enums, descriptions surfaced inline. The same form you use to call the tool is the documentation for the tool.
list_issues · form view
one of: open · closed · archived
OpenAPI export
Export any server as OpenAPI 3.1.
For docs, for Postman collections, for Swagger UI, for any tool that doesn't speak MCP yet but speaks OpenAPI.
- Single-server export
- Multi-server export
- Component schemas preserved
- Examples preserved when present
Environment variables
Postman-style variables, MCPOrbit-wide.
{{variable}} substitution across connections, headers, tool inputs, and registry adapters. Define dev, staging, prod once, switch with a single dropdown.
environments
Copy as anything
Right-click. Copy. Done.
Copy a tool call as curl. Copy a tool's schema. Copy a server's entire connection config. Copy a saved comparison as a runnable snippet. The clipboard is the export format we use most.
- Copy as curl
- Copy as schema
- Copy as MCP JSON
- Copy as agent prompt
right-click menu
Schema and export FAQ
Which OpenAPI version?
3.1, with downgrade-to-3.0 toggle for tools that haven't caught up.
Are environment variables encrypted at rest?
Yes. MCPOrbit uses the macOS Keychain for any value flagged as a secret.
Does copy-as-curl include my secrets?
Only if you've inlined them. Variables stay as {{TOKEN}} placeholders unless you opt in to “expand variables on copy.”
