Skip to main content
Glama
NAJEMWEHBE

unreal-ai-connection

by NAJEMWEHBE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to unreal-ai-connection

No user-submitted related servers found.

    Related Servers

    • unreal-engine-mcp

      harn3ss
      A
      license
      B
      quality
      C
      maintenance
      An 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

    • Monolith

      tumourlove
      A
      license
      Not graded
      quality
      A
      maintenance
      Unreal 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.
      300
      MIT

    • UnrealMCP

      AvatarGanymede
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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.
      1
      MIT

    • unreal-mcp-additional-tools

      nodormu
      A
      license
      C
      quality
      B
      maintenance
      An MCP server that complements Epic's official Unreal Engine MCP server with 78 additional tools across 14 subsystems for build/cook/package, cinematics, Niagara, automation testing, source control, profiling, World Partition, and project maintenance, using Unreal's built-in Python and Remote Control plugins.
      78
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 105 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessResponsive

    Resources