AgentStack
MCP verified Apache-2.0 Self-run

Wwise MCP

mcp-bilkentaudio-wwise-mcp · by BilkentAudio

Wwise-MCP is a Model Context Protocol (MCP) server that enables large language models (LLMs) to interact with the Wwise Authoring application. It exposes a set of tools built on a custom Python WAAPI library, allowing MCP clients such as Claude or Cursor to automate and compose complex, multi-step Wwise workflows.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add mcp-bilkentaudio-wwise-mcp

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Wwise MCP? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Wwise-MCP (Model Context Protocol for Wwise)

[](https://www.apache.org/licenses/LICENSE-2.0) [](https://www.audiokinetic.com/en/wwise/) [](https://github.com/BilkentAudio/Wwise-MCP/releases/latest) [](https://github.com/BilkentAudio/Wwise-MCP/releases) []()

Wwise-MCP is a Model Context Protocol (MCP) server that enables large language models (LLMs) to interact with the Wwise Authoring application. It exposes a set of tools built on a custom Python WAAPI library, allowing MCP clients such as Claude or Cursor to automate and compose complex, multi-step Wwise workflows.

Watch the demo and installation guide on YouTube

⚠️ Experimental Notice

This project is currently in an EXPERIMENTAL state. It is still under active development and should not be used with Wwise projects intended for production at the moment. Please keep in mind:

  • Breaking changes may occur without warning
  • Features may be incomplete or unstable
  • Documentation may be outdated or missing
  • Production use is not recommended at this time

Installation

Prerequisites

Setup

  • Once you have the above 3 components installed, configure your MCP Client's (i.e Claude's or Cursor's) json file to include the Wwise-MCP application.
 {
    "mcpServers":
    {
         "wwise-mcp":
         {
           "command": "C:\\Your\\PathTo\\Wwise-MCP.exe",
           "args": []
         }
    }
 }
 ```
  https://github.com/user-attachments/assets/98141541-8286-4c1d-98f5-2052364bf4bb
- Refer to the [setup page](https://github.com/BilkentAudio/Wwise-MCP/tree/main/docs/setup) for detailed instructions on setting up with [Claude](https://github.com/BilkentAudio/Wwise-MCP/blob/main/docs/setup/Claude/ClaudeSetup.md) and [Cursor](https://github.com/BilkentAudio/Wwise-MCP/blob/main/docs/setup/Cursor/CursorSetup.md)

# ⚠️ macOS Security Blocker
- On macOS, you will most likely face an error on your first launch of Wwise-MCP after setup due to macOS security.
- To bypass it, open **Terminal** then run `chmod +x "/YourPathTo/Wwise-MCP-v1-0/macOS/Apple Silicon/Wwise-MCP"`
- Make sure to configure the above command to the path where you store your **version (Intel or Silicon)** of Wwise-MCP
- Relaunch your MCP Client (i.e Claude) once more. It may fail again. Navigate to **Privacy & Security** in **System Settings**
- There should be a `"Wwise-MCP" was blocked to protect your Mac` message. Select **Allow Anyway**.
- Relaunch your MCP Client (i.e Claude).

# Quickstart

1. **Connect to your Wwise project**  
   Always start with a prompt akin to **“Connect to my Wwise project”**.  
   This attaches Wwise-MCP to your currently open Wwise session.

2. **Let your MCP Client (i.e Claude) “see” your project structure**  
   Use the **“Resolve parent path”** command.  
   This builds an index of objects under a given Wwise path so Claude can cache and navigate your project by paths.
   A good place to begin is one of Wwise’s top-level roots, for example:
   - `\Actor-Mixer Hierarchy`, `\Containers (Wwise 2025)` 
   - `\Events`
   - `\Switches`, `\States`, `\Game Parameters`
  
   Example prompt:  
   > Resolve all path relationships in actor mixer.

3. Before using any game object–related prompts (e.g. “Post X event on 5 new game objects and spread them around 500 units from the origin”), make sure you’ve enabled “Start Capture” (red when enabled) in Wwise’s Game Object view.
   > 

# Features
- **Wwise Session Connection**: Connects to the active Wwise session so the agent can issue WAAPI commands to the appropriate wwise session.
- **Hierarchy Indexing**: Scans a parent path and builds a path-first index of the subtree for fast lookup and navigation.
- **Object Creation & Organization**: Creates actor-mixers, containers, buses, work units, soundbanks, folders, attenuations and more under specified parent paths, and can move or rename them in batches.
- **Property, Reference & Automation Configuration**: Sets object references, configures RTPC curves, attenuation curves and property randomizations.
- **Container Assignment & Playback Logic**: Assigns children to Switch Containers, Blend Tracks, and Random/Sequence Container playlists, enabling automated setup of switch-based, blend-based, and randomized playback structures.
- **Event Authoring**: Creates multiple Wwise events in one batch from source objects and parent paths, and lists all existing event names.
- **Music Authoring & Interactive Music Setup**: Assigns Music Switch Container arguments and entries, builds Music Playlist hierarchies, and retrieves authored Music Transition rules including sync, fade, and transition-segment settings.
- **Game Object Management**: Creates, moves, and unregisters game objects in batches, with full 3D positioning support and a global fallback object.
- **RTPC / Switch / State Setup**: Batch-creates RTPCs, switch groups, switches, state groups, and states, and exposes helpers to list and set them at runtime.
- **Audio Import & Discovery**: Imports folders of audio into Wwise under a target parent, and lists all audio files under a given file-system path.
- **Soundbank Configuration & Build**: Includes selected objects in soundbanks and generates soundbanks for specified platforms and languages using project metadata.
- **Runtime Audio Control**: Posts events with optional delays, sets RTPC ramps, switches and states, moves game objects over time, and stops all sounds in the captured session.
- **Advanced Project Queries & Dependency Analysis**: Executes arbitrary WAQL queries, retrieves detailed object information (including authored and resolved properties), discovers available properties/references, and finds every object that references a target object.
- **Remote Connection Management**: Connects Wwise Authoring to running Sound Engine instances or profiler captures, lists available targets, checks connection status, and disconnects remote sessions.
- **Effect & Plug-in Authoring**: Creates Effect ShareSets, adds effects to sounds, buses, and actor-mixers, configures plug-in-specific properties, and creates Source Plug-ins such as Sine, Tone Generator, and SoundSeed sources.
- **Profiler Capture & Runtime Diagnostics**: Starts and stops profiler captures, enables profiler data streams, retrieves voices, RTPCs, audio objects, bus activity, voice contribution trees, cursor positions, and exports captures to `.prof` files for offline analysis.
- **Object Lifecycle Management**: Deletes Wwise objects by path, GUID, or qualified name, and provides tools to inspect dependencies before removal.
- **Layout & Property Utilities**: Toggles Wwise layouts, sets object properties by path, retrieves the current selection, and lists valid property names and value types.
- Refer to [Tools](https://github.com/BilkentAudio/Wwise-MCP/blob/main/docs/tools/ToolList.md) page for detailed explanation of each functionality.

# Directory Structure

- **docs/** - Wwise-MCP documentation
  - **setup/** - Instructions for installing and configuring Wwise-MCP and MCP clients ([Claude](https://github.com/BilkentAudio/Wwise-MCP/blob/main/docs/setup/Claude/ClaudeSetup.md) & [Cursor](https://github.com/BilkentAudio/Wwise-MCP/blob/main/docs/setup/Cursor/CursorSetup.md))
  - **tools/** - A list of all functionalities and example prompts

- **app/** - Python server. Instructions for setting up Python environment can be found in the [README](https://github.com/BilkentAudio/Wwise-MCP/blob/main/app/README.md)
  - **scripts/** - Python application source code 

# Developers
- Wwise-MCP consists of 3 primary Python modules
- The main entry point is wwise_mcp.py
- Be sure you are using python version 3.13+
- More info can be found [here](https://github.com/BilkentAudio/Wwise-MCP/blob/main/app/README.md)

# License
Apache 

# Author
Built by Bilkent Samsurya 

Audio Programmer | AI-integrated Audio Tools | Wwise & Unreal Specialist

[Website](https://bilkentsam.com) •
[LinkedIn](https://www.linkedin.com/in/bilkentsamsurya) •
[Twitter/X](https://twitter.com/BilkentAudio)

# Feedback/Questions
Feel free to reach out to me at bilkentaudiodev@gmail.com

## Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [BilkentAudio](https://github.com/BilkentAudio)
- **Source:** [BilkentAudio/Wwise-MCP](https://github.com/BilkentAudio/Wwise-MCP)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.