Skip to main content
Glama

uefn-ai-toolkit

Build Fortnite maps by describing them to Claude, instead of clicking through the UEFN editor by hand.

It is a Claude Code plugin with three parts: an MCP server that drives a running UEFN editor over Epic's Python remote execution protocol, a set of skills, and a knowledge base of what actually works in Fortnite Creative — which assets are publish-safe, which device settings are scriptable, and which routes are dead ends that look promising.

What you need

  • UEFN installed, with a project created.

  • Claude Code.

  • uv on your PATH (the server is Python).

Related MCP server: Unreal-MCP-Ghost

Install

/plugin marketplace add dylannalex/uefn-ai-toolkit
/plugin install uefn-ai-toolkit@dylannalex-uefn

Then start a new Claude Code session — MCP servers only connect at session start. Open UEFN with your project loaded and ask:

Set up my UEFN project for remote execution.

Claude finds the project on disk and turns on the two settings UEFN needs — Python Scripting, and remote execution for it — both off by default. If UEFN was already open you will be told to restart it; those settings are only read at startup.

Use it

Describe what you want:

Show me everything currently placed in my level

Spawn a chest at the centre of the map and put an assault rifle in it

Move "SpawnPoint_1" up by 200 units

Take a screenshot of the map from above so you can see it

Check whether anything in my level will fail to publish

You don't need to know Unreal or Python. If Claude doesn't know a device or prop's name, it can search your content browser for it.

Keeping notes between sessions

Claude has no memory of the editor between conversations, and a .uefnproject is binary — it can't be diffed or reviewed. Ask for a map project and the plugin scaffolds a plain git repository of markdown alongside your map: the design, what is currently built, what is still pending, and a build log.

Set up a project folder for my new map

That repository is yours and holds no plugin files, so updating the plugin never touches your notes.

Limits worth knowing

  • One editor at a time. Discovery connects to whichever UEFN instance it finds first, so keep one open. Several Claude Code sessions can now run against it — each gets its own command port.

  • Compiling Verse is a manual click. There is no scriptable trigger for Verse > Build Verse Code; everything downstream of a compile is automated, the compile itself isn't.

  • Item content is only scriptable on Item Spawner V3. Item Granter and Class Designer hold theirs behind a platform wall. This is documented rather than worked around, so nobody spends a session rediscovering it.

  • Claude finds placed things by their World Outliner name, so clear, unique labels help.

How it works

See skills/uefn-knowledge/SKILL.md for the knowledge base's routing table, and docs/internals/INDEX.md for the architecture, the wire protocol, and a tool call traced end to end.

Available Tools

11 tools
delete_actorA

Delete the actor with the given editor label (World Outliner name).

Inputs: label (required).

duplicate_actorA

Duplicate the actor with the given label, optionally offsetting the copy's world location and giving it a new editor label.

Inputs: label (required), offset, new_label.

execute_pythonA

Run arbitrary Python code inside the UEFN editor's unreal module.

Use this to explore the editor when the dedicated tools aren't enough: e.g. browsing content with unreal.EditorAssetLibrary, inspecting Fortnite device/actor classes, or calling APIs not wrapped by other tools.

Args: code: Python source to run. For "statement"/"eval" it must be a single expression/statement; for "file" (default) it can be a full multi-line script. mode: One of "file" (default, runs as a script), "statement" (executes and prints one statement), or "eval" (evaluates one expression and returns its value).

Returns: dict with success (bool), result (the eval'd value or error text as a string), and output (anything printed/logged).

Inputs: code (required), mode.

get_actor_transformA

Get the world transform (location/rotation/scale) of the actor with the given label.

Inputs: label (required).

get_editor_statusA

Check connectivity and report basic info about the connected UEFN editor (project file, current level name, engine version, actor/selection counts).

Inputs: no named parameters.

get_selected_actorsA

Return the actors currently selected in the UEFN editor viewport/outliner.

Inputs: no named parameters. Returns: result

list_actorsA

List actors currently placed in the loaded level.

Args: class_name: If set, only return actors whose class name contains this substring (case-insensitive), e.g. "StaticMeshActor". limit: Maximum number of actors to return.

Inputs: limit, class_name. Returns: result

list_content_assetsA

Browse assets in the content browser (props, Blueprints, materials, etc.).

Args: path: Content path to search, e.g. "/Game" or "/Game/Devices". class_names: If set, only return assets whose class name is in this list (e.g. ["StaticMesh", "Blueprint"]). recursive: Whether to search subfolders. limit: Maximum number of assets to return.

Inputs: path, limit, recursive, class_names. Returns: result

save_levelA

Save the current level. If all_dirty is True, saves all dirty levels instead.

Inputs: all_dirty.

set_actor_transformA

Move/rotate/scale the actor with the given label. Any of location, rotation, or scale left unset is left unchanged.

Inputs: label (required), scale, location, rotation.

spawn_actorA

Spawn an actor into the loaded level.

Args: class_path: Object path of the class to spawn. Either a native class (e.g. "/Script/Engine.StaticMeshActor") or a Blueprint class asset path (e.g. "/Game/Devices/BP_MyDevice.BP_MyDevice"). Use list_content_assets or execute_python to discover available Fortnite device/prop Blueprint paths. location: World location {"x", "y", "z"} in cm. Defaults to origin. rotation: World rotation {"pitch", "yaw", "roll"} in degrees. scale: Actor scale {"x", "y", "z"}. Defaults to (1, 1, 1). label: Optional editor display name (shown in the World Outliner).

Inputs: class_path (required), label, scale, location, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but list_actors and get_selected_actors overlap somewhat in returning actor information, and execute_python is a catch-all that could be confused with dedicated tools if misused. Descriptions are clear enough to resolve ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, using predictable verbs like list, get, set, delete, spawn, duplicate, and save. No mixed conventions or vague naming.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range for a UEFN editor server. Each tool covers a distinct editor operation without unnecessary bloat, making the surface manageable and focused.

    Completeness4/5

    The tool set covers core actor lifecycle (spawn, read, update, delete, duplicate), saving, content browsing, and editor status. Missing operations like property editing or asset creation are mitigated by the execute_python escape hatch, which allows arbitrary editor access.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      An MCP server that gives AI agents broad control over Unreal Engine 5.7, enabling actor/asset/level management, Blueprint and material creation, screenshots, automation, and arbitrary editor Python execution.
      35
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes the Unreal Editor for Fortnite to AI assistants via MCP, enabling actor manipulation, device property editing, Verse building, and more through a Python bridge.
      3
      GPL 3.0