Skip to content
Conductor TerminalConductor Terminal

Supported Agent Targets

Conductor Terminal can write, verify and remove the editor’s MCP client entry in each of the agents below. Most are available in two scopes:

  • Project — the config file lives in your Unreal project directory and applies to that project only.
  • User — the config file lives in your home directory and applies everywhere. These targets carry a -user suffix.

Paths in the Config file column are relative to the project root or your home directory according to the Scope column.

JSON targets

Section titled “JSON targets”
Target Scope Config file Root key
claude Project .mcp.json mcpServers
claude-user User .claude.json mcpServers
cursor Project .cursor/mcp.json mcpServers
cursor-user User .cursor/mcp.json mcpServers
copilot Project .vscode/mcp.json servers
copilot-user User .copilot/mcp-config.json mcpServers
gemini Project .gemini/settings.json mcpServers
gemini-user User .gemini/settings.json mcpServers
qwen Project .qwen/settings.json mcpServers
qwen-user User .qwen/settings.json mcpServers
opencode Project opencode.json mcp
opencode-user User .config/opencode/opencode.json mcp
crush Project .crush.json mcp
crush-user User .config/crush/crush.json mcp
factory Project .factory/mcp.json mcpServers
factory-user User .factory/mcp.json mcpServers
openclaw Project config/mcporter.json mcpServers
openclaw-user User .mcporter/mcporter.json mcpServers
roo Project .roo/mcp.json mcpServers
auggie-user User .augment/settings.json mcpServers
kimi User .kimi/mcp.json mcpServers
antigravity User .gemini/config/mcp_config.json mcpServers
nanobot User .nanobot/config.json tools.mcpServers

TOML targets

Section titled “TOML targets”
Target Scope Config file Root key
codex Project .codex/config.toml mcp_servers
codex-user User .codex/config.toml mcp_servers

YAML targets

Section titled “YAML targets”
Target Scope Config file Root key
hermes User config.yaml inside the Hermes home mcp_servers

The Hermes home is resolved from HERMES_HOME, falling back to %LOCALAPPDATA%\hermes on Windows and ~/.hermes elsewhere.

Entry shapes

Section titled “Entry shapes”

Agents disagree about how an HTTP MCP server should be described. The writer emits the right shape per target:

Shape Targets
{ "type": "http", "url": ... } Claude, Cursor, Copilot, Roo, Auggie, OpenClaw, Crush, and the default for anything unlisted
{ "httpUrl": ... } Gemini, Qwen
{ "serverUrl": ... } Antigravity
{ "url": ... } Nanobot
{ "url": ..., "transport": "http" } Kimi
{ "type": "remote", "url": ..., "enabled": true } OpenCode
{ "type": "http", "url": ..., "disabled": false } Factory

Safety behaviour

Section titled “Safety behaviour”
  • Merge, never clobber. Other MCP servers and unrelated settings in the file are preserved.
  • Backup before write. The existing file is copied to <file>.bak, rotating to .bak.1, .bak.2 and so on.
  • Case-insensitive matching. An entry you wrote as Unreal-MCP is recognised and updated rather than duplicated.
  • Comments and neighbours survive in TOML and YAML — those formats are edited block by block, not reserialised.
  • Clean removal. Removing the entry leaves the rest of the file intact, and deletes the file only if the entry was all it contained.

Each write reports one of: created, added, updated, unchanged, removed, not_found, file_not_found, deleted_empty_file, or error.