Overview

Supported clients

Client Config file Format
Claude Desktop <config>/Claude/claude_desktop_config.json JSON (mcpServers)
Claude Code ~/.claude.json JSON (mcpServers)
Cursor ~/.cursor/mcp.json JSON (mcpServers)
Factory Droid ~/.factory/mcp.json JSON (mcpServers)
Crush $CRUSH_GLOBAL_CONFIG/crush.json, or $XDG_CONFIG_HOME/crush/crush.json (~/.config/... by default) JSON (mcp)
VS Code <config>/Code/User/mcp.json JSON (servers)
Devin Desktop (Cascade) ~/.codeium/windsurf/mcp_config.json JSON (mcpServers)
Devin Local / CLI %APPDATA%/devin/mcp_config.json (Windows), ~/.config/devin/mcp_config.json (macOS; Linux default) JSON (mcpServers)
OpenCode ~/.config/opencode/opencode.json JSON (mcp)
Kilo Code ~/.config/kilo/kilo.jsonc JSONC (mcp)
Codex $CODEX_HOME/config.toml (default ~/.codex/config.toml) TOML (mcp_servers)
Copilot CLI ~/.copilot/mcp-config.json JSON (mcpServers)
Grok Build $GROK_HOME/config.toml (default ~/.grok/config.toml) TOML (mcp_servers)
Continue ~/.continue/config.yaml YAML (mcpServers)
Antigravity ~/.gemini/config/mcp_config.json JSON (mcpServers)
Gemini CLI $GEMINI_CLI_HOME/.gemini/settings.json (default ~/.gemini/settings.json) JSON (mcpServers)
Qwen Code $QWEN_HOME/settings.json (default ~/.qwen/settings.json) JSON (mcpServers)
JetBrains Junie ~/.junie/mcp/mcp.json JSON (mcpServers)
Cline <config>/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json JSON (mcpServers)
Roo Code <config>/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.json JSON (mcpServers)
Warp ~/.warp/.mcp.json JSON (mcpServers)
Amazon Q ~/.aws/amazonq/mcp.json JSON (mcpServers)
Kiro ~/.kiro/settings/mcp.json JSON (mcpServers)
Kimi Code $KIMI_CODE_HOME/mcp.json (default ~/.kimi-code/mcp.json) JSON (mcpServers)
Zed ~/.config/zed/settings.json JSON (context_servers)
LM Studio ~/.lmstudio/mcp.json JSON (mcpServers)
Jan <data>/Jan/data/mcp_config.json JSON (mcpServers)
BoltAI ~/.boltai/mcp.json JSON (mcpServers)
Pi ~/.pi/agent/mcp.json JSON (mcpServers)
Oh My Pi ~/.omp/agent/mcp.json JSON (mcpServers)
Goose ~/.config/goose/config.yaml YAML (extensions)
Hermes ~/.hermes/config.yaml YAML (mcp_servers)
AnythingLLM <config>/anythingllm-desktop/storage/plugins/anythingllm_mcp_servers.json JSON (mcpServers)
Witsy <config>/Witsy/settings.json JSON (mcpServers)
Amp ~/.config/amp/settings.json JSON (amp.mcpServers)

<config> is your OS application-config dir (%APPDATA% on Windows, ~/Library/Application Support on macOS, ~/.config on Linux); <data> is the data dir (~/.local/share on Linux, the same as <config> elsewhere). Zed and Goose paths vary slightly by OS; Toolport resolves the right one automatically.

Codex walkthrough#

1
Enable servers

In Toolport, add or enable the MCP servers you want Codex to use.

2
Connect Codex

Open Clients, select Codex, optionally choose a profile, and click Connect to Toolport.

3
Check the config

Toolport adds a single [mcp_servers.toolport] entry to $CODEX_HOME/config.toml (default ~/.codex/config.toml). Other TOML keys and MCP servers are preserved, and the existing file is backed up first.

4
Start a new session

Codex re-reads the config and the Codex row in Toolport shows connected to Toolport.

Older installs with [mcp_servers.conduit] are renamed to toolport on the next Toolport launch.

HTTP and OpenAPI consumers#

Open WebUI, n8n, LibreChat and custom agents connect over HTTP instead of a config file. See Open WebUI.

Agent plugin#

Clients that install Agent Plugins 1.0 packages (VS Code, GitHub Copilot CLI, the Copilot app) can install the plugin in packaging/agent-plugin/toolport/. It launches the gateway the desktop app already installed, so it shares your servers, credentials and profiles.

If the client is already connected in the Clients view, disconnect it there first. Otherwise the gateway connects twice and every meta-tool shows up in duplicate.

Updated

Was this page helpful?