Wwise-MCP is a Model Context Protocol server that allows LLMs to interact with the Wwise Authoring application. It exposes tools from a custom python waapi function library to MCP clients.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"wwise-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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 automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in entertainment / developer-tools
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
MCP Security Weekly
Get CVE alerts and security updates for Wwise MCP and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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
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:
{
"mcpServers":
{
"wwise-mcp":
{
"command": "C:\\Your\\PathTo\\Wwise-MCP.exe",
"args": []
}
}
}
https://github.com/user-attachments/assets/98141541-8286-4c1d-98f5-2052364bf4bb
chmod +x "/YourPathTo/Wwise-MCP-v1-0/macOS/Apple Silicon/Wwise-MCP""Wwise-MCP" was blocked to protect your Mac message. Select Allow Anyway.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.
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 ParametersExample prompt:
Resolve all path relationships in actor mixer.
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 Captur