MCP without the
complexity.
Test an MCP server in 60 seconds.
Universal binary · ~64 MB · Free
Built for the MCP ecosystem
- Tracks the MCP spec
- Ships SEP-1649 (Server Cards)
- MIT licensed
- Code-signed for macOS
- Free · No account
Press ⌘K
One window. Every server. Zero setup.
Open MCPOrbit, search the server you heard about, hit return. The protocol handshake, tool discovery, and parameter forms are all there waiting.
mcporbit — connect
Search MCP servers
⌘K- Open↵
Linear
Official PostgreSQL
OfficialSlack
CommunityNotion
CommunityFilesystem
Official
5 results
— free, no signup, no telemetry.
create_issue
Create a new issue in a Linear team
"team": "ENG", "title": "Add dark mode", "description": "Users want..."
"id": 42, "url": "https://...", "state": "open"
Capabilities
Three jobs in one window.
Discovery, evaluation, and integration each have their own workflow today. MCPOrbit collapses them into a single surface.
Discover
Find every MCP server that exists
Browse the Official MCP Registry without leaving the app, and let MCPOrbit auto-discover servers from any domain that publishes a Server Card.
- Search the Official MCP Registry from inside the app
- Auto-discover servers via .well-known/mcp.json (SEP-1649)
- Pluggable registry adapters for additional sources
Evaluate
See what a server actually does
Connect, browse the tools, run them with typed inputs, watch responses stream back. No glue code, no agent in the loop.
- Auto-generated forms from each tool's JSON Schema
- Side-by-side comparison across servers and models
- Live request/response log with full JSON-RPC traffic
Integrate
Ship it into your stack
One click installs any tested server into Claude Desktop, Cursor, or Windsurf. Export schemas as OpenAPI for everywhere else.
- Add to IDE for Claude Desktop, Cursor, Windsurf
- Export any server's schema as OpenAPI
- Postman-style environment variables with {{variable}} substitution
Server Cards · SEP-1649
First MCP manager to shipAuto-discover MCP servers from any domain.
MCPOrbit reads .well-known/mcp.json from any domain and indexes every MCP server it finds — no manual registration, no centralised directory. Think DNS for MCP tools.
- 01
The server publishes — drop a JSON file at
https://yourdomain.com/.well-known/mcp.json - 02
MCPOrbit indexes it — point the app at the domain; every server shows up automatically.
linear
claude-opus-4.7287ms> tools/call list_issues
{ "team": "growth", "status": "open" }
< response
{ "issues": [4 items], "cursor": "..." }
postgres
gpt-5-mini412ms> tools/call list_issues
{ "team": "growth", "status": "open" }
< response
{ "issues": [4 items], "cursor": "..." }
Comparison Mode
One prompt. Every server. Every model.
Run the same task across any combination of MCP servers and language models. See outputs, tool-call traces, latency, and failures side by side. The eval workflow you currently fake with five terminal tabs.
- Test how claude-opus-4.7 and gpt-5 handle the same MCP server
- Diff structured outputs across two builds of the same server
- Spot performance regressions before they land in production
Use cases: vetting a new server before integration · regression testing during development · benchmarking model providers.
Agent panel
Bring your own model. Then drift-test what it touched.
MCPOrbit's Agent panel runs against any model provider you have credentials for — Anthropic, OpenAI, OpenRouter, Bedrock, Groq, Ollama, LM Studio, or any OpenAI-compatible endpoint. Use it to drive end-to-end tests, including drift detection: baseline a server's capabilities once, re-run later, and MCPOrbit highlights every schema change, new tool, or removed permission.
Drift detection
Baseline → re-run → diff. Catch breaking changes before they break production.
Local + remote
Plug in ollama for fully-offline runs, or hit any OpenAI-compatible inference endpoint behind your VPC.
Add to IDE
From bench to production in one click.
Once you've vetted a server in MCPOrbit, install it into your editor with a guided handoff. MCPOrbit validates the target's config, writes the entry, and surfaces any conflicts before you save.
No more copy-pasting JSON snippets and hoping the file format hasn't changed.
Registry browser
The Official MCP Registry, inside the app.
Search and filter the entire Official MCP Registry without ever opening a browser. MCPOrbit caches results locally, supports lazy pagination, and adds new sources as the ecosystem grows.
mcporbit — registry
Search the Official MCP Registry
2,400+ serverslinear
Issues, projects, and cycles
+ Addpostgres
Query, schema, migrations
+ Addgithub
PRs, issues, code search
+ Addslack
Channels, messages, files
+ Addnotion
Pages, databases, blocks
+ Addfilesystem
Read, write, watch local files
+ AddBuilt for builders
The smaller details that add up.
Every shipped feature that doesn’t need its own section. Each one quietly removes a step you used to do by hand.
Environment variables
Postman-style {{variable}} substitution across connections, headers, and tool inputs. Define dev, staging, prod once. Use them everywhere.
Request/response log
Every JSON-RPC message between MCPOrbit and a server, timestamped and inspectable. The DevTools you’ve always wanted for MCP.
Copy as curl
One-click export of any tool call as a curl command. Or as the raw schema. Or as the response.
OpenAPI export
Export any connected server’s schema as OpenAPI. For docs, for Postman collections, for any other tool that doesn’t speak MCP yet.
Schema explorer
Every tool’s JSON Schema rendered as a readable form, with required fields, defaults, enums, and inline descriptions surfaced.
Code-signed and notarized
No Gatekeeper warnings, no right-click-to-open. Universal binary for Apple Silicon and Intel.
Auto-updates
Background updates via electron-updater. Always on the latest spec build, never reinstalling DMGs.
No telemetry by default
MCPOrbit never phones home. The future opt-in telemetry that powers the Popular MCP Servers report has a public schema and a one-click delete.
MIT licensed
Free, open, modifiable. Fork it, embed it, ship a derivative. We’d rather grow the ecosystem than build a moat.
Time-to-value
From curiosity to confidence.
Connect a server you heard about.
Paste the launch command or URL. MCPOrbit handles the handshake, capability negotiation, and pulls in every tool. You see the server work in a couple of seconds.
Vet it before it hits production.
Run the tools manually. Compare two models on the same task. Drift-test against a snapshot. Decide whether to integrate based on what the server actually does, not what the README claims.
Ship it into your stack.
Add the server to Claude Desktop, Cursor, or Windsurf with one click. Or export the schema as OpenAPI. By the time you’ve integrated, you’ve already seen every tool fail in every way it can.
Community
What the MCP community is saying.
“Finally a tool I can hand a non-engineer and say “click this.” MCPOrbit replaced about ten lines of glue code I was about to write.”
@server-author
MCP server author · GitHub
“The drift test caught a parameter rename that would have silently broken our agent in production.”
@platform-eng
ML platform engineer · Discord
“Server Cards in MCPOrbit feels like the moment npm registry finally clicked. Drop a JSON file, get discovered.”
@open-source-dev
Open-source maintainer · X
“We use it as the eval bench for every server we consider. It’s faster than writing a test harness.”
@eval-engineer
AI infrastructure · Reddit
“Comparison mode replaced an afternoon of manual benchmarking. Two model providers, three servers, one window.”
@indie-builder
Indie hacker · X
“Inspecting JSON-RPC traffic in a real UI saved hours. I was about to rebuild this myself.”
@modelcontext-dev
LLM engineer · Discord
Have a story to share? [email protected]
Honestly
How does MCPOrbit fit in?
| Approach | Speed | Trust |
|---|---|---|
| Clone the README + write a client | Slow | Hope-driven |
| Use Postman with a custom collection | Medium | Doesn’t model MCP primitives |
| Browse a registry directory in a browser | Fast to find | Can’t actually run anything |
| Open MCPOrbit and connect | Seconds | Run, compare, drift-check, ship |
We're not trying to replace Postman. We're trying to do what Postman did for HTTP — but for MCP.
Indexed via Server Cards · MCP Registry · Total servers reachable through MCPOrbit
2,400+
Updated as new servers join the network.