Every MCP server, in every AI agent.Set up once. It just keeps working.

1. 1

   Find what you have

   Toolport detects the AI agents on your machine and lists the MCP servers already in their configs.

2. 2

   Bring them in

   Import them in one go. API keys move out of plain-text config files and into your OS keychain.

3. 3

   Connect each agent

   Each agent's direct server entries are replaced by one Toolport entry. A backup is kept, and you can restore it from the app.

4. 4

   Check it works

   Toolport lists every server's tools through the gateway and shows which ones are ready.

[mcp_servers.linear]
url = "https://mcp.linear.app/mcp"

[mcp_servers.stripe]
command = "npx"
env = { STRIPE_SECRET_KEY = "sk_live_..." }

[mcp_servers.cloudflare]
command = "npx"
env = { CLOUDFLARE_API_TOKEN = "..." }

# and again in Cursor, Claude Code, Zed...

# the only entry Toolport writes
[mcp_servers.toolport]
command = "/home/you/.config/Toolport/bin/toolport-gateway"

# 5 servers and 1,379 tools behind it.
# Keys live in your OS keychain.

• A server crashes or times out

  Retrying

  Retries it in the background, waiting a little longer each time, from 2 seconds up to 5 minutes. Your agents keep their one entry.

• A sign-in expires

  Needs sign-in

  Stops retrying that server and asks you to sign in again, instead of hammering it with requests that will fail.

• You add or remove a server

  Ready

  Toolport updates the shared server set immediately. Agents that support tool-list notifications refresh live; others need one reload.

• You run six agents at once

  Ready

  Agents on this machine share one host gateway, so ordinary servers start once. Servers tied to a project folder start once for that folder.

• You want your old setup back

  Restored

  Toolport backs up each agent's config before every edit. Disconnect restores what it moved.

• Skills

  Every skill on your machine, grouped by where it came from, with its state in each agent: on, name only, off, or another copy wins. Turn one off and Toolport writes that agent's own setting.

• Rules

  The rules files each agent reads, such as CLAUDE.md and AGENTS.md, the links it follows to reach them, and the @import lines it loads or skips.

• Needs a look

  A skill you turned off in one agent that still loads in another, a link to a missing folder, an import an agent ignores. Toolport offers a fix where one is safe.

Toolport

Toolport changes a skill only through the agent's own setting and backs up the config file first. It never moves or deletes your skill folders to turn one off. How the Skills page works

Measured with REA and Ghidra on two crackme tasks, five runs per setup, DeepSeek V4.1 Flash in OpenCode 1.19.3. Claude Code, which has its own tool search, saw no savings from Toolport. Your numbers depend on your agent and servers. Method and raw numbers

Compare every feature and read the FAQ