Skip to main content
Glama
JulianIrigoyen

ascent-unreal-mcp

by JulianIrigoyen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ascent-unreal-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • Unreal Engine MCP Server

      andrewkorot
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control and automate Unreal Engine through a native C++ Automation Bridge plugin. It supports a comprehensive range of tasks including asset management, actor manipulation, editor control, and blueprint graph editing.
      1,053 npm
      1
      MIT

    • unreal-mcp

      sam-david
      F
      license
      C
      quality
      D
      maintenance
      Enables natural language interaction with Unreal Engine, providing 127 tools across 16 subsystems for tasks like actor manipulation, asset management, blueprint creation, and more, using built-in Python and Remote Control plugins.
      100
      6
      -

    • unreal-ai-connection

      NAJEMWEHBE
      A
      license
      B
      quality
      B
      maintenance
      Drive 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.
      100
      9
      MIT

    • UE-MCP

      db-lyon
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI assistants deep read/write access to the Unreal Editor through 21 category tools covering 525+ actions, plus a YAML flow engine for multi-step workflows.
      793 npm
      345
      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

    A3.6/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource and action: actor probes/setters, asset probes/setters, imports, screenshots, and UDS/weather tools. The only likely confusion is between the generic unreal_probe_actor and the UDS-specialized uds_inspect_level for sky/weather actors, and between unreal_screenshot and weather_capture_phase_stills; detailed descriptions minimize misselection.

    Naming Consistency3/5

    The set is consistently snake_case and mostly uses an action-first pattern with an unreal_ prefix. However prefixes vary (uds_, ascent_, weather_, anim_), 'unreal_asset_probe' reverses the verb-noun order of 'unreal_probe_actor', and 'unreal_screenshot'/'ascent_unreal_status' are noun-like rather than verb-first, making the pattern readable but not uniform.

    Tool Count3/5

    20 tools is at the high end for an MCP server and feels heavy, but the surface spans several subdomains: asset registry, actor editing, import pipeline, UDS/weather, screenshots, and animation audit. The count is defensible but borderline.

    Completeness4/5

    The set covers the main asset and actor lifecycles: discover, probe, set, spawn/import, create material instances, duplicate maps, snapshot levels, and verify mutations. Gaps like generic asset/actor deletion and new-map creation exist, but tag-based cleanup and the script/verify escape hatches make them workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources