SoundCraft MCP Server — Give Your AI Agent a DAW

MCP needs the desktop download on your computer. The browser version on this site has no control channel and can’t be driven by an agent; for help while you work in the browser, open the AI mixing assistant.

Get the CLI

soundcraft-cli ships with the desktop builds: the Windows installer and portable zip, every Linux package and the FreeBSD tarball. On macOS it is a separate download, soundcraft-cli-0.5.0-macos-universal.zip, signed and notarized.

Set up with Claude Code

claude mcp add soundcraft -- soundcraft-cli mcp --demo

Or add it to your agent’s MCP configuration (.mcp.json in a project for Claude Code):

{
  "mcpServers": {
    "soundcraft": {
      "command": "soundcraft-cli",
      "args": ["mcp", "--demo"]
    }
  }
}

Without --demo the agent starts from an empty session. To let the agent work in the app window you are looking at, start the app with a control port and connect the server to it:

soundcraft --control 7801 &
soundcraft-cli mcp --connect 7801

What the agent gets

Tool	What it does
`list_commands`	Every command with its id, label, menu path, shortcut, parameters and whether it is enabled
`execute`, `batch`	Run one command, or several in order, with JSON parameters
`inspect_session`	Tracks, clips, mixer, plugins, sends, automation, markers and selection, to check the work
`new_session`, `open_session`, `save_session`	Session files (`.scraft`, with audio in an Audio Files folder)
`import_audio`	WAV, AIFF, FLAC, MP3, OGG, AAC/M4A, ALAC or CAF onto a new or existing track
`bounce_mix`	Render to WAV, AIFF or FLAC and report peak dBFS and integrated LUFS
`screenshot`, `click`, `drag`, `key`, `menu_invoke`	Only with `--connect`: see and operate the app window

Programmatic calls never open dialogs; empty parameters act on the current selection. Tracks can be named ("Kick") or given by id, and positions can be samples, {"seconds": 2.5} or a time string such as "bars_beats:5|1|000". The full session JSON and the command list are also available as resources.

Prompts to try

“Open the demo, turn the Kick down 3 dB, put a 7-band EQ on the Bass with a high-pass at 40 Hz, and bounce the mix to mix.wav. Tell me its loudness.”
“Import vocal.wav onto a new track, add a compressor and a send to a reverb aux, then save the session.”
“Add a marker at every chorus and write a volume fade-out over the last 4 bars.”

Without MCP: the CLI on its own

# Headless: load the demo, turn the kick down, add an EQ, bounce.
soundcraft-cli run --demo \
  --cmd 'mix.volume={"track":"Kick","db":-6}' \
  --cmd 'mix.insert={"track":"Bass","plugin":"eq_7band"}' \
  --bounce mix.wav

soundcraft-cli commands mix          # list commands, filtered
soundcraft-cli plugins               # built-in plugins
soundcraft-cli convert in.wav out.flac --bit-depth 24

FAQ

Can an AI agent control the browser version on this site?

No. Browsers cannot open the TCP control channel the agent tools use, so the web build has none. The MCP server is part of soundcraft-cli and runs on your computer, either headless or connected to the desktop app. In the browser, the AI assistant panel explains steps for you to follow instead.

Which agents work with it?

Any MCP client that can launch a local stdio server: Claude Code, Claude Desktop, Cursor, VS Code agents and others. They all take the same command: soundcraft-cli mcp, with --demo to start from the demo song.

Does it open a network port?

The headless server talks over stdin and stdout only. Driving the desktop app needs you to start it with --control <port>, which listens on 127.0.0.1, so only programs on your own computer can connect.

Can the agent undo what it did?

Yes. Every command is undoable through edit.undo unless it is a query or a view setting, and session.inspect reports exactly what changed, so an agent can check its own work.

Source: the SoundCraft README, MCP guide and control protocol. Commands can change between releases; check soundcraft-cli commands.