Skip to main content
Glama
Groggy-rollcall812

unreal-engine-mcp

by Groggy-rollcall812
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to unreal-engine-mcp

No user-submitted related servers found.

    Related Servers

    • Unreal Engine MCP Server

      ChiR24
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to control Unreal Engine via Remote Control API for game development automation, including asset management, actor control, level editing, animation, physics, visual effects, and cinematics creation through natural language.
      1
      909 npm
      888
      MIT

    • ue4-mcp-server

      lusilong
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control Unreal Engine editor through natural language, supporting scene setup, asset management, and level editing via the engine's Remote Execution protocol.
      MIT
    • Funplay MCP for Unreal by FunplayAI

      Funplay MCP for Unrealofficial

      FunplayAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly control and interact with the Unreal Editor through natural language, allowing tasks such as spawning actors, building levels, creating materials, and running Python scripts.
      3
      MIT

    • Unreal Engine MCP Bridge

      gingerol
      A
      license
      Not graded
      quality
      D
      maintenance
      A server that enables control of Unreal Engine 5.5+ using natural language commands, allowing users to create Blueprints, manipulate actors, work with nodes, manage project settings, and create UMG widgets through the Model Context Protocol.
      5
      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.1/5.0

    Scored across 72 tools

    Disambiguation4/5

    Most tools target a distinct resource/action and the descriptions clearly separate similar-sounding tools such as ue_status vs ue_editor_status and ue_spawn_actor vs ue_spawn_many. The main ambiguities are ue_import_assets vs ue_import_audio, both of which can handle .wav files, and ue_build_start vs ue_live_compile, but the descriptions resolve these sufficiently.

    Naming Consistency3/5

    Names are consistently snake_case and mostly readable, but word order flips between action_noun tools like ue_open_level/ue_spawn_actor and noun_action or noun_noun tools like ue_project_create/ue_editor_open/ue_build_status/ue_engine_list. The preset_* group adds a second prefix, so the convention is mixed but still fairly predictable.

    Tool Count1/5

    At 72 tools this is far beyond a well-scoped MCP surface; even the heavy band tops out at 25. The server spans multiple subdomains—project management, build/package, assets, presets, Blueprints, materials, rendering, and multiplayer—that should really be split into separate toolsets.

    Completeness3/5

    Coverage is broad across the Unreal Engine lifecycle: project creation, build/package, asset import, actor/level editing, Blueprints, materials, rendering, and PIE are all represented. However, notable gaps remain, such as no dedicated texture/image import even though material creation depends on textures, and no Blueprint graph editing; the latter is explicitly delegated to a C++ workflow or ue_exec_python.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources