MCP gateway
Toolport
Set up your MCP servers once, then use them in every AI client. Toolport is a local gateway that shares one set of MCP servers across Claude, Cursor, Codex, VS Code and 30+ other clients, with keys kept in your OS keychain.
Why Toolport#
- Less context overhead. Agents search for tools when they need them instead of loading every tool definition up front.
- One setup for every client. Add and authenticate each server once. Profiles decide which servers each client sees.
- Keys stay local. Credentials live in the OS keychain, outside client configs.
- Control over tool calls. Disable tools, require approval for destructive calls, review activity in one place.
- Shared agent rules. Write instructions once and apply them to supported clients, with a preview before anything is written.
Start here
Quickstart
Install, add a server, connect your first client.
Installation
Desktop app, Arch pacman repo, or build from source.
Supported clients
The 35 clients Toolport detects and the config file each one uses.
Answers
One MCP setup for Claude, Cursor and VS Code
The short answer and the three clicks.
Reduce MCP token usage
Lazy discovery and the measured 74 to 91% cut.
Self-hosted MCP gateway for a team
Headless gateway, scoped tokens, Toolport Teams.
Reference