soundcraft
Installation
SKILL.md
SoundCraft
Operate SoundCraft through its structured automation interface. Preserve the user's requested session, routing, and audio content.
Protocol reference
Read the relevant sections of references/control-protocol.md before constructing calls. This is the downloaded upstream protocol, captured on 2026-11-15.
Source: SoundCraft control protocol. The documentation is distributed under the bundled MIT license. Relative links inside the snapshot (e.g. cli.md) resolve against https://github.com/storytold/soundcraft/blob/main/docs/. Discover command ids and parameter docs at runtime through engine.commands instead of inventing them.
Select the surface
Every command is reachable from several surfaces; pick by task:
- Desktop control channel:
soundcraft --control <port>(0picks a free port, printed asSOUNDCRAFT_CONTROL_PORT=…), driven over loopback TCP. - CLI against a running app:
soundcraft-cli app --port <port> <method or command id> [JSON]. - Headless CLI:
soundcraft-cli run --demo --cmd 'mix.volume={"track":"Kick","db":-6}' --bounce out.wav. - MCP:
soundcraft-cli mcp [--demo](headless) orsoundcraft-cli mcp --connect <port>(bridged to the live app).