Skip to main content
Glama

Toolport

CI Latest release License: MIT Discord Glama quality

Your AI agents' tools, skills and rules. Set up once, on every machine.

Toolport is a free desktop app and local gateway for MCP, the protocol that gives AI apps tools like GitHub, Linear and databases. Add a server once and Claude Code, Codex, Cursor, VS Code and 40+ other agents can all use it.

Download · Website & demo · Discord

Toolport Servers screen with eight servers ready and one turned off

Why Toolport?

  • One setup for every agent. Toolport finds the agents on your machine, imports the servers they already have and gives each one a single Toolport entry. Fix a server once and every agent gets the fix. Access sets choose which servers each agent can reach.

  • Every machine, too. Pro syncs your servers to each computer you sign in on. Secrets stay on each machine.

  • Skills and rules in one place. See which skills and rules files (CLAUDE.md, AGENTS.md and others) each agent actually loads, turn skills on or off per agent, and link agents to the rules file the others already share. See skills and rules.

  • Safe by default. API keys move out of plain-text configs into your OS keychain. Toolport pins every tool definition and flags changes, such as a tool you approved rewriting its description, plus hidden instructions in descriptions and results. The default Ask level holds destructive calls for your OK. Strict also quarantines changed tools and blocks detected injection. Every call is in Activity. See security.

  • Lighter on context where it helps. For agents that send every tool definition on every request, Toolport's search tools can cut input tokens by several times. Claude Code, Codex and Cursor already defer tools, so Toolport's Auto mode gives them the full list (Claude Code up to 800 tools). See the benchmarks.

Related MCP server: Proxima

Get started

  1. Download Toolport for Windows, macOS, or Linux.

  2. Add a server from the catalog, import an existing setup, or paste a server config. Curated servers that need launch arguments show a Launch setup section in the app.

  3. Authenticate the server, then open Clients and connect your AI apps. Restart or reload the client once so it picks up Toolport.

Installers and release notes are also on GitHub Releases. On Arch and Omarchy, the pacman repository keeps Toolport on your normal update path.

Working with a team? Toolport Teams shares server configuration and policies while each member keeps their own credentials.

Documentation

Development

Requires Node.js and stable Rust, plus the platform dependencies described in Contributing.

npm ci
npm run build:gateway
npm run tauri dev

See Contributing for testing and build instructions.

Toolport Teams

Share server configuration and policies across a team while each member keeps their own credentials. Hosted and self-hosted options.

License

The desktop app and gateway are MIT licensed.

Available Tools

4 tools
toolport_call_toolA

Invoke a tool discovered via toolport_search_tools. Pass the tool's exact name (as returned by the search) and put ALL of that tool's parameters INSIDE the arguments object (matching its input schema) - not at the top level next to name. Never invent or guess an identifier (teamId, accountId, projectId, etc.): if a required value isn't known, first call a list or get tool on the SAME server to obtain it, then call this with the real value.

Inputs: name (required), arguments.

toolport_fetch_resultA

Read more of a large tool result that Toolport truncated. When a result is too big for context, Toolport returns the head plus a cursor in a [Toolport shaped this result] marker; call this with that cursor and the offset shown in the marker to page through the rest. Nothing was lost.

Inputs: cursor (required), offset (required).

toolport_search_toolsA

Your single gateway to every connected MCP server and ALL their tools. Try this FIRST for ANY external action or data the user asks for - sending or listing email, deployments, payments, databases, repos, issues, files, web search, etc. Do NOT reach for an unrelated tool or tell the user a capability is unavailable until you have searched here; if the service is connected, its tool is here. Returns matching tools with their exact name, description, and input schema; call one with toolport_call_tool. Once a result matches what you need, call it - do NOT keep searching for a better one (the first result includes its full schema and is ready to call). Pass server (a name/prefix like "resend") to scope to one server, and pass an EMPTY query with server to list ALL of that server's tools. If the result says more tools matched than were shown, narrow with server or raise limit before concluding a capability is missing - many servers expose a generic API bridge (a single write/create tool), so search by capability, not just an exact operation name. toolport_status lists every server prefix and its tool count. Large input schemas may be omitted from broad results (flagged schemaOmitted) to keep responses small - search a tool's exact name to get its full schema.

Inputs: query (required), limit, server.

toolport_statusA

Report Toolport's status: the MCP servers enabled in the active profile, each server's tool count, and how many tokens (and dollars) lazy discovery has saved you so far.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: status reports server state, search_tools discovers tools, call_tool invokes them, and fetch_result pages through truncated results. There is no meaningful overlap between any two tools.

    Naming Consistency4/5

    All tools share the consistent toolport_ prefix and most follow a verb_noun pattern (search_tools, call_tool, fetch_result). toolport_status is slightly less consistent because it uses a noun without an explicit action verb, but the pattern remains predictable.

    Tool Count5/5

    Four tools is a well-scoped size for a gateway/meta-server: discovery, invocation, result pagination, and status reporting each earn their place. The set is neither bloated nor thin for its purpose.

    Completeness5/5

    The tool set covers the full lifecycle of using a unified MCP gateway: finding tools, invoking them, retrieving large results, and checking server status. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      A local AI gateway that connects multiple AI providers (ChatGPT, Claude, Gemini, Perplexity) to your development environment via MCP tools, enabling coding, search, analysis, and more without API keys.
      75 npm
      1,203
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
      33 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Centralized encrypted gateway that routes requests to 11+ LLM providers (API keys and CLI subscriptions) through a single OpenAI-compatible endpoint, with MCP tools for vault operations, code search, and shared state.
      30
      14 npm
      2
      MIT