Use case · Server author
Hand your users a tool, not a README.
MCPOrbit is the path of least resistance from 'I built an MCP server' to 'people use my MCP server.' Publish a Server Card; users paste your URL; tools run in seconds.
The 60-second demo
Faster than typing 'npm install'.
The fastest way to onboard someone to your server: tell them to install MCPOrbit (free, signed, no account), paste your domain, and click your tool. They see your output in real time. They didn't read your README. They didn't write a config file.
Distribution
Server Cards as your install path.
Drop a .well-known/mcp.json on your domain. Every MCPOrbit user pointed at your domain discovers your server automatically. No registry submission, no approval queue.
- Single source of truth
- Multiple servers per domain
- Works for private MCP servers behind a VPN
- Implements Server Cards discovery
The agent panel as a developer aid
See how a real model uses the tools you shipped.
Point the Agent panel at your own server during development. Tick the tools a run may reach and watch which ones the model actually picks, with the arguments it sent — the fastest way to find a tool description that reads well to you and badly to a model.
Agent panel
Agent panel →Run your own server through a real agent loop and watch which tools it picks.
The shape of it
Build server
Implement your MCP server in any language.
Publish Server Card
Drop the .well-known/mcp.json file.
Demo via MCPOrbit
Anyone who points the app at your domain discovers and runs it.
Iterate on real feedback
Run your changes through the agent locally first.
