Every AI client, sharing the same MCP servers.
Set up a server once in Toolport and every client below can use it. One toggle per client: Toolport writes its gateway entry into the client's own config, next to anything already there, and your full server set shows up with lazy discovery keeping the token cost flat.
Chat & local model apps
-
Claude Desktop
Anthropic's desktop app, connected to every server through one gateway entry.
set up Claude Desktop -
LM Studio
local modelsLocal models with tool use, without pasting server configs into mcp.json by hand.
set up LM Studio -
Jan
local modelsThe open source local assistant, with your full server set one toggle away.
set up Jan -
BoltAI
The macOS AI chat app, sharing the same servers as your editor and CLI.
set up BoltAI -
Open WebUI
local modelsConnects natively over the gateway's HTTP/OpenAPI endpoint. No bridge, no mcpo.
set up Open WebUI
Code editors & IDEs
-
Cursor
One gateway entry in ~/.cursor/mcp.json instead of a server list to maintain.
set up Cursor -
VS Code
Copilot agent mode with every server, from one entry in your user mcp.json.
set up VS Code -
Windsurf
Cascade reaches every server through one mcp_config.json entry.
set up Windsurf -
Zed
A context_servers entry in settings.json, edited surgically and never wiped.
set up Zed -
Antigravity
Google's agent-first editor, with your servers shared from the same gateway.
set up Antigravity -
Kiro
AWS's agentic IDE, connected through one entry in its settings mcp.json.
set up Kiro
CLI agents & terminals
-
Claude Code
One global gateway entry in ~/.claude.json; every project inherits it.
set up Claude Code -
Codex
CLI and desktop app share ~/.codex/config.toml; Toolport writes the TOML for you.
set up Codex -
Gemini CLI
Google's terminal agent, wired to every server through settings.json.
set up Gemini CLI -
Goose
local modelsBlock's open source agent; Toolport writes the extensions entry in config.yaml.
set up Goose -
Amazon Q
Amazon Q Developer CLI, connected through ~/.aws/amazonq/mcp.json.
set up Amazon Q -
Warp
The agentic terminal, reading Toolport's gateway from its file-based MCP config.
set up Warp -
Hermes
Nous Research's agent, configured via the mcp_servers map in config.yaml.
set up Hermes
Editor extensions
Using a client that isn't listed? If it reads an mcpServers-style config, the
gateway entry usually works as a manual add, and we're quick to add first-class support.
Open an issue or ask on
Discord.