Connecting Your CLI Agent

Your agent needs one thing: an MCP client entry pointing at the editor’s local server. Conductor Terminal can write that for you, or you can do it by hand in about thirty seconds.

The endpoint

Two of the values come from Edit → Editor Preferences → Plugins → Model Context Protocol; the other two are fixed:

	Default	Where it comes from
Host	127.0.0.1	Fixed — the server is local only
Port	8000	Server Port Number in the MCP settings
URL path	/mcp	Server URL Path in the MCP settings
Server name	unreal-mcp	Fixed — the key the entry is written under

Giving http://127.0.0.1:8000/mcp.

On UE 5.7 and earlier

The equivalent was Epic’s ECABridge, on port 3000, with the server name Epic-Coding-Assistant. Conductor Terminal requires 5.8+, but the code path is aware of both.

Auto-configuration

The Unreal MCP Client Config section of the plugin’s settings page — Edit → Editor Preferences → Plugins → Conductor Terminal, or the gear button in any terminal’s top bar — lists every supported agent with Write to Project Config and Write to User Config buttons. Once an entry is present the row shows a green check and a Remove button. See the full list in Supported Agent Targets — 26 targets covering 15 agents, most in both project and user scope.

What it does:

• Merges rather than overwrites. Your other MCP servers and hand-written settings survive.
• Backs up first. The existing file is copied to .bak, rotating to .bak.1, .bak.2 if needed.
• Writes the right shape per agent. Some want url, some httpUrl, some serverUrl, some need a type field or an enabled flag; Codex needs TOML and Hermes needs YAML. The writer knows the difference.
• Can check without touching anything. The green check is a non-mutating probe that reports whether your entry is already present; it never writes.
• Can remove itself cleanly. The remove path strips the entry back out and deletes the file if it was the only thing in it.

Writes and removes do not pop a toast; the check mark appearing or disappearing is the feedback, and the file path and action are logged to the Output Log. Most agents read their MCP config only at startup, so restart the agent after writing.

By hand

Most agents use the same JSON shape. Project scope means a file in your Unreal project directory; user scope means one in your home directory.

Claude Code — .mcp.json (project) or ~/.claude.json (user)

{
  "mcpServers": {
    "unreal-mcp": {
      "type": "http",
      "url": "http://127.0.0.1:8000/mcp"
    }
  }
}

Codex — .codex/config.toml

[mcp_servers.unreal-mcp]
url = "http://127.0.0.1:8000/mcp"

Gemini CLI — .gemini/settings.json (Qwen: .qwen/settings.json)

{
  "mcpServers": {
    "unreal-mcp": {
      "httpUrl": "http://127.0.0.1:8000/mcp"
    }
  }
}

GitHub Copilot — .vscode/mcp.json

{
  "servers": {
    "unreal-mcp": {
      "type": "http",
      "url": "http://127.0.0.1:8000/mcp"
    }
  }
}

OpenCode — opencode.json

{
  "mcp": {
    "unreal-mcp": {
      "type": "remote",
      "url": "http://127.0.0.1:8000/mcp",
      "enabled": true
    }
  }
}

Hermes — config.yaml in the Hermes home

mcp_servers:
  unreal-mcp:
    url: "http://127.0.0.1:8000/mcp"
    enabled: true

Supported Agent Targets has the config path and root key for every recognised agent.

Checking it worked

Start the agent in a terminal pane and ask it what tools it has. You are looking for Epic’s editor toolsets and a toolset called Cndctr Terminal.

If nothing Unreal-related appears:

1. Is the editor running? The MCP server is in-process — no editor, no server.
2. Is Auto Start Server on? Without it the server waits to be started by hand.
3. Did you restart the agent after writing the config? Most read MCP config only at startup.
4. Does the port match? Check Editor Preferences → Plugins → Model Context Protocol.

More in Troubleshooting.