Skip to main content
Glama
CrispyW0nton

Unreal-MCP-Ghost

by CrispyW0nton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Unreal-MCP-Ghost

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

    • unreal-mcp-ue4

      conaman
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control and query Unreal Engine 4.27.2 editor through MCP, supporting asset creation, level editing, and project inspection via Python remote execution.
      411 npm
      25
      MIT

    • soft-ue-cli

      softdaddy-o
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for controlling Unreal Engine 5 from AI agents, providing 120+ commands for spawning actors, editing Blueprints, managing assets, and more via CLI or MCP.
      215
      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.
      3
      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.8/5.0

    Scored across 729 tools

    Disambiguation1/5

    Massive redundancy makes tool selection nearly impossible. Identical or near-identical operations exist under multiple names: add_branch_node vs add_blueprint_branch_node vs bp_add_node, compile_blueprint vs bp_compile vs compile_blueprint_and_report, exec_python vs ue_exec_safe vs ue_exec_transact, and net_set_function_rpc vs net_create_rpc_event. An agent cannot reliably distinguish dozens of overlapping groups.

    Naming Consistency2/5

    Individual sub-families are consistent (spatial_*, gen_*, net_*), but the Blueprint tooling alone alternates between add_blueprint_*_node, add_*_node, and bp_* prefixes for the same operations. Verbs like create/add/build/insert are used interchangeably, and parallel APIs (create_material vs mat_create_material vs material_create_master) break any single predictable pattern.

    Tool Count1/5

    729 tools is an extreme mismatch for any conceivable server scope, far beyond the 50+ threshold for a 1. Even a comprehensive Unreal Engine integration would be better served by 30-50 consolidated tools; this count makes tool discovery and selection itself the primary obstacle.

    Completeness4/5

    The surface covers nearly every Unreal domain: Blueprint graphs, AI, animation, materials, VFX, UI, networking, GAS, audio, world building, geometry, and generative pipelines, each with create/read/update plus validation and repair tools. Minor gaps exist (e.g., asset deletion for several asset types), but exec_python and generic bridge tools provide escape hatches.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources