Featured Project

unreal-mcp-ue4

A UE4.27.2-focused MCP server built around Unreal Python Remote Execution, designed for practical editor workflows in projects that still operate inside UE4-era production constraints.

Repository Back to projects

Why it exists

UE4.27 still matters in real environments

Many AI-assisted Unreal examples assume newer editor capabilities or UE5-specific expectations. This project starts from a simpler question: what does a useful MCP-shaped workflow look like when the team still lives on UE4.27.2?

Core idea

Respect the engine version you actually ship with

The interesting constraint is not just “make Unreal work with MCP.” It is making that integration honest about engine boundaries, Python support, and the kinds of editor actions that are reliable enough to expose.

What it does

Editor and content workflows

The server focuses on useful operations that map well to an open Unreal Editor session instead of chasing the largest possible surface area.

Inspection Reads project, map, asset, and actor information from the open editor.
Tool surface Exposes editor and content workflows in a form that is comfortable for MCP-driven tools.
Coverage Supports actors, assets, widgets, Blueprints, and inspection-oriented flows.

Why it is interesting

Constraints shape the design

What makes this project representative is the way the implementation is bounded: it stays close to stock UE4.27 Python behavior and treats compatibility as part of the product design, not an afterthought.

Direction

The project also sets the tone for the site.

This is the kind of work I want the homepage to point toward: projects that are technically concrete, shaped by real compatibility constraints, and documented well enough that someone else can understand the trade-offs without digging through the whole repository first.