Use with any MCP client

Already using Claude Code? Skip this page — the plugin auto-configures everything (.mcp.json, tool permissions, the cu wrapper) when the editor loads. This page is for driving ClaudeUnreal from any other MCP client: Cursor, Cline, Windsurf, Antigravity, or anything that speaks MCP.

Nothing about the plugin is Claude-Code-specific underneath. The UE editor runs a TCP bridge at 127.0.0.1:55557, and both a standard stdio MCP server and the cu CLI talk the same JSON to it. Any agent can drive it.

On UE 5.8: mount onto Unreal's own MCP server

If your IDE already speaks to Unreal Engine 5.8’s built-in MCP server (Epic’s ModelContextProtocol plugin), you can skip running a second server: set Project Settings → Plugins → Claude Unreal → MCP Mode to Mount on official and ClaudeUnreal registers its tools onto that server via the Toolset Registry. It currently mounts a few hot-path tools — for the full surface, keep the default Standalone mode and follow the steps below. See Mount on UE 5.8’s official MCP server for the setup walkthrough.

Fastest path: let your agent do it

Copy this to your agent

Paste the entire block below into your IDE’s agent — or just give it this page’s URL. It contains everything the agent needs to configure your IDE itself, adapting each step to your IDE’s MCP config format.

You are configuring the ClaudeUnreal Unreal Engine plugin to work with the
MCP client of the IDE you are running in. Do the following, adapting each
step to THIS IDE's configuration format.

Architecture: the plugin runs a TCP bridge at 127.0.0.1:55557 inside the
live UE editor. Both an MCP server and a `cu` CLI speak the same JSON to it,
so any agent can drive it. The UE editor must be running for anything to work.

1. Locate, in the user's UE project:
   - the MCP dir:  <Project>/Plugins/ClaudeUnreal/Resources/MCP
   - the `uv` binary (https://docs.astral.sh/uv/), e.g. ~/.local/bin/uv,
     /opt/homebrew/bin/uv, or /usr/local/bin/uv.

2. Register a stdio MCP server in THIS IDE's MCP config. The canonical
   Claude Code entry is below — translate it into this IDE's format:
     {
       "command": "<abs path to uv>",
       "args": ["--directory", "<MCP dir>", "run", "claude_unreal_server.py"]
     }

3. For the long tail of tools not exposed over MCP, use the `cu` CLI. There
   is no `.claude/cu` wrapper outside Claude Code, so invoke it directly:
     uv run --directory "<MCP dir>" cli/cu.py catalog      # list every tool
     uv run --directory "<MCP dir>" cli/cu.py help <tool>  # show one tool
     uv run --directory "<MCP dir>" cli/cu.py exec <tool> --key value ...
   Read `cu catalog` output to learn the available tools. Optionally create a
   shell alias/wrapper named `cu` for that `uv run ...` command.

4. skills and slash-command recipes are Claude-Code-only and are NOT present
   here. If this IDE has a rules/workflow system, re-author the flows you
   need in its format; otherwise just call `cu` directly.

5. Verify: run `uv run --directory "<MCP dir>" cli/cu.py ping` (or call the
   MCP `ping` tool). It should reach the bridge. If it fails, confirm the UE
   editor is open, uv is installed, and port 55557 is free.

Doing it by hand

The brief above is self-contained; the essentials, for a human:

• Register a stdio MCP server in your IDE’s config — equivalent to the entry the plugin writes for Claude Code:

  {
    "command": "/abs/path/to/uv",
    "args": ["--directory", "<Project>/Plugins/ClaudeUnreal/Resources/MCP", "run", "claude_unreal_server.py"]
  }

• Long-tail tools go through cu. Outside Claude Code there is no .claude/cu wrapper, so call it directly: uv run --directory "<MCP dir>" cli/cu.py catalog | help <tool> | exec <tool> --key value.

• skills & slash-command recipes don’t carry over (Claude-Code-only) — re-author them in your IDE’s rules/workflow system, or just call cu.

• Prereqs: uv installed, the UE editor open, port 55557 free. Verify with … cli/cu.py ping; if it fails, the usual cause is the editor not being fully loaded yet.

See Architecture & tools for how the pieces fit together.