Skip to content

Quick Setup

Direktor connects through a small npm bridge, unreal-direktor-mcp, that runs with npx. It works on every MCP client, including the ones that don’t speak Streamable HTTP directly, and it caches the tool list so your AI session survives editor restarts.

  1. Make sure the Direktor plugin is enabled and the editor is running (see Installation). The setup panel under Window → Direktor shows the server listening on port 13579.

  2. Add the config below to your AI client.

  3. Restart or reload your client so it picks up the new MCP server, then ask it to do something in the editor — for example, “spawn a cube at the origin.”

Every client uses the same bridge command. Pick your client below.

Open Settings → Developer → Edit Config to find claude_desktop_config.json, then add:

{
"mcpServers": {
"direktor": {
"command": "npx",
"args": ["-y", "unreal-direktor-mcp"]
}
}
}

Restart Claude Desktop. Direktor’s tools appear under the MCP tools menu.

If your client supports a direct Streamable HTTP MCP endpoint, you can skip the npm package entirely and point it at the loopback URL:

http://127.0.0.1:13579/mcp

The bridge is still the recommended path because it works on every client and keeps a cached tool list so the client can start and list tools even before the editor is up.

The bridge reads a few optional environment variables if you’ve changed Direktor’s defaults:

Env varDefaultPurpose
DIREKTOR_URLhttp://127.0.0.1:13579/mcpFull MCP endpoint of the running editor
DIREKTOR_PORT13579Port only, used when DIREKTOR_URL is unset
DIREKTOR_CACHEnext to the scriptRelocate the tool-list cache if the install dir is read-only