Wwise FAQs

Question 1

What is Wwise-MCP and how does it integrate with Wwise?

Accepted Answer

Wwise-MCP is a Model Context Protocol (MCP) server that enables Large Language Models (LLMs) to interact directly with the Wwise Authoring application. It exposes custom WAAPI functions, allowing AI clients like Claude or Cursor to automate various audio production tasks within Wwise.

Question 2

Is Wwise-MCP suitable for production-level game audio projects?

Accepted Answer

Currently, Wwise-MCP is in an **EXPERIMENTAL** state. While under active development, it's not recommended for production use due to potential breaking changes, incomplete features, and instability. It's best used for experimentation and development.

Question 3

What key features does Wwise-MCP offer for game audio development?

Accepted Answer

Wwise-MCP provides features like Wwise session connection, hierarchy indexing, automated object creation (actor-mixers, containers, buses), batch event authoring, real-time game object management, RTPC/Switch/State setup, audio import, and soundbank configuration.

Question 4

What are the prerequisites for setting up Wwise-MCP?

Accepted Answer

To use Wwise-MCP, you'll need an MCP compatible AI client (e.g., Claude Desktop or Cursor), Wwise 2024.1+, and the Wwise-MCP application package. Detailed setup instructions are available in the project's documentation.

Question 5

How do I start interacting with my Wwise project using Wwise-MCP and an LLM?

Accepted Answer

First, prompt your MCP client with "Connect to my Wwise project" to establish a connection. Then, use commands like "Resolve parent path" (e.g., 'Resolve all path relationships in actor mixer') to allow the LLM to index and navigate your Wwise project structure.

Wwise

Wwise

Key Features

Use Cases

Key Features

Use Cases