0bridge and MetaMCP
MetaMCP is an open-source MCP aggregator you run yourself: it puts many MCP servers behind one endpoint. 0bridge does the same job hosted, and adds history, memory, secrets and control of coding agents. As of 2026-10-01.
Last updated
The short version#
Use MetaMCP if you want to host the aggregator yourself and keep all of it on your own infrastructure. Use 0bridge if you'd rather not run it, and want your sessions, memory and secrets handled too.
Side by side#
| 0bridge | MetaMCP | |
|---|---|---|
| What it is | A hosted MCP endpoint, a dashboard and a CLI | A self-hosted MCP aggregator |
| Where it runs | 0bridge's servers | Yours |
| One endpoint for many servers | Yes | Yes |
| Sign-in to services | OAuth and API keys, kept encrypted per user | As you configure it |
| Session history and resume | Yes | Not its job |
| Secrets vault, memory, agent control | Yes | Not its job |
| Client side | 0b setup configures your tools | You point each client at it |
| Cost | Free for one person | Your hosting |
MetaMCP's column is how we understand it on the date above; check its documentation for what it does today.
When not to use 0bridge#
- You need everything to run on infrastructure you control. 0bridge is hosted; only your secrets and personal files are sealed from it.
- You want to modify the aggregator itself. The 0bridge client is source available; the service is not open source.
- Your network can't reach the internet. 0bridge needs it.