Ue MCP logo

Ue MCP

Controls Unreal Editor projects through MCP, covering authoring, inspection, builds, workflows, and extensible tool categories.

Install Ue MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ue-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ue-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

ue-mcp MCP server connects AI assistants to the Unreal Editor through a TypeScript/Node.js process and an in-editor C++ bridge plugin. It exposes broad Unreal development actions for levels, Blueprints, materials, assets, animation, VFX, gameplay systems, project operations, and more, with filesystem access for project configuration and source inspection when the editor is closed. Use its search, describe, and call gateway to discover and invoke actions, or define reusable YAML flows for multi-step tasks with retries, conditions, shell commands, and rollback. Reach for ue-mcp when an agent needs to inspect or modify a real Unreal project rather than only answer questions about it.

Use cases

  • Inspect Unreal project settings, headers, and assets before opening the editor
  • Author and compile Blueprint graphs through an AI assistant
  • Create and modify levels, materials, VFX, lighting, and gameplay systems
  • Run repeatable build, validation, and editor workflows from YAML flows

Key features

  • Unreal Editor access through a C++ bridge
  • Action discovery with search, schemas, and dynamic calls
  • YAML flows with retries, conditions, shell steps, and rollback
  • Coverage across major Unreal authoring and gameplay systems
  • npm plugin extensions and Unreal 5.8 Epic tool routing

Tools2

What Ue MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

11/11 checks healthy over the last 23d

What it can do

From the 2 tools this server returned when we ran it.

Runs commands · 1Makes network requests · 1Read-only tools · 1
Network at startup4 connections
Files written at startup1
Install scriptsprepare
npm provenanceSigned build
Package age219 days
Maintainers1

Observed 2026-10-25 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · ue-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars480Stargazers on the source repository.
npm downloads15kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed2Callable tools this server registers over MCP.

How Ue MCP works

What ue-mcp does

ue-mcp gives MCP-compatible AI assistants read and write access to Unreal Engine projects through an in-editor bridge. Its action surface spans level editing, actors, Blueprints, materials, assets, animation, Niagara, landscape, foliage, PCG, audio, UI, physics, navigation, AI, StateTree, Gameplay Ability System, networking, Sequencer, builds, logs, project settings, and editor lifecycle operations.

Project-oriented operations can also inspect INI configuration, C++ headers, and asset listings directly from the filesystem. Those reads can be used while the editor is closed. On Unreal Engine 5.8 and later, the server can also surface tools from Epic's native AI Toolset Registry as epic_* actions in related categories.

How it works

The MCP process runs in TypeScript on Node.js and communicates with a C++ bridge plugin inside Unreal Editor over WebSocket and JSON-RPC. The bridge calls Unreal editor APIs, while the MCP process handles direct filesystem reads and action routing.

The top-level gateway helps an agent discover the large action catalog without loading every schema at once:

  • search finds actions by keyword or intent.
  • list_categories returns available categories.
  • describe shows category pages or one action's parameters.
  • call invokes a selected category action with an argument object.

The flow system runs named sequences from ue-mcp.yml. Flows can contain any MCP action, nested flows, or shell commands, and support conditions, retries, retry delays, step references, ignored failures, and optional rollback. A flow can first be inspected with plan, while list reports flows merged from project configuration, user-global configuration, and loaded plugins.

Setup and configuration

Run the interactive initializer from the Unreal project directory:

Terminal
npx ue-mcp init

It detects a .uproject, lets you select categories, deploys the bridge plugin, enables required Unreal plugins, and configures supported MCP clients. Restart the editor once after initialization so the bridge loads. Later updates use:

Terminal
npx ue-mcp update

For connection diagnostics, run npx ue-mcp doctor. Manual client configurations can launch npx -y --min-release-age=0 ue-mcp@latest with the path to a .uproject as an argument.

Plugins can extend the server through npm packages, adding actions to existing categories or creating new categories backed by C++ handlers. Agent skills included with the package cover editor workflow, Blueprint authoring, Niagara, animation, native C++, and routing to Epic toolsets where supported.

Tools and capabilities

Supported areas include:

  • Level actors, lights, volumes, splines, water, and bounds
  • Blueprint graphs, nodes, pins, compilation, components, and CDO properties
  • Materials, instances, expression graphs, and parameters
  • Asset creation, import, inspection, collision, navigation, and bounds
  • Animation, Control Rig, retargeting, montages, and pose analysis
  • Niagara, PCG, landscape, foliage, audio, UMG, physics, AI, and StateTree
  • Project status, configuration, source inspection, builds, logs, PIE, Sequencer, and editor controls
  • YAML flows, npm extensions, the built-in procedural demo, and feedback actions

Limitations and notes

Write access to an Unreal project carries operational risk. Configurable write guards can block or require confirmation before mutating methods reach the editor, and source-control guards can gate writes to checked-in assets. The bridge must be compiled and loaded in the project, and the editor must be open for editor API actions. If the editor is connected to a different project than the configured .uproject, operations may target the wrong project context or fail.

Flow execution stops when a step reports an unexpected failure. An ignore_failure step records its error and continues, while rollback can replay collected inverse tasks in reverse order. The built-in Neon Shrine demonstration creates a procedural scene through a 19-step sequence and provides cleanup support.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ue MCP

ue-mcp is an MCP server that connects AI assistants to Unreal Editor projects through a Node.js process and C++ bridge. Its main tools search and describe available actions, call Unreal operations, inspect project data, and run named YAML flows for tasks such as authoring levels, Blueprints, materials, VFX, assets, and builds.

Run `npx ue-mcp init` from the Unreal project directory. The initializer detects the `.uproject`, deploys the bridge plugin, enables required Unreal plugins, and configures supported clients. Restart the editor after setup, then use `npx ue-mcp doctor` if the connection fails.

Yes, ue-mcp can configure Cursor during its interactive setup. The server uses a standard MCP launch configuration with `npx`, the `ue-mcp@latest` package, and the path to the target `.uproject`.

Define a named flow in `ue-mcp.yml`, inspect it with `flow(action="plan", flowName="...")`, and execute it with `flow(action="run", flowName="...")`. Flows can combine MCP actions, nested flows, shell commands, conditions, retries, runtime parameters, and optional rollback.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUe MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ue-mcp?style=directory)](https://allmcps.com/mcp/ue-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ue-mcp"><img src="https://allmcps.com/api/badge/ue-mcp?style=directory" alt="Ue MCP on AllMCPs" /></a>