0bridge and editing each tool's config by hand
You can add MCP servers to every AI tool yourself, in each tool's own config file or settings screen. For one tool and a couple of servers, that is fine. 0bridge is for when it stops being fine. As of 2026-10-01.
Last updated
The short version#
Edit by hand if you use one or two tools and a few servers and rarely change them. Use 0bridge when you have several tools, several machines or several accounts, because the same servers need adding and signing in to again in each of them.
Side by side#
| 0bridge | By hand | |
|---|---|---|
| Adding a service | Connect once; every tool has it | Add to each tool, on each machine |
| Signing in to a service | Once | In each tool |
| A new machine | 0b setup and sign in | Copy the config again |
| Chat apps | One custom connector | One per app, per service |
| Secrets | A vault used by name | .env files or config values |
| Session history and resume | Yes | Each tool's own, not shared |
| Control | A hosted service and an account | None; every file is yours |
| Cost | Free for one person | Your time |
Doing both#
You can keep servers you added by hand next to 0bridge's entry; the endpoint is one entry in each tool. 0b history hooks off takes out the hooks 0bridge added.
When not to use 0bridge#
- You use one tool, and its own settings already do what you need.
- You don't want a hosted service in the path of your tool calls. Calls to connected services go through 0bridge; their content isn't logged, but they do pass through.
- You want to audit every config file by eye. Direct entries are the simplest thing to audit.