Editor on your machine · Verse in the cloud

Your agent builds the island.

Spawn Fortnite devices and props, place actors, screenshot the viewport, play in creator, compile and verify Verse, edit the scene graph — in the real UEFN editor on your machine. Verse docs and API search come with the same install.

Install uefn-mcp Connect your agent

What you make

Islands · Devices · Props · Scenes

A Fortnite creator sees islands, devices, and play first — not a hosted API.

Islands

Ship a playable Fortnite island — not a chat log about Verse.

Devices

Place the devices that make the loop: buttons, zones, spawners, scoring.

Props

Spawn from the Fortnite / UEFN library and dress the space your players run.

Scenes

Edit transforms, properties, and the scene graph like you are in the viewport.

On your machine

What your agent can do in UEFN.

Spawn, place, screenshot, play, compile, and edit the scene — in the real editor on your machine.

on your machine

Spawn from the Fortnite library

Pull props and actors from the Fortnite / UE library and drop them on the island.

on your machine

Place devices

Drop the devices that make the loop: buttons, zones, spawners, scoring.

on your machine

Viewport screenshots

Capture what the viewport sees so the agent can look before it edits.

on your machine

Play in Creator

Start Play in Creator on your machine and watch the island run.

on your machine

Compile & verify Verse

Compile the Verse on the box that has the editor — pass or fail, not a guess.

on your machine

Scene graph

Edit transforms, properties, and the scene graph like you are in the viewport.

Install

One client. That’s the whole setup.

Install uefn-mcp once with one PowerShell command. Your agent registers one server. It drives the editor on your machine and looks up Verse at HOSTED_MCP_URL. Source: github.com/BizaNator/uefn-mcp.

uefn-mcp

Run one command. Paste to your agent.

One PowerShell command on the Windows box that has UEFN. Source: BizaNator/uefn-mcp. Do not add a second MCP server.

Run the installer

If the client repo is private, the script uses gh or git with your existing GitHub login. The installer writes CONNECT.md and does not dump mcpServers JSON unless you pass -VerbosePaste.
PowerShell
```
irm https://uefnmcp.com/install.ps1 | iex
```
Paste this to your agent

One line. The installer writes the full brief to CONNECT.md (and UEFN-MCP-CONNECT.md on the island when the project is known). That file tells the agent to ASK THE HUMAN for the folder that contains the .uefnproject if needed, verify already-written .mcp.json, and run setup.ps1 so Content\Python is armed. One server only. A portal key is not required.
paste to agent
```
Read %LOCALAPPDATA%\uefn-mcp\CONNECT.md and configure UEFN-MCP according to those instructions.
```

CONNECT.md

The brief on disk tells the agent to verify already-written .mcp.json — do not hand-author. HOSTED_MCP_URL defaults to the hosted grounding endpoint. -VerbosePaste still prints the old mcpServers dump.

uefn-mcp

{
  "mcpServers": {
    "uefn-mcp": {
      "command": "node",
      "args": [
        "<path printed by the installer>\\index.js",
        "--stdio"
      ],
      "env": {
        "HOSTED_MCP_URL": "https://uefnmcp.com/mcp",
        "UEFN_PROJECT_PATH": "<absolute project folder — contains the .uefnproject>",
        "UEFN_PROJECT_ROOT": "<absolute Content/Verse or Plugins/<Plugin>/Content/Verse>"
      }
    }
  }
}

Hosted grounding signs in via browser OAuth on first use. Portal keys (uefn_sk_*) are optional — CI and overrides only. CI / override keys.

Included

Grounded Verse comes with the install

Docs and API search. Keys. Same client — not a second setup.

Grounded Verse docs / API search
Browser OAuth on first use
BYO agent

Connect your agent Open the tools