Toolport

~ Local gateway, Rust + Tauri v2

A desktop app ships a `toolport-gateway` binary that speaks MCP to every client (Claude, Cursor, Codex, and the rest). Each client points at one gateway, a server is authenticated once and appears in all of them, and new servers propagate without touching each app config.

~ Lazy discovery / meta-tools

Instead of the full catalog, the gateway advertises four compact meta-tools (`toolport_status`, `toolport_search_tools`, `toolport_call_tool`, `toolport_fetch_result`) and the agent searches and calls on demand. That meta-tool set is a constant 781 tokens regardless of how many downstream tools exist. A couple more appear only when approvals or agent-control features are on.

~ Measured, graded benchmarks

A separate benchmark repo runs one command against committed fixtures with a deterministic tiktoken tokenizer, no keys and no network. Standing-context reduction: 99.8% on Stripe (587 tools, 415k down to 781), 99.8% on GitHub (1194 tools), 99.7% on OpenAI. On a frontier model, up to 91% fewer total tokens at the same graded task success (correct answers, not just completion).

~ Honest about amortized cost

The headline is the standing cost, the tokens tools occupy on every request just by being available. Lazy mode adds per-search result tokens, so a session touching 30 distinct tools pays for about 30 tools worth of search results, still far below loading all 587 every turn. The docs report the standing reduction and state this plainly instead of claiming it as a whole-session saving.

~ Per-agent scoping + governance

Each client sees only the servers in its profile, so a coding agent literally cannot call a tool outside its scope. Any tool can be toggled off, or every destructive tool hidden at once, and every call is recorded with per-server latency and error rates.

~ Keys in the OS keychain

Clients only ever say "talk to Toolport." OAuth tokens and API keys live in the OS keychain and are injected at runtime, never written into client config files where they leak into dotfiles and backups.

~ Supply-chain security on the path

Because every call flows through one gateway, Toolport screens tools for rug-pulls and tool-poisoning and can require human-in-the-loop approval (`toolport_confirm`) before a destructive or newly changed tool runs. That is detection a per-client config could never enforce.

~ Teams control plane

A paid multi-tenant service (Rust + Axum on Neon Postgres) syncs one set of servers, policies, and agent instructions to every member client, with seats, invites, SSO/RBAC, complete audit history, and Stripe billing. The desktop app stays MIT and free; Teams is source-available (BSL) and self-hostable free for up to five people.