Skip to main content
Glama
linnn-nb

wwise-mcp

by linnn-nb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to wwise-mcp

No user-submitted related servers found.

    Related Servers

    • dcc-mcp-wwise

      dcc-mcp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables interaction with Audiokinetic Wwise Authoring through WAAPI, allowing project inspection, sound and music imports, event management, and audible previews.
      MIT

    • FmodStudioMCP

      xDarkzx
      A
      license
      B
      quality
      A
      maintenance
      MCP server that connects AI assistants to FMOD Studio via its scripting terminal, enabling live game-audio authoring such as creating events, importing sounds, routing mixers, and building banks through natural language.
      92
      1
      Apache 2.0

    • unreal-mcp

      sam-david
      F
      license
      C
      quality
      D
      maintenance
      Enables natural language interaction with Unreal Engine, providing 127 tools across 16 subsystems for tasks like actor manipulation, asset management, blueprint creation, and more, using built-in Python and Remote Control plugins.
      100
      6
      -

    • 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.
      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.9/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Wwise project management: auditing, creation, editing, inspection, soundbank operations, and cross-referencing. Overlaps are minimal and clearly differentiated by descriptions (e.g., wwise_audit vs wwise_naming_check vs wwise_audio_file_check).

    Naming Consistency5/5

    All tools follow the wwise_ prefix with snake_case and a verb_noun pattern (e.g., create_container, assign_shareset, fix_all). The naming is highly uniform and predictable.

    Tool Count4/5

    20 tools is on the higher end, but the domain of Wwise project management justifies the breadth. Each tool serves a clear purpose without redundancy, making the count reasonable though slightly above the ideal range.

    Completeness4/5

    The tool set covers major workflows: auditing, creation, editing, soundbank management, documentation, and Unity integration. Minor gaps exist (e.g., no delete tool, limited event modification), but overall the surface is comprehensive for typical audio designer tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources