Skip to main content
Glama
sam-david

unreal-mcp

by sam-david
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to unreal-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
      164 npm
      872
      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-MCP

      aadeshrao123
      A
      license
      B
      quality
      A
      maintenance
      Controls Unreal Engine 5 editor from AI coding assistants, enabling 280 commands across 13 categories for materials, blueprints, Niagara VFX, and more.
      100
      77 PyPI
      39
      Mozilla Public 2.0

    • 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.
      5,017 npm
      331
      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

    C2.9/5.0

    Scored across 127 tools

    Disambiguation3/5

    Many tools are clearly distinct, but there are clusters that could cause misselection: run_stat_command overlaps with execute_console_command, build_cook_run and package_project both package the project, and reset_niagara_system vs reinit_niagara_system are similar. Descriptions help clarify, but the volume of tools increases ambiguity.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern, but there are notable deviations: sc_ prefix for source control (sc_status vs source control), run_* vs execute_* for similar actions, and inconsistent granularity like build_target vs build_cook_run vs package_project. Still readable, but not a clean consistent scheme.

    Tool Count1/5

    127 tools is extremely excessive for any MCP server, even for a complex engine like Unreal. This volume overwhelms agents and makes tool selection costly. A more focused set of 30-40 tools would likely cover the same workflows.

    Completeness4/5

    The toolset covers an impressive breadth of Unreal workflows: asset management, actor manipulation, blueprints, materials, animation, Niagara, build automation, testing, source control, profiling, and world partition. Minor gaps exist (e.g., explicit level save/manage), but overall the surface is remarkably complete for its scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources