A
licenseB
qualityC
maintenanceAn 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
unreal-mcp-additional-tools
by nodormu
Related Servers
Alternatives to unreal-mcp-additional-tools
No user-submitted related servers found.
Related Servers
- 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.2MIT
- 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.10065 PyPI4MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for controlling Unreal Engine 5 with 199 tools across 37 categories, including Blueprint analysis, animation pipeline, and async tasks.1-
- AlicenseBqualityBmaintenanceDrive the Unreal Engine 5.7 editor from any MCP client over a local TCP socket - 105 editor-automation tools (72 native C++ handlers + 33 bridge-side): actors, levels, materials, Blueprints, sequencer, rendering, asset import, editor Python. Native C++ plugin + thin Python bridge, ~50ms round-trips. MIT.1009MIT
- 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
TDQS
C2.6/5.0
Scored across 78 tools
Disambiguation2/5
Many tools overlap in purpose: execute_console_command and run_stat_command both run console/stat commands, and run_automation_test, run_all_automation_tests, run_automation_tests_by_category have unclear boundaries. Build-related tools also overlap significantly (build_cook_run, cook_content, package_project).
Naming Consistency2/5
Naming is inconsistent: source control tools use a 'sc_' prefix while similar workflows use full verb_noun patterns; run_stat_command vs execute_console_command; get_test_results vs list_automation_tests; and tool verbs mix 'get', 'list', 'run', 'execute', 'set' without a clear convention.
Tool Count2/5
78 tools is far beyond a well-scoped server and spans multiple unrelated domains (source control, build, automation, Niagara, sequences, remote control). The high count makes the tool surface difficult to navigate and likely contains redundant operations.
Completeness3/5
The broad toolkit covers many Unreal Editor workflows, including build, test, source control, Niagara, sequences, and remote control. However, each domain has notable gaps—e.g., no generic actor quer or asset creation/deletion—and some areas feel opportunistic rather than systematic.
Maintenance
ActivitySlowing
ResponsivenessNo issues