The agents
ExonUI writes setup for 11 agents. Each one stores its servers in its own format, and the wizard writes the format yours expects. Our setup formats were checked against each agent's documentation and command line.
| Agent | Formerly | MCP documentation |
|---|---|---|
| Claude Code | Claude Code docs (opens in a new tab) | |
| Cursor | Cursor docs (opens in a new tab) | |
| VS Code | VS Code docs (opens in a new tab) | |
| Codex | Codex docs (opens in a new tab) | |
| OpenCode | OpenCode docs (opens in a new tab) | |
| Google Antigravity | Google Antigravity docs (opens in a new tab) | |
| Gemini CLI | Gemini CLI docs (opens in a new tab) | |
| Devin Desktop | Windsurf | Devin Desktop docs (opens in a new tab) |
| Zed | Zed docs (opens in a new tab) | |
| Cline | Cline docs (opens in a new tab) | |
| Conductor | Conductor docs (opens in a new tab) |
Check and troubleshoot
These apply whichever tool you connect. For problems specific to one tool, open its connect guide from its catalog page.
Claude Code
Check: run claude mcp list. Start a session and run /mcp to see the server, its status and its tools.
- Servers in a project
.mcp.jsonstay inactive until you approve them the first time Claude Code starts in that folder. claude mcp addsaves to the local scope by default: only you, only this project. Add--scope userto use it in every project.- If a server shows as failed, run
claude --debugto see its startup output.
Claude Code's own MCP documentation (opens in a new tab)
Cursor
Check: Open Cursor Settings, find the MCP section and check the server is enabled with its tools listed.
- Project servers live in
.cursor/mcp.json; servers for every project live in~/.cursor/mcp.json. - After editing the file by hand, toggle the server off and on in settings, or restart Cursor.
- The Output panel (MCP Logs) shows why a server failed to start.
Cursor's own MCP documentation (opens in a new tab)
VS Code
Check: Run MCP: List Servers from the Command Palette, then open Copilot Chat in Agent mode and check the tools picker.
- VS Code asks you to trust a server the first time it starts. Accept it, or the tools stay hidden.
code --add-mcpwrites to your user profile, so the server works in every workspace.- Use MCP: List Servers → Show Output to see startup errors.
VS Code's own MCP documentation (opens in a new tab)
Codex
Check: run codex mcp list. In a Codex session, run /mcp to see connected servers and their tools.
- Codex reads
~/.codex/config.toml. A project.codex/config.tomlis only read in projects you have trusted. - Codex doesn't expand
~or environment variables incommand. Use a full path in the config file. - Servers that need a sign-in: run
codex mcp login <name>.
Codex's own MCP documentation (opens in a new tab)
OpenCode
Check: run opencode mcp list. Start OpenCode in the project; the server's tools are available to the agent straight away.
- OpenCode reads
opencode.jsonfrom the project root, or~/.config/opencode/opencode.jsonfor every project. - Environment variables use the
{env:NAME}syntax inside the config file. - Servers that need a sign-in: run
opencode mcp auth <name>.
OpenCode's own MCP documentation (opens in a new tab)
Google Antigravity
Check: In the editor, open the … menu at the top of the agent panel and choose MCP Servers. In the app, open Settings → Customizations → Installed MCP Servers. In the agy CLI, type /mcp.
- The app, the editor and the
agyCLI share~/.gemini/config/mcp_config.json. A project's.agents/mcp_config.jsonapplies only to that project. - Antigravity doesn't expand
~or environment variables in the config. Use full paths. - Click Refresh next to Installed MCP Servers after editing the file by hand.
Google Antigravity's own MCP documentation (opens in a new tab)
Gemini CLI
Check: run gemini mcp list. In a Gemini CLI session, run /mcp to see each server, its status and its tools.
- Since June 2026, Gemini CLI works with a paid Gemini API key or an enterprise licence. If you signed in with a personal Google account, use Google Antigravity instead.
gemini mcp addsaves to the project's.gemini/settings.jsonby default. Add--scope userto save it to~/.gemini/settings.jsonfor every project.- Local servers only show as connected in folders you trust. Run
gemini trustin the project folder. - Gemini CLI hides environment variables that look like secrets from servers unless the server's
envblock lists them.
Gemini CLI's own MCP documentation (opens in a new tab)
Devin Desktop
Check: run devin mcp list. In Devin Desktop, open Customize from the Agents window, choose MCPs and check the server under This computer.
- Devin Desktop and the Devin CLI share the same MCP files:
.devin/mcp_config.jsonin a project,.devin/mcp_config.local.jsonfor just you, and~/.config/devin/mcp_config.jsonfor every project. - Servers set up in Windsurf's old
mcp_config.jsonaren't read. Add them again in the Devin format. - Servers that need a sign-in: run
devin mcp login <name>, or click Authenticate next to the server.
Devin Desktop's own MCP documentation (opens in a new tab)
Zed
Check: Open Settings → AI → MCP Servers. A green dot next to the server means it is running.
- Zed reads MCP servers from the
context_serverskey, notmcpServers. Servers under any other key are ignored. - Run zed: open settings file from the command palette to edit your settings.
- Zed asks before running each tool. Change this with
agent.tool_permissionsin your settings.
Zed's own MCP documentation (opens in a new tab)
Cline
Check: run cline config mcp. In VS Code or JetBrains, open the MCP Servers panel in Cline and check the server is listed with its tools.
- In the editor, open the MCP Servers panel, choose Configure and click Configure MCP Servers to edit
cline_mcp_settings.json. - The Cline CLI keeps its own list in
~/.cline/data/settings/cline_mcp_settings.json, separate from the editor's. - Remote servers need
"type": "streamableHttp". Without it, Cline falls back to the older SSE transport.
Cline's own MCP documentation (opens in a new tab)
Conductor
Check: run claude mcp list. In a Conductor session, click the plug icon in the composer or run /mcp-status to see each server's status.
- Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
- Each workspace is a separate git worktree. Servers added with plain
claude mcp addonly apply to the folder you ran it in, so use--scope useror a committed.mcp.json. - Conductor runs on macOS. Environment variables for local servers can go in
.conductor/settings.local.toml, under[environment_variables].