Skip to main content
Glama
JosephOIbrahim

UnrealEngine Bridge

by JosephOIbrahim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to UnrealEngine Bridge

No user-submitted related servers found.

    Related Servers

    • qfoldit-unigine-toolbelt

      qfoldit
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate UNIGINE 2 editor workflows through 25 composite tools (scene, materials, procedural, stamps, codegen, assets, and build console) via an external MCP bridge that runs alongside UNIGINE's official MCPBridge Plugin.
      6
      -

    • 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

    • Hayba

      zajalist
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server enabling AI agents to author Unreal Engine 5 scenes directly, with tools for spawning actors, building PCG graphs, validating physics, generating terrain, and more through a single MCP connection.
      13
      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
    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.8/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: mood tools are separate from viewport, X3D, spatial, and general utilities. No two tools appear to do the same thing, and descriptions clarify boundaries.

    Naming Consistency5/5

    All tools use the 'ue_' prefix followed by a consistent verb_noun pattern (e.g., apply_mood_preset, get_world_info, snap_to_ground). Minor deviations like 'ue_status' are still clear and follow the convention.

    Tool Count4/5

    With 25 tools, the server covers a broad range of Unreal Engine operations without being excessive. The count is appropriate for comprehensive bridge functionality, though it could be slightly trimmed.

    Completeness4/5

    The tool surface is extensive, covering mood, time, sky, viewport, X3D, spatial queries, and actor manipulation. The ue_execute_python tool fills many gaps. Minor omissions like direct material editing are acceptable given the scope.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources