Toolport (formerly Conduit)
Fix the tool-list bloat slowing your AI agent
158 followers
Fix the tool-list bloat slowing your AI agent
158 followers
Your agent got slower the more MCP servers you added, and it's not the model. Every server dumps its whole tool list into context on every request: 3 servers cost ~24k tokens before you even say hi. Toolport (formerly Conduit) puts them behind one local gateway that exposes 3 meta-tools the agent searches on demand. Measured: 97% less tool overhead per request, ~90% fewer tokens, same task success. Cloud or local, one tool or five. Keys in your OS keychain. Free and open source.
This is the 2nd launch from Toolport (formerly Conduit). View more
Toolport for Teams
Launching today
Set up your team's MCP servers once; every member's AI client gets them (Claude, Cursor, Codex, +18 more). Only the server set syncs, never a secret: keys stay in each member's OS keychain, so there's no central vault to breach. Govern centrally: access control, roles, spend budgets, tighten-only safety policy, rug-pull alerts, CSV audit trail. Up to 91% fewer tokens via lazy discovery. Hosted or self-hosted. Free for up to 5; Team is $39/mo flat, then $12/person past 5. 14-day trial, no card.
Free Options
Launch Team / Built With
Toolport (formerly Conduit)
Hey PH! A few weeks ago I launched Toolport here: a local gateway that gives your AI agent every MCP server through a handful of meta-tools instead of hundreds of definitions. The most common question since has been "how do I roll this out to my team without pasting API keys into Slack?"
Toolport for Teams is the answer. Define your team's MCP server set once; every member's Toolport syncs it, and every AI client they use gets it (Claude, Cursor, Codex, 21 clients total).
The best part: only the server set syncs, never a secret. Each member authenticates locally and keys stay in their own OS keychain. There's no central credential vault to breach, because there is no central credential vault.
The obvious question is "why not just commit an mcp.json to the repo?" Because a file can't enforce anything. A checked-in config is advice a teammate can edit or ignore. Toolport applies the shared set and its safety policy on every member's machine, at runtime:
Tighten-only safety policy: admins can force destructive-call approval, injection screening, and drift quarantine fleet-wide. A member can never loosen them.
Rug-pull alerts: if a tool quietly rewrites its own definition on anyone's machine, the whole team is notified (Slack, Discord, or MS Teams).
Central governance: per-server access control, roles (admin, billing, auditor, viewer), and monthly spend budgets with alerts.
Audit without surveillance: every member's tool calls, usage, and cost, exportable as CSV. Metadata only, never request contents.
Zero-key onboarding: a new teammate pastes one invite code and has the whole stack. Nobody DMs a key.
Up to 91% fewer tokens from lazy discovery, measured at identical task success, multiplied across every developer and agent on the team.
Hosted by us, or fully self-hosted on your own network when compliance demands it. Same product, your call.
Pricing is simple: free for up to 5 people. Team unlocks every governance feature above for a flat $39/month for up to 5, then $12/month per additional teammate. Start with a 14-day trial, no card required, and use PHLAUNCH for 50% off your first 3 months. The core Toolport app stays free and open source.
If you're running MCP across a team today, I'd love to hear how you're sharing configs and keys right now, and what you'd need to see before trusting a tool like this with your team. I'll be in the comments all day.
Finally something that actually fixes the MCP token bloat problem. Set it up as a local gateway in a few minutes and watched my context usage drop dramatically with the same tasks completing fine.
Toolport (formerly Conduit)
@mirag1jy Thank you! That's the experience I was chasing. The same tasks completing the same way, just without paying the tool-definition tax on every single request. We measured it end to end at 74-91% fewer total tokens depending on the server mix, and it compounds as you add servers, because the context cost stays flat instead of growing with every new tool.
Today's launch takes that same idea team-wide: one shared server set that syncs to every member's AI clients, keys staying in each person's own keychain, and the token cut multiplied across every developer and agent on the team.
How many servers are you running through it, and on which client? Always curious where the ceiling is in the wild.
The OS keychain integration is a really thoughtful touch, especially since most tools just dump API keys into env files. Glad the project is open source too.
Toolport (formerly Conduit)
@yarenk8za Thanks Yaren! The env-file thing is exactly what pushed me to the keychain. Plaintext keys in dotfiles end up committed, pasted into Slack, or synced somewhere they shouldn't be, and every desktop OS already ships a solved answer to this, so the gateway just uses it.
One precision on open source, because I'd rather be exact than take credit for a label that only half fits. The core Toolport app, the gateway everyone installs, is MIT and stays that way. The Teams server we launched today is a commercial product on top of it (you can self-host it, and it's free for up to 5 people). The keys-never-leave-your-machine part is the same in both.
What does your current setup look like, env files and all? Curious what you'd want handled that isn't yet.
Plugged three MCP servers into Toolport and watched the prompt tokens drop from a wall of text to almost nothing, the gateway approach just works and keeping keys in the OS keychain feels right.
Toolport (formerly Conduit)
@caner334669 Thanks Caner! That moment is exactly what got me building this. Three servers is right about where the tool definitions start crowding out your actual work, so hearing the wall of text collapse for you is great.
And agreed on the keychain part. Once keys are out of config files, sharing the setup stops being scary, which is basically what today's launch is. That same gateway, but the server set syncs across a whole team while everyone's keys stay in their own keychain.
Out of curiosity, which three servers are you running? And is it just you on MCP or do teammates use it too? It's super useful for me to know who's hitting this today.