Toolport README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Toolport listing page.
Toolport
Set up your MCP servers once. Use them in every AI client.
Toolport is a local gateway for MCP, the protocol that gives AI apps access to tools like GitHub, Slack, and databases. Connect your servers once, then share them across Claude, Cursor, Codex, VS Code, and other clients.
Download · Website & demo · Discord
Why Toolport?
- Less context overhead. Agents search for tools when they need them instead of loading every tool definition up front. See the benchmarks.
- One setup for every client. Add and authenticate each server once. Use profiles to choose which servers each client can access.
- Keys stay local. Credentials live in your OS keychain, outside client configs.
- Control over tool calls. Disable tools, require approval for destructive calls, and review activity in one place.
- Shared agent rules. Write instructions once and apply them to supported clients, with a preview before changes are written.
Get started
- Download Toolport for Windows, macOS, or Linux.
- Add a server from the catalog, import an existing setup, or paste a server config.
- Authenticate the server, then open Clients and connect your AI apps.
Installers and release notes are also on GitHub Releases. For Linux desktop integration, see Toolport on Omarchy.
Documentation
- Supported clients and setup
- Profiles, environment variables, and configuration
- Agent rules and permissions
- Headless gateway and Docker
- Open WebUI and agent plugin
- Security and troubleshooting
- Changelog
Development
Requires Node.js and stable Rust, plus the platform dependencies described in Contributing.
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.