GWwise — Wwise MCP Server

Connect an AI assistant to Audiokinetic Wwise for game-audio batch editing, project inspection, profiling, and audition. GWwise is a local Model Context Protocol (MCP) server backed by the Wwise Authoring API (WAAPI).

English · 简体中文 · Download Windows executable · Workflows · Compatibility · Validation

Canonical project: WilliamWAudio/wwise-mcp-server. Repository name: wwise-mcp-server; executable and MCP server name: gwwise-mcp-server; short name: GWwise. This is an independent community project, not an Audiokinetic product.

What can I use it for?

• Replace Wwise audio sources by name without intentionally creating new Sound objects.

• Batch rename and organize objects, copy or move missing descendants, and synchronize Output Bus references by relative path.

• Inspect a project with WAQL, read properties and references, and discover the connected Wwise instance's actual API schemas.

• Generate SoundBanks, sample Profiler data, and audition audio through Wwise Authoring.

• Subscribe to WAAPI events instead of repeatedly querying the same state.

The public catalog exposes 45 MCP tools: 44 definitions in knowledge/defs.json, plus wwise_connect added by the server. Of these, 17 names start with batch_. These are interface counts, not a benchmark or a claim that every workflow is one call.

Related MCP server: SK Wwise MCP

Why consider GWwise?

Quick start: Windows executable

1. Download gwwise-mcp-server.exe from GitHub Releases. This is a local stdio server, not a hosted service to deploy to a cloud URL.

2. Open a backed-up test copy of your Wwise project.

3. Enable Project → User Preferences → Wwise Authoring API. Confirm the WAMP port; the usual default is 8080.

4. Register the executable in an MCP-compatible client. Replace the example absolute path with your real path.

Claude Desktop / Claude Code configuration example (claude_desktop_config.json / .mcp.json):

{
  "mcpServers": {
    "wwise": {
      "command": "C:/Tools/GWwise/gwwise-mcp-server.exe",
      "args": ["--wwise-host", "127.0.0.1", "--wwise-port", "8080"]
    }
  }
}

Cursor example (.cursor/mcp.json):

{
  "mcpServers": {
    "wwise": {
      "command": "C:/Tools/GWwise/gwwise-mcp-server.exe",
      "args": ["--wwise-port", "8080"]
    }
  }
}

Codex configuration example (config.toml):

[mcp_servers.wwise]
command = "C:/Tools/GWwise/gwwise-mcp-server.exe"
args = ["--wwise-host", "127.0.0.1", "--wwise-port", "8080"]

Client configuration locations and approval controls vary by client version. The server can start before Wwise is open and connects when a tool needs WAAPI. Its connection code may try nearby fallback ports: verify the returned project and endpoint before any edit, especially when multiple Wwise instances are open.

First request: inspect, do not edit

Connect to Wwise and report the connected application version and project identity. Query the selected objects and list available schemas. Do not change project objects, save the project, generate SoundBanks, delete files, start playback, or change the profiler session.

This is an instruction to the assistant, not a server-enforced permission boundary. A client that supports tool allowlists should expose only the needed inspection tools first.

Practical workflows

These are reproducible workflow guides, not a claim that the scenarios were run successfully during this documentation update.

Example requests:

• “List every Sound under Weapons whose volume is below -10 dB. Report the GUID and path; do not modify anything.”

• “Compare the selected subtree with these same-name WAV files. Show the proposed matches first; do not replace audio until I confirm.”

• “Preview moving missing descendants from this source to this target. Use an explicit preview_only: true where the tool supports it.”

• “Subscribe to object name changes, wait for an event, then unsubscribe when finished.”

Tool catalog

The authoritative parameter definitions are in knowledge/defs.json and src/bin/mcp_server.rs. Inspect the schema instead of assuming similarly named tools have identical options.

Safety and limitations

• Back up the project and Originals before writes. Query and confirm the intended project, GUIDs, scope, and changes first.

• Preview is tool-specific. Explicitly set preview_only when supported. batch_replace_audio_by_name and raw batch_delete do not provide the same preview contract.

• Undo groups are not transactions. Batches can report per-item failures or leave partial changes. Follow-up routing work may use another undo group. Do not promise a single Ctrl+Z reverses every workflow.

• Disk changes are a separate risk. cleanup_unused_originals_files can permanently delete files; Wwise Undo does not recover them. A preview can also write a report. Do not enable cleanup as part of routine inspection.

• Profiler capture and audition affect sessions. Sampling may enable profiler data, and playback tools produce audible sound. Get permission before either, and verify the final state.

• The default endpoint is local, not an authorization sandbox. Host arguments and connection tools can select other endpoints. Keep WAAPI on a trusted network. The AI client has its own data and privacy policies.

• Schema discovery does not guarantee correct edits or audible results. Wwise versions, structure, languages, plugins, and client behavior still need testing.

Compatibility and evidence

The maintainer previously reported use across Wwise 2019–2025; the repository description separately mentioned 2021 and 2024. Exact-build evidence is not yet published in this checkout, so these are not presented as a verified per-version support matrix. See compatibility for recording a run.

The source contains 175 test cases across unit, definition-contract, knowledge-text routing-contract, protocol, and live-Wwise suites. This does not mean 175 live-Wwise tests: there are nine live test functions, and some tests return early when Wwise or the private knowledge base is absent. A green aggregate alone is not proof of E2E coverage. See validation and reproduction.

Build from source

Install a Rust toolchain and the platform's native build prerequisites, then run:

cargo build --release

The Windows executable is target/release/gwwise-mcp-server.exe. A source build has the same public tool definitions but fallback instructions because knowledge/base.txt is intentionally absent. Do not infer non-Windows support or a minimum Rust version from this command; see compatibility.

Documentation and metadata checks for contributors (Node.js required only for this check, not for running GWwise):

node scripts/check-docs.mjs

Distribution and discovery

• Windows EXE releases remain the direct installation path.

• MCPB packaging and Registry preparation describe an optional bundle. A raw .exe is not an MCPB package. No new Registry publication is claimed by these files.

• glama.json identifies the maintainer for directory metadata; it does not claim ownership verification or directory review is complete.

• Maintainer discovery checklist covers repository About/topics, directory corrections, public evidence, and genuine community examples.

License and project ownership

• Public source code, tool definitions, and public documentation: MIT. See the standard root LICENSE.

• Tuned knowledge base (knowledge/base.txt) and that content embedded in official binaries: proprietary. The original free personal/commercial use and restrictions remain in knowledge/LICENSE. Do not describe the entire official binary as MIT-licensed.

• GWwise does not include Wwise or grant rights to Wwise, third-party plugins, or your audio assets.

Maintainer: WilliamWAudio / william.wang. Report reproducible problems in GitHub Issues, including the GWwise version, exact Wwise build, operating system, task, and redacted error. Do not post private project paths, credentials, or copyrighted audio without permission.