Prava Toolport App Icon
🔍 One Broker · Every Tool, On Demand · Any Language

Every tool your agent needs.
None of the context bloat.

Prava Toolport is a local semantic tool registry that sits between any AI agent and all your MCP servers — handing the agent only the few right tools for each task, instead of every tool definition at once.

Get Toolport — free 3-day trial · Solo $9.99/mo or $89.99/yr
Mac · Menu Bar App Windows · x64 & ARM64 (soon) Claude Code Codex Cursor Any MCP Agent
search_tools Describe the task in plain language — any language
get_tool_schema Load full details for one tool, only when needed
invoke_tool Run it, proxied to the right downstream server

Your Agent Is Drowning in Tool Definitions

Every MCP server dumps its whole tool menu into the agent's context. A few servers together can eat a large share of the window before any work starts. Toolport fixes that with progressive disclosure.

🔍

Semantic Tool Search

The agent describes what it wants to do — "turn off the broken approval flow" — and Toolport returns the top matching tools from across all your servers. Three meta-tools stand in for your whole catalog, so the agent loads a handful of definitions instead of hundreds — and the built-in receipt shows exactly what that saved on your setup.

🌍

Any Language In, Any Language Out

Cross-lingual embeddings mean a query in Japanese finds a tool described in English, and vice versa. Most tool layers are English-only; Toolport is multilingual by architecture.

🏠

Local-First, Not a Cloud Service

The search index and embedding model live on your machine — unlike hosted tool-routing gateways. Discovery works offline, round trips stay on-device, and nothing about your tools is sent anywhere. Air-gap-friendly by design.

🤝

Agent-Agnostic, Not Model-Locked

Works with any MCP-speaking client — Claude Code, Codex, Cursor, or your own agent — not tied to one model's platform. One registry entry replaces a page of server configs, and Toolport teaches connecting agents the workflow automatically.

🔐

Hosted Servers, OAuth Built In

Connect remote MCP servers over HTTP with sign-in handled for you — including enterprise services like Microsoft 365 and GitHub. One-click Sign In per connector; tokens are stored locally, never proxied through us.

🧩

First-Party Connectors, Bundled

Seven "Prava for …" connectors ship inside the app — Power Platform, Microsoft 365, Apple, Apple Docs, Markets, Reddit, Google Workspace. Discrete tools, structured output, confirm-gated writes. Only available with Toolport.

📊

Menu-Bar Command Center

A native macOS menu-bar app supervises everything: add servers from a catalog or by hand, watch the live savings receipt, edit policy gates, re-index on demand, and run diagnostics — no terminal required.

More Than Routing: One Local Engine

Plenty of tools now trim tool bloat — most are cloud services, or locked to a single model. Toolport's difference is the combination: one local-first, on-device, multilingual broker that does progressive tool disclosure and bundles web Retrieve, semantic Cache, durable Memory, source Grounding, Policy gates, and savings Metering — the whole disclosure layer in one private engine on your machine, not a stack of hosted services. All on every plan.

🧾

Trace — The Savings Receipt

Every search is metered: what loading your full catalog would have cost vs. what the agent actually received. The receipt lives in the menu bar and in a get_savings call — with a resettable trip meter beside the lifetime total. Proof, not promises.

🛡️

Policy — Gates Before Anything Runs

Read-only that knows reads from writes — globally or per server — plus dry-run, allow/deny lists, and confirm-to-send for outbound actions. One config protects every connector, and a send that wasn't approved with its exact arguments doesn't run. Safety is never paywalled.

✂️

Results — Outputs, Condensed

Oversized tool outputs (logs, JSON dumps, tables) arrive condensed and clearly marked, with the recent full payload retrievable page by page — condensing never silently drops content.

📖

Retrieve — Passages, Not Pages

Agents call search_context and the fetch-and-extract happens in the engine: web pages and your local docs come back as a few cited passages. The 40k-token page never enters the prompt. Bring-your-own search key optional.

♻️

Cache — Don't Pay Twice

A repeated read-safe call — even paraphrased, even in another language — serves the prior result and skips the downstream call. Only tools that declare themselves read-only are eligible; approved actions never cache.

🧠

Memory — Facts That Persist

Agents store durable facts explicitly (remember / recall / forget) with provenance and expiry. Recall is semantic and cross-lingual: a fact stored in English is found by a Japanese query. Everything stays on your machine, with a viewer in Settings.

⚖️

Grounding — Trust the Right Sources

Retrieved passages carry trust tiers, cross-source corroboration counts, and duplicate collapse — so agents can tell documentation from SEO spam before quoting it.

Set Up in Minutes

One install. One registry entry in your agent. Done.

1

Install Toolport

Toolport lives in your menu bar and runs the registry engine locally — a native app for Mac today, Windows coming soon.

2

Add Your MCP Servers

Pick servers from the built-in catalog or add your own. Toolport connects to each one, asks for its tools, and files everything into a local searchable index.

3

Point Your Agent at Toolport

Register Toolport as a single MCP server in Claude Code, Codex, Cursor, or any MCP client. That one entry now fronts every server you added.

4

Work Normally

Your agent discovers tools on demand — search, load one schema, invoke. When a server's tools change, Toolport re-checks it automatically.

Toolport vs. Connecting Servers Directly

Progressive disclosure beats loading everything up front.

Direct MCP Connections Prava Toolport
Context cost Every tool definition loaded up front 3 meta-tools instead of every definition
Adding another server Context shrinks with each one Constant cost, any number of servers
Finding the right tool Agent scans a wall of definitions Semantic search over intent
Non-English queries English-only matching Cross-lingual by design
Small / on-device models Choke first on tool bloat Tiny footprint fits any model
Oversized outputs Raw dumps flood the context Condensed, full payload retrievable
Repeated calls Full cost, every turn, every subagent Semantic cache — cross-turn, cross-language
Risky actions Whatever the tool allows Policy gates: read-only, dry-run, confirm-to-send
Proof of savings None Trace receipt on every install; governance & audit for teams

One App. Pick Your Tier.

Everyone gets the same app — your plan simply unlocks components. Solo is available today on Mac; Team & Enterprise and Windows are coming soon.

Team
Available soon
Mac & Windows · license key · per seat
  • Everything in Solo
  • Network serving — shared team registry
  • Per-seat licensing & seat management
  • Governance & audit receipts
  • Security pre-screen of tools
  • Token / cost metering
  • Central management & analytics
Enterprise
Available soon
Mac & Windows · license key · per seat
  • Everything in Team
  • Air-gapped / on-prem deployment
  • Offline license validation
  • SSO (OIDC — Entra, Okta, Google)
  • Audit export to your SIEM

Every tier, on your platform

Mac

macOS 14+ · Apple Silicon (M-series)

Two ways to get it — same native menu-bar app, same engine:

  • Mac App Store — Solo, subscription billed by Apple. Sandboxed, so remote (HTTP/OAuth) servers only.
  • Direct download (Developer ID) — Solo today via license key (Team & Enterprise soon). Notarized DMG; adds local (stdio) servers on top of remote.
  • All platform modules and first-party connectors on both

Windows Coming Soon

Windows 10 & 11 · Native x64 & ARM64

A native Windows tray app is built and in testing — Fluent Settings window, server catalog, per-connector Sign In/Out, and the live savings receipt. Same engine, built natively for both architectures.

  • Free download, 3-day trial — Solo unlocks with a license key
  • Local and remote MCP servers
  • Same modules and first-party connectors*

*macOS-only connectors (e.g. Prava for Apple) remain Mac-exclusive. Join the waitlist to hear the moment it's available.

Prices shown in USD. Solo on Mac is billed by Apple through the Mac App Store, or bought here and unlocked with a license key on the direct-download edition (see Download). Windows is built and in testing — coming soon as a free download with a 3-day trial, unlocked the same way. Team and Enterprise launch soon on both platforms, unlocked with a signed license key. Local (stdio) servers require the Windows edition or the direct-download Mac edition. Team and Enterprise are licensed per seat (one seat = one user or agent); run the registry on as many servers as you need for load or redundancy — servers aren't a licensing unit.

Your Tools. Your Machine. Your Business.

Toolport talks only to the MCP servers you configure — nothing else.

Local Search Index On-Device Embeddings Your Servers Only OAuth Tokens Stay Local No Telemetry No Tracking

Built With

Model Context Protocol TypeScript Node.js Bun Multilingual Embeddings SwiftUI WinUI 3 stdio + HTTP Transports OAuth 2.0 Ed25519 Licensing macOS Sandbox