uefn_listener.py and init_unreal.py copied to Content/Python/
.mcp.json configured for Claude Code
DefaultEngine.ini updated with the recommended CVar overrides
However, I’m hitting an account-level block. The Output Log shows:
LogPython: Python disabled via CVar ‘Engine.Python.IsEnabledByDefault’
And the Beta Access section is completely absent from my Project Settings, so I cannot enable Python Editor Scripting from there either. Manual ini overrides have no effect because UEFN’s validation layer ignores them without account-level access.
As the support team confirmed, this is gated at the account level and requires being allow-listed by Epic.
Could my account be considered for allow-listing for the Python Beta? I’m an active creator in good standing and this workflow (MCP + Claude Code + UEFN Python) is exactly the kind of early-access AI-assisted development use case mentioned in the official UEFN Python documentation.
Epic account: AlpG_431
UEFN version: 5.8
OS: Windows 11
Hi, my Epic account is XMosamyX and I’m a UEFN creator working on a Fortnite map using UEFN 5.7.4. I’m requesting access to the Python Editor Scripting Beta. My use case is editor automation via the UEFN MCP Server ( GitHub - KirChuvakov/uefn-mcp-server: MCP server for controlling UEFN (Unreal Editor for Fortnite) from Claude Code — 22 tools for actors, assets, levels, viewport, and Python execution · GitHub ) integrated with Claude Code. The goal is to automate repetitive editor tasks such as actor placement, asset management, and level setup, so I can focus more time on the creative side of building. All gameplay logic will remain in Verse — Python is purely for speeding up world-building and iteration. I’m not using it for anything gameplay-related, just editor-side automation to reduce manual work. Any help granting access would be greatly appreciated!
I’m requesting access to the Python Editor Scripting Beta.
My specific use case is editor automation via UEFN MCP (in-editor HTTP listener + Cursor / Claude Code) so I can control UEFN from an AI coding agent. The goal is to automate repetitive editor tasks like actor placement, asset management, and scene setup from a JSON stage definition — all gameplay logic remains in Verse.
I’ve already completed the full setup on my end:
Python 3.12 installed
UEFN MCP / uefn_tools deployed under the project Content/Python/
init_unreal.py and an MCP start hook copied to Content/Python/
.mcp.json configured for Cursor
DefaultEngine.ini / CVar overrides attempted as documented
However, I’m hitting an account-level block. Tools > Execute Python Script is missing, the Output Log has no py command bar, and the Beta Access section is completely absent from my Project Settings, so I cannot enable Python Editor Scripting from there either. Manual ini overrides have no effect because UEFN’s validation layer ignores them without account-level access.
As the support team confirmed, this is gated at the account level and requires being allow-listed by Epic.
Could my account be considered for allow-listing for the Python Beta? I’m an active creator in good standing and this workflow (MCP + coding agent + UEFN Python) is exactly the kind of early-access AI-assisted development use case mentioned in the official UEFN Python documentation.
Epic account: aoi_android
Epic organization / team ID: ID: 4ac781cf4a814ada8961c624c655941e
UEFN version: 5.8
OS: Windows 11