unreal-ai-connection
Related Servers
Alternatives to unreal-ai-connection
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI clients to control Unreal Engine 5 editor for automated Blueprint authoring, level inspection, actor spawning, and other editor workflows via a local Python MCP server and UE plugin.5003AGPL 3.0
- AlicenseBqualityCmaintenanceAn 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.35MIT
- AlicenseNot gradedqualityAmaintenanceUnreal Engine 5.7 editor plugin that gives AI assistants full read/write access to Blueprints, Materials, Animation, Niagara, Config, and more via MCP. 119 actions across 9 domains, pure C++, embedded Streamable HTTP server.325MIT
- AlicenseNot gradedqualityCmaintenanceDrives Unreal Engine 5 from any AI assistant by exposing the open editor as MCP tools over Unreal's built-in Remote Control API, so users can spawn, list, move, and delete actors, search assets, and read or write properties through natural language. No custom plugin or in-engine code is required, and it includes a raw function-call tool plus batch execution for arbitrary BlueprintCallable functions.MIT
- AlicenseBqualityAmaintenanceAn MCP server that lets an AI agent drive Unreal Engine 5: create projects, import assets, build levels and Blueprints, configure replication, compile C++, run Play In Editor and package the game.10096 PyPI4MIT
- AlicenseNot gradedqualityAmaintenanceA native MCP server for Unreal Engine 5.7 that lets AI assistants inspect and control an open Unreal Editor through a single 'unreal' tool, supporting Python/console command execution and async tasks.3MIT
TDQS
Scored across 105 tools
Most tools are clearly separated by resource type (inspect_sound_*, inspect_blueprint, etc.), but several execution families overlap: execute_unreal_python / exec_python_persistent / run_python_file / apply_python_to_selection all run Python, and get_viewport_screenshot / screenshot_actor / take_high_res_screenshot / render_camera_to_png all capture images. Detailed descriptions mitigate the ambiguity, but an agent could easily misselect without reading carefully.
The server mostly follows a clean verb_noun snake_case pattern, with excellent family consistency in inspect_*, bulk_*, set_*, and poll_* tools. Minor deviations exist: pie_control and unsubscribe are single verbs, sequencer_add_transform_keyframe breaks the verb-first ordering, and some verbs alternate between get_ and inspect_ for similar read operations.
105 tools is an extreme surface, far beyond the 16-25 'heavy' range and even the 50+ extreme-mismatch bar. While Unreal Editor is a broad domain, this many tools creates severe context-window and selection burden, and many tools could be condensed into parameterized families or folded into the Python escape hatch.
The toolset is exceptionally broad: asset inspection/mutation, actor control, level sequencing, audio, niagara, materials, Python execution, console variables, events, marketplace import, and even mod packaging. Missing creation/lifecycle tools for many asset types and the lack of Blueprint graph editing are genuine gaps, but they are workable around via execute_unreal_python and the extensive bulk/batch helpers.