One gateway, every tool
Agents connect to a single stdio server. mcphub proxies every downstream server behind it and exposes their tools as server__tool — names never collide.
How the gateway works
Define your servers once in mcphub.yaml. mcphub fronts them all on a single stdio connection, syncs 12 agent harnesses for you, and shows which tools actually earn their context budget.
$ brew install abdul-hamid-achik/tap/mcphubSee it run
One YAML file in, twelve synced harnesses out — and a local ledger of what every server actually costs you.
$ mcphub sync
» claude (claude, gateway) → ~/.claude.json
update mcphub
» codex (codex, gateway) → ~/.codex/config.toml
update mcphub
» copilot (copilot, gateway) → ~/.copilot/mcp-config.json
update mcphub
» crush (crush, gateway) → ~/.config/crush/crush.json
update mcphub
» hermes (hermes, gateway) → ~/.hermes/config.yaml
update mcphub
» opencode (opencode, gateway) → ~/.config/opencode/opencode.json
update mcphub
Dry run. Re-run with --write to apply (a .bak is saved first).How it works
mcphub initWrite mcphub.yaml once — or import the servers your agents already declare with --from-agents.
mcphub sync --writePush the right config into every harness. Dry-run by default, a timestamped .bak before any write.
mcphub mcp serveYour agent connects to one gateway that proxies everything — and every call is recorded locally.
Syncs into 12 harnesses