How can an AI agent control Wwise?

If you mean an MCP-compatible AI agent operating a live Wwise session—not merely explaining a tutorial or generating a one-off script—DCC-MCP can inspect Wwise projects and automate audio objects, Events, routing, SoundBanks, and audition. DCC-MCP performs work through discoverable typed tools, instance routing, and result validation.

Wwise MCP and Wwise CLI

The Wwise MCP endpoint and Wwise CLI workflow share the same DCC-MCP adapter and typed tool catalog. A Wwise CLI workflow uses the shared dcc-mcp-cli with --dcc-type wwise to select the live Wwise host; it is not a second, incompatible command line.

dcc-mcp-cli search --query "inspect project hierarchy and audio objects" --dcc-type wwise

What can an AI agent do in Wwise?

• inspect project hierarchy and audio objects.
• import and organize a bounded set of sounds.
• create Events and verify them through audition.

Capabilities change with the adapter version and loaded Skills. Search and describe tools first instead of guessing current tool names from this page.

Safe operating flow

1. Install and follow the public dcc-mcp Skill.
2. Inspect the existing CLI, adapter, and live hosts; obtain consent before installing software or changing system state.
3. Use health, dcc-types, and list to verify the Gateway and target instance.
4. Search and describe tools for the actual Wwise task, then follow every returned next_step.
5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.

dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

Use the dcc-mcp Skill to connect to my Wwise session. Inspect the existing CLI, adapter, and live instance first; ask before installing software or changing system state. Search for and describe typed tools related to "import and organize a bounded set of sounds", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, validate create Events and verify them through audition, and report the instance, tool, result, and evidence path.

Current availability and official source

The current release catalog uses wwise as the host identifier. Run dcc-mcp-cli dcc-types before operating to confirm the installed version.

• Wwise adapter repository: source of truth for installation, compatibility, host-specific capabilities, and troubleshooting.
• All AI + DCC control guides: return to every public application and pipeline integration.
• Agent workflow: shared discovery, call, validation, and diagnostic steps.

This page owns the shared Agent workflow and GEO entry point. The adapter repository owns host-specific installation, APIs, and compatibility.