Toolport icon

Toolport

Toolport is a free, open source local MCP gateway for connecting one set of MCP servers to multiple AI agents with local secret handling.

Toolport

Local MCP gateway for individual users and teams

Toolport is a free, open source local MCP gateway that lets you connect multiple AI agents to the same set of MCP servers from one place. Instead of configuring GitHub, Slack, databases, or other tool servers separately in each agent, you add or import a server once in Toolport and then switch it on in the clients you use.

The product is aimed at people who work across several AI agents and want less duplicated setup, smaller tool context, and local handling of credentials. The site also positions Toolport for teams, where shared server sets, access control, and audit features are available through Toolport for Teams.

Core capabilities

One gateway for many agents

Add an MCP server once and reuse it across supported agents, so you do not have to paste the same server config and API key into each app separately.

Lazy tool discovery

Tools are discovered on demand through a small set of meta-tools rather than dumping an entire server's tool list into context, which keeps the working context smaller.

Tool-integrity checks

The app fingerprints tool definitions and flags changes that may indicate a rug pull, plus hidden instructions in descriptions that could poison an agent's behavior.

Local secret handling

API keys are stored in your OS keychain and injected at runtime, so they do not need to live in a config file or cloud service.

Shared governance for teams

Toolport can expose a server or tool to everyone on a team, with controls for per-server access, per-tool allow-lists, and tighten-only safety policy in the Teams offering.

Observability and audit trail

The app shows per-server latency, error rates, and an audit trail of tool calls, giving users visibility into what happened inside the gateway.

Practical ways to use Toolport

  • Reuse the same tool stack across agents

    A developer who moves between Claude, Cursor, and Codex can configure GitHub, Slack, or database servers once in Toolport and use the same servers in each agent without rebuilding configs by hand.

  • Reduce tool-definition bloat

    A user who cares about prompt efficiency can keep the agent context smaller by letting Toolport expose a few meta-tools and fetch server tools only when they are needed.

  • Govern a shared team setup

    A team lead can share an approved MCP server set with teammates while keeping each person's credentials on their own machine and enforcing shared access rules.

  • Inspect tool usage and policy enforcement

    An admin reviewing behavior can use the audit trail, latency, and error data to see how tool calls performed and whether a policy was enforced as expected.

  • Keep tool access local and checked

    A cautious operator can rely on integrity checks and local secret storage to reduce the risk of tampered tool definitions or exposed API keys.

Pros and Cons

Pros

  • Reduces repeated setup by letting you configure a server once and reuse it across supported agents.
  • Keeps secrets on the local machine through the OS keychain instead of requiring a cloud vault for the core app.
  • Provides tool-integrity checks and local safety screening to catch changed or suspicious tool definitions.
  • Supports Windows, macOS, and Linux through downloadable desktop builds.
  • Offers team governance features such as shared server sets, access controls, and audit trails in the Teams product.

Cons

  • The source material does not provide a full, page-by-page list of supported MCP servers or every agent integration.
  • Pricing is only partially documented in the collected sources, so some plan details may require checking the live pricing or teams pages.
  • The Teams product includes self-hosting and hosted options, but the evidence here does not fully explain the operational or security tradeoffs of each deployment model.

FAQ

How does setup work?

Toolport installs as a local desktop app and then connects to your MCP servers once. After that, you toggle it into supported agents such as Claude, Cursor, or VS Code and reload the agent so it can search tools on demand.

What platforms does it support?

The source describes Toolport as a free, open source, local MCP gateway for Windows, macOS, and Linux. The download page offers Windows x64, macOS Apple Silicon and Intel, and Linux AppImage or Debian/Ubuntu builds.

Is Toolport only for solo users?

Toolport is designed for individual use and team use. The home page emphasizes one local hub for every AI agent, while the Teams page adds shared server sets, governance, and per-member local authentication for groups.

Does Toolport change how agents see tools?

No. Toolport loads tools on demand instead of exposing every tool definition to the agent at once, and it uses lazy discovery to keep the tool context smaller. The site says this reduces token usage while maintaining task success.

How does Toolport handle secrets and tool safety?

Toolport includes integrity checks that fingerprint tools and flag rug pulls or tool poisoning, and it keeps API keys in the OS keychain. The product is described as local-first with no cloud account required for the core app.

Quick Facts

Category
Developer Tool
Product type
Local MCP gateway
Platforms
Windows, macOS, Linux
Core workflow
Add or import an MCP server once, then toggle it into supported AI agents
Source domain
toolport.app
License / access
Free, open source (MIT) for the core app