quangdang46

Uefn Verse MCP — Development skill for Claude Code

Development community

MCP bridge for Unreal Editor for Fortnite that lets Claude Code, Cursor, and other MCP clients drive a live UEFN editor safely.

How to install Uefn Verse MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open quangdang46/uefn-verse-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Uefn Verse MCP does

MCP bridge for Unreal Editor for Fortnite that lets Claude Code, Cursor, and other MCP clients drive a live UEFN editor safely.

Alternatives in Development

MCP Language Server — mcp-language-server gives MCP enabled clients access semantic tools like get definition, references, rename, a 1.5k ★
Nexting — Remote control for Claude Code, Codex, Grok, and Cursor on Mac or PC 1.3k ★
MCP Linker — mcp store manager, add & syncs MCP server configurations across clients like Claude code, Cursor💡mcphub 308 ★

README

uefn-mcp

Python 3.10+ UEFN MCP

A two-process MCP bridge for Unreal Editor for Fortnite that lets Claude Code, Cursor, and other MCP clients drive a live UEFN editor safely.

MCP client (Claude Code / Cursor / custom host)
    │
    │ stdio
    ▼
server/main.py  ── FastMCP host process
    │
    │ HTTP 127.0.0.1:8765-8770
    ▼
Content/Python/uefn_tools/tools/mcp_bridge.py
    │
    │ queue + Slate tick callback
    ▼
UEFN editor main thread -> unreal.* -> 354 registered uefn_tools actions

**Quick setup**

git clone https://github.com/quangdang46/uefn-verse-mcp.git
cd uefn-verse-mcp
python -m pip install -r requirements.txt
python deploy.py --project "MyIsland"

There is no packaged one-line installer yet. The supported path today is source checkout plus local deploy into a UEFN project.

TL;DR

The Problem

UEFN's Python layer is powerful, but it is a bad place to host a modern MCP server directly:

unreal.* calls must run on the editor main thread.
Blocking Python code can freeze the editor.
The MCP SDK belongs in a normal host Python runtime, not inside the editor sandbox.

The Solution

`uefn-mcp` splits the system in two:

server/main.py runs externally as a FastMCP stdio server.
Content/Python/uefn_tools/tools/mcp_bridge.py runs inside UEFN as a local HTTP listener.
Commands are queued and drained on Slate ticks so editor API calls stay on the main thread.

Why Use `uefn-mcp`?

Capability	What it gives you
31 direct MCP tools	A curated surface for actors, assets, project info, viewport, logs, and status
354 `run_tool` entries	An escape hatch into the full `uefn_tools` registry without re-wrapping every action as fir