This task can be performed using Toolport
All your MCP servers. One port.
Best product for this task
Toolport
dev-tools
Toolport is a free, open-source, local-first MCP gateway. Set up and authenticate each MCP server once, and every AI client (Claude, Cursor, VS Code, Codex and the rest) shares it. Your agent loads a handful of meta-tools instead of hundreds, cutting tool-token overhead up to 91%. Every call is fingerprinted for tampering, your API keys stay in the OS keychain, and you get a full audit trail. No containers, no sign-up.
What to expect from an ideal product
- Toolport acts as a single local MCP gateway, so you enter each API key once into your OS keychain and every client β Claude, Cursor, VS Code, Codex β reads from that same authenticated source without any duplication or copy-pasting across config files.
- Instead of loading hundreds of individual tools into every AI session, Toolport exposes a small set of meta-tools per client, reducing tool-token overhead by up to 91% and keeping context windows free for actual work.
- There is no Docker setup, no cloud account, and no sign-up form β Toolport runs locally, installs in minutes, and stores nothing outside your own machine, which makes it practical for developers who work in air-gapped or compliance-sensitive environments.
- Every MCP call routed through Toolport is fingerprinted at the request level, giving you a full audit trail that shows exactly which client triggered which tool, when, and with what parameters β something raw multi-client MCP setups cannot provide out of the box.
- Because Toolport is open-source and free, teams can inspect the gateway code, self-host it on a shared dev machine, and onboard new clients like Codex or any future MCP-compatible agent without reconfiguring server credentials from scratch each time.
