wwise-mcp

You:    "These 8 gunshots — make them playable in-game, per our conventions."

Claude:  ✅ converted   ✅ wrapped in a Random container   ✅ created 8 Play_ events
         ✅ routed to the SFX bus   ✅ added to the Main SoundBank
         (preview shown first · one Ctrl+Z undoes the whole thing)

Sound designers burn hours in plumbing mode — naming, building events, dragging folders, hunting "why is there no sound?". wwise-mcp hands all of that to the AI so you stay in your ears. Read the sound-designer's workflow →

✨ Why you'll want this

• 🩺 Catches real bugs. Events not in any SoundBank, empty sounds, and the classic code calls AK_Reload but Wwise has AK_Relod typo — pinpointed to the exact file:line.

• ⚡ One-shot flows. "Onboard this batch" runs convert → container → events → bus → bank in a single sentence. "Check everything and fix what's safe" audits then fixes.

• 🛡️ Safe by design. Every write previews first and undoes in one Ctrl+Z. It never touches the risky stuff (duplicates, empty sounds) without you.

• 🎧 Stays out of your art. It does the plumbing; mixing, sound choice, and feel stay yours.

• 🔌 20 tools, every one live-validated against real Wwise 2024.1 — not vaporware.

Related MCP server: Unity MCP

Setup

1. In Wwise: User Preferences → enable Wwise Authoring API (WAMP, default port 8080), then open a project.

2. Install:

   python3.12 -m venv .venv && . .venv/bin/activate && pip install -e .

3. Register with your MCP client (stdio). Use the absolute path to the venv entry point so it works without activating the venv first. For Claude Code:

   claude mcp add wwise -- /Users/inl/wwise-mcp/.venv/bin/wwise-mcp

   Or in an MCP client config JSON:

   { "mcpServers": { "wwise": { "command": "/Users/inl/wwise-mcp/.venv/bin/wwise-mcp" } } }

Tools

All 20 tools are live-validated against Wwise v2024.1.13. Write tools use a two-step mode="plan" (preview + token) → mode="apply" (execute, undoable) flow.

For how this fits a sound designer's actual day, see WORKFLOW.md.

One-shot flows (compose the building blocks — start here)

Read / inspect

Document

Write (plan/apply)

Action

Write tools show exactly what will change before anything is written, and each batch is one Ctrl+Z to undo.

Not yet implemented

• RTPC/Switch wiring — deferred: the @RTPC curve-object structure could not be cleanly validated via WAAPI in this environment, so a write op was not shipped rather than ship an unvalidated mutation. See docs/superpowers/notes/.

Compatibility

Requires Wwise 2021.1+ (the version that introduced WAQL, which most tools use). Run wwise_compat_check first on any untested version to see what works.

Help expand this matrix: see CONTRIBUTING.md — capturing your version takes ~5 minutes and no coding (python scripts/capture_fixtures.py → PR).

Tests

pytest -m "not integration"   # unit + contract (runs across all version fixtures) — no Wwise needed
pytest -m integration         # requires a running Wwise + open project

Design & plans

• Design spec: docs/superpowers/specs/2026-06-13-wwise-mcp-design.md

• Foundation plan: docs/superpowers/plans/2026-06-13-wwise-mcp-foundation.md

• Open WAAPI questions: docs/superpowers/notes/waapi-precondition-findings.md