Need help? We're here for you.
If you have questions, feedback, or need help with Prava Toolport, reach out:
We aim to respond within 48 hours.
Toolport sits between your AI agent and all your MCP servers. Instead of every server loading its full tool list into the agent's context, the agent gets three small meta-tools — search_tools, get_tool_schema, and invoke_tool — and discovers the right tools on demand. Same power, a fraction of the context.
Any MCP-speaking client: Claude Code, Codex, Cursor, or your own agent. You register Toolport as a single MCP server in your agent's configuration, and it fronts every server you've added.
Add Toolport as an MCP server in your Claude Code configuration (one entry). Toolport announces the search → schema → invoke workflow to the agent automatically when it connects — no system-prompt changes needed.
No. Toolport speaks standard MCP to your servers. Point it at the same server definitions you use today; it connects, asks each server for its tools, and indexes them. When a server's tools change, Toolport re-checks it automatically.
Yes. Toolport uses cross-lingual embeddings, so a query in one language finds tools described in another — for example, a Japanese query can find an English-described tool.
Semantic search and the index are fully local. You need network access only to reach remote MCP servers you've configured; local (stdio) servers and search itself work offline.
For remote servers that require OAuth (for example, Microsoft or GitHub hosted services), Toolport opens the provider's sign-in in your browser and stores the tokens locally on your Mac. Your credentials never pass through Prava Labs.
Every new install starts a 14-day trial with all components enabled — including the Team features (network serving, governance, security pre-screen, metering). After the trial, the app settles to your purchased tier.
Same engine, different install and capabilities. The Mac App Store edition sells the Solo tier as a monthly or annual subscription billed by Apple; it is sandboxed and remote-only — it fronts hosted (HTTP) MCP servers with OAuth sign-in. The Developer ID edition is a notarized direct download purchased from pravalabs.app and unlocked with a signed license key; it carries the Team and Enterprise tiers and does everything the App Store edition does plus local (stdio) servers and multi-user network serving. If your workflow depends on local servers (filesystem, local CLIs) or a shared team registry, you want Developer ID.
Your tier unlocks components. Solo (Mac App Store) covers the core registry with your own remote servers. Team (Developer ID) adds local servers, multi-user network serving, governance receipts, security pre-screening, cost metering, and central management. Enterprise (Developer ID) adds SSO, air-gapped licensing, audit export, and priority support. See the plans overview.