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.0.
For docs, for Postman collections, for Swagger UI, for any tool that doesn't speak MCP yet but speaks OpenAPI.
- One connected server at a time
- One POST path per tool
- Each tool's input schema as the request body
- Saved as a JSON document
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 to clipboard
One button. No ceremony.
Run a tool and the result header carries Copy Response and Copy as curl — the call you just made, as a runnable request. The schema tab has Copy Schema. Handing a server to an editor copies an mcpServers block. The clipboard is the export format we use most.
- Copy as curl — the call you just ran
- Copy Response — the result JSON
- Copy Schema — the tool's input schema
- Copy Config — an mcpServers block
tool result
curl -X POST http://localhost:3000/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"tools/call",
"params":{"name":"search_docs",
"arguments":{"q":"retries"}},"id":1}'Schema and export FAQ
Which OpenAPI version?
3.0.0, written as JSON. Every tool becomes one POST /tools/<name> path with that tool's input schema as the request body.
Where does the copied curl point?
At http://localhost:3000/mcp. That endpoint is a fixed placeholder, not your connection's real transport — treat the copied command as a template and point the URL at your own server. For a stdio server there is no URL to point it at; the body is still a valid tools/call request.
Are environment variables encrypted at rest?
No. Environment variable values — and the credentials you paste into a connection — are stored unencrypted in ~/Library/Application Support/MCPOrbit/mcporbit-data.json. They stay on your machine and are never sent to us, but they are not encrypted, so treat that file as sensitive. AI provider API keys are the exception: those are encrypted with Electron safeStorage, which is Keychain-backed on macOS.
Does copy-as-curl include my secrets?
Only what you typed into the form. The copied body carries your arguments exactly as entered, before substitution runs — so a {{TOKEN}}placeholder stays a placeholder. Your connection's headers aren't copied at all; the command sends only Content-Type. Type a literal secret into a field and it will be in there.
