Every tool, one port. One MCP setup for all your AI agents
A free, open source, local MCP gateway. Set up each server once and every AI agent shares it (Claude, Cursor, VS Code, Codex, and 29 more). Instead of dumping every tool definition into context, it exposes a few meta-tools your agent searches on demand. Benchmarked and graded for correct answers, that's up to 91% fewer tokens at the same task success. Secrets live in your OS keychain, not client configs. Rug-pulls and tool poisoning get flagged, and destructive calls can wait for your approval.
Hey everyone, Tyler here. I built Toolport because I was configuring the same MCP servers over and over. Claude Desktop, Claude Code, Cursor, Codex, VS Code, each one wanted its own JSON file with the same API keys pasted in as plain text.
The second problem showed up after the servers were connected. Every MCP server dumps its full tool list into context on every request. Three servers cost me about 24,000 tokens of definitions before I'd asked anything. Toolport sits between your agents and your servers and advertises a handful of small meta-tools instead, so the agent searches for tools when it actually needs them. Benchmarked on a frontier model and graded for correct answers, that works out to up to 91% fewer total tokens at the same task success. On a real 415-tool catalog the definition overhead drops 99.5%.
Since a gateway is on the path anyway, I used that position for security. Toolport fingerprints every tool and flags rug-pulls and tool poisoning, marks injection-looking tool output as data rather than instructions, and can pause destructive calls until you approve them from the app. Your agent asks before it drops the table.
If you saw the Teams launch back in July, the free app has moved a lot since then. Toolport now speaks the latest MCP spec (2026-07-28) on both sides, while older clients and servers keep working untouched. Code mode lets an agent run a whole tool sequence as one sandboxed server-side script instead of round-tripping every call through the model. Approvals are bound to the exact arguments you saw when you approved them. Client support is up to 33 apps, and there's a headless Docker gateway if you don't want the desktop app at all.
It's MIT licensed and fully local, nothing routes through my servers. If you try it, tell me which client or server you'd want supported next. That list drives the roadmap.
About Toolport on Product Hunt
“Every tool, one port. One MCP setup for all your AI agents”
Toolport launched on Product Hunt on August 8th, 2026 and earned 0 upvotes and 1 comments, placing #59 on the daily leaderboard. A free, open source, local MCP gateway. Set up each server once and every AI agent shares it (Claude, Cursor, VS Code, Codex, and 29 more). Instead of dumping every tool definition into context, it exposes a few meta-tools your agent searches on demand. Benchmarked and graded for correct answers, that's up to 91% fewer tokens at the same task success. Secrets live in your OS keychain, not client configs. Rug-pulls and tool poisoning get flagged, and destructive calls can wait for your approval.
On the analytics side, Toolport competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Toolport performed against the three products that launched closest to it on the same day.
Who hunted Toolport?
Toolport was hunted by Tyler. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Toolport including community comment highlights and product details, visit the product overview.
Tyler