# Unreal Engine MCP server

> Automate the Unreal Editor (UE 5.0-5.8): levels, Blueprints, UI, materials, VFX and more through a native C++ plugin.

- Listing: https://mcp.tc/i/unreal-engine
- Connect: this is a local (stdio) server; install it on your machine (see Install). The listing link is a page, not an MCP endpoint.
- Type: local (stdio)
- Auth: API key
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: ChiR24
- Repository: <https://github.com/ChiR24/Unreal_mcp>
- Package: npm `unreal-engine-mcp-server`

## About

Connects an MCP client to a running Unreal Editor through the MCP Automation Bridge C++ plugin. A single tool, unreal, exposes nearly 400 capabilities covering levels and actors, Blueprints, UMG widgets, materials, Niagara effects, landscapes, gameplay systems, cinematics, audio, Play-In-Editor testing and builds.

It runs locally. The npm package unreal-engine-mcp-server talks over stdio to the plugin's WebSocket, or a client can connect directly to the plugin's HTTP endpoint at 127.0.0.1:3000/mcp. Both routes require the project's capability token, which the plugin generates in the project's Saved/MCP folder. Needs Unreal Engine 5.0 to 5.8 and Node.js 20.19 or later for the stdio route.

## What it can do

- Spawn, place and attach actors; load, stream and save levels
- Create Blueprints, variables, components and event graphs
- Lay out UMG widgets with a preview image
- Build material graphs, landscapes, foliage, Niagara and PCG
- Set up characters, animation, AI and Enhanced Input
- Run Play-In-Editor, take screenshots, read logs and profile
- Run Python and package builds

## Example prompts

- "Spawn 50 trees in a ring around the origin in the current level"
- "Create a Blueprint with a health variable and a damage event"
- "Build a simple main menu widget and show me a preview"
- "Run Play-In-Editor and take a screenshot of the scene"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport stdio unreal-engine --env "UE_PROJECT_PATH=<YOUR_UE_PROJECT_PATH>" --env "MCP_AUTOMATION_CAPABILITY_TOKEN=<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>" -- npx -y unreal-engine-mcp-server
```

2. Start Claude Code and type `/mcp`. **unreal-engine** should show as connected.

Add `--scope user` to make it available in every project. Replace the placeholders with your own values.

### Claude Desktop

1. Open **Settings → Developer → Edit Config**. It opens `claude_desktop_config.json`. Add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "unreal-engine": {
      "command": "npx",
      "args": [
        "-y",
        "unreal-engine-mcp-server"
      ],
      "env": {
        "UE_PROJECT_PATH": "<YOUR_UE_PROJECT_PATH>",
        "MCP_AUTOMATION_CAPABILITY_TOKEN": "<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>"
      }
    }
  }
}
```

2. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in `~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on Windows.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=unreal-engine&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsInVucmVhbC1lbmdpbmUtbWNwLXNlcnZlciJdLCJlbnYiOnsiVUVfUFJPSkVDVF9QQVRIIjoiPFlPVVJfVUVfUFJPSkVDVF9QQVRIPiIsIk1DUF9BVVRPTUFUSU9OX0NBUEFCSUxJVFlfVE9LRU4iOiI8WU9VUl9NQ1BfQVVUT01BVElPTl9DQVBBQklMSVRZX1RPS0VOPiJ9fQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "unreal-engine": {
      "command": "npx",
      "args": [
        "-y",
        "unreal-engine-mcp-server"
      ],
      "env": {
        "UE_PROJECT_PATH": "<YOUR_UE_PROJECT_PATH>",
        "MCP_AUTOMATION_CAPABILITY_TOKEN": "<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>"
      }
    }
  }
}
```

Needs Node.js on your computer. Replace the placeholders with your own values.

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the secret the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "unreal-engine": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "unreal-engine-mcp-server"
      ],
      "env": {
        "UE_PROJECT_PATH": "<YOUR_UE_PROJECT_PATH>",
        "MCP_AUTOMATION_CAPABILITY_TOKEN": "${input:mcp-automation-capability-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-automation-capability-token",
      "description": "MCP_AUTOMATION_CAPABILITY_TOKEN",
      "password": true
    }
  ]
}
```

Needs Node.js on your computer.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "unreal-engine": {
      "command": "npx",
      "args": [
        "-y",
        "unreal-engine-mcp-server"
      ],
      "env": {
        "UE_PROJECT_PATH": "<YOUR_UE_PROJECT_PATH>",
        "MCP_AUTOMATION_CAPABILITY_TOKEN": "<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

### Codex

```bash
codex mcp add unreal-engine --env "UE_PROJECT_PATH=<YOUR_UE_PROJECT_PATH>" --env "MCP_AUTOMATION_CAPABILITY_TOKEN=<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>" -- npx -y unreal-engine-mcp-server
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.unreal-engine]
command = "npx"
args = ["-y", "unreal-engine-mcp-server"]
env = { UE_PROJECT_PATH = "<YOUR_UE_PROJECT_PATH>", MCP_AUTOMATION_CAPABILITY_TOKEN = "<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>" }
```

Needs Node.js on your computer. Replace the placeholders with your own values.

### Gemini CLI

```bash
gemini mcp add -e "UE_PROJECT_PATH=<YOUR_UE_PROJECT_PATH>" -e "MCP_AUTOMATION_CAPABILITY_TOKEN=<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>" unreal-engine npx -- -y unreal-engine-mcp-server
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients that start local servers accept this shape:

```json
{
  "mcpServers": {
    "unreal-engine": {
      "command": "npx",
      "args": [
        "-y",
        "unreal-engine-mcp-server"
      ],
      "env": {
        "UE_PROJECT_PATH": "<YOUR_UE_PROJECT_PATH>",
        "MCP_AUTOMATION_CAPABILITY_TOKEN": "<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings, with the same `command`, `args` and `env` fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

## Recent changes

- 2026-10-27 17:41 UTC: New version 0.6.0 (was 0.5.30), read from npm. Source: automatic check.
- 2026-10-11 04:27 UTC: Tracking started: version 0.5.30. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/unreal-engine#history (Atom feed: https://mcp.tc/i/unreal-engine/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.6.0
- Last checked: 2026-10-11
- Listed: 2026-10-11
- Updated: 2026-10-11

---
Source: https://mcp.tc/i/unreal-engine (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
