Skip to main content
Glama
koshimazaki

UE Audio MCP

by koshimazaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to UE Audio MCP

No user-submitted related servers found.

    Related Servers

    • Monolith

      tumourlove
      A
      license
      Not graded
      quality
      A
      maintenance
      Unreal Engine 5.7 editor plugin that gives AI assistants full read/write access to Blueprints, Materials, Animation, Niagara, Config, and more via MCP. 119 actions across 9 domains, pure C++, embedded Streamable HTTP server.
      325
      MIT

    • UnrealEngine Bridge

      JosephOIbrahim
      A
      license
      A
      quality
      C
      maintenance
      A comprehensive bridge connecting AI agents to Unreal Engine 5.7 through 39 MCP tools for scene manipulation, asset management, and blueprint control. It enables real-time perception and editor automation using the Remote Control API and file-based protocols.
      25
      2
      MIT

    • bptoolkit-mcp

      caizhirong486-lab
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read, review, and generate Unreal Engine 5.4+ blueprints, including dumping graph JSON, reviewing Wwise logic chains, and building blueprints from JSON specs.
      2
      MIT

    • Hayba

      zajalist
      A
      license
      Not graded
      quality
      A
      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
    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 81 tools

    Disambiguation3/5

    Prefixes (wwise_, ms_, bp_) separate major domains, but there are overlapping high-level and low-level paths: ms_build_graph wraps ms_validate_graph/ms_graph_to_commands/ms_save_asset, bp_wire_audio_param wraps bp_add_bp_node/bp_connect_bp_pins, and wwise_create_object overlaps with wwise_create_event. Descriptions usually clarify intent, but several boundaries remain easy to confuse.

    Naming Consistency3/5

    Tool names use snake_case throughout, but the prefixing convention is mixed: some domains are consistently prefixed (wwise_, ms_, bp_), while many editor/system tools are generic and unprefixed (build_audio_system, place_anim_notify, find_actor, spawn_audio_emitter). This is readable but not a predictable single pattern.

    Tool Count1/5

    With 81 tools, the surface is far beyond a well-scoped set and well past the 50+ threshold for extreme mismatch. Even accounting for Wwise, MetaSounds, Blueprint, and UE5 editor domains, the count creates heavy selection and context burden.

    Completeness4/5

    The surface is very broad, covering Wwise authoring, MetaSounds graph construction, Blueprint wiring/scanning, UE5 actor/editor operations, templates, import/export, sync, and auditing. Explicit delete/move/rename operations and some asset lifecycle operations are missing, though WAAPI escape hatches and high-level builders cover most practical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources