
conaman/unreal-mcp-ue4
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
UE4.27-first MCP server for controlling Unreal Editor sessions over Python Remote Execution.
개요
UE4.27.2-focused MCP server for Unreal Engine using Unreal Python Remote Execution unreal-mcp-ue4 started from the core idea and early workflow shape of runreal/unreal-mcp, but it has since been heavily refactored for Unreal Engine 4.27.2 and expanded with many new tools, UE4-specific compatibility layers, documentation, and smoke coverage. At this point, the original inspiration remains, but the public surface and day-to-day behavior are substantially different and UE4-first. This port and the follow-up tool, documentation, and smoke-test work were developed with assistance from OpenAI Codex. This project is still under active development, so bugs, rough edges, and UE4.27-specific limitations may still surface. Published package: unreal-mcp-ue4 Registry name: io.github.conaman/unreal-mcp-ue4 - No custom Unreal C++ plugin from this repository is required. - The server talks to the editor through Unreal's built-in Python Remote Execution path.
README
원문 README의 일부입니다. 원문 보기.
unreal-mcp-ue4
UE4.27.2-focused MCP server for Unreal Engine using Unreal Python Remote Execution
unreal-mcp-ue4 started from the core idea and early workflow shape of runreal/unreal-mcp, but it has since been heavily refactored for Unreal Engine 4.27.2 and expanded with many new tools, UE4-specific compatibility layers, documentation, and smoke coverage. At this point, the original inspiration remains, but the public surface and day-to-day behavior are substantially different and UE4-first.
This port and the follow-up tool, documentation, and smoke-test work were developed with assistance from OpenAI Codex.
This project is still under active development, so bugs, rough edges, and UE4.27-specific limitations may still surface.
Published package:
unreal-mcp-ue4
Registry name:io.github.conaman/unreal-mcp-ue4
Overview
- No custom Unreal C++ plugin from this repository is required.
- The server talks to the editor through Unreal’s built-in Python Remote Execution path.
- The tool surface is organized into granular tools and higher-level tool namespaces.
- UE5-only editor scripting features are not reintroduced; UE4.27-safe operations work normally, while unreliable graph or binding flows are either excluded from the MCP surface or return a clear message instead of silently failing.
Origin
- Original inspiration and starting point: runreal/unreal-mcp
- The current codebase has gone through extensive UE4.27-focused refactoring, architecture changes, and tool expansion.
- In practice, the shared idea is still visible, but the implementation, scope, and supported workflows now reflect a separate UE4-first project.
- Unreal Python API reference: Unreal Engine Python API 4.27
Safety
- This is not an official Epic Games project.
- Any connected MCP client can inspect and modify your open Unreal Editor session.
- Use a disposable test project first, especially when trying asset or world-generation tools.
Requirements
- Unreal Engine
4.27.2 - Node.js
18+ npm- An MCP client such as Codex, Claude Code, Claude Desktop, Cursor, or GitHub Copilot in a supported IDE
MCP Client Setup
This is the most important setup step: your MCP client must know how to launch unreal-mcp-ue4.
1. Install the server
Recommended global install:
설치
npx unreal-mcp-ue4