SoundCraft MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOUNDCRAFT_APP | No | Path of the desktop app when it lives elsewhere (e.g. a Linux AppImage) | |
| SOUNDCRAFT_CLI | No | Path of `soundcraft-cli` / `soundcraft-cli.exe` (wins over `SOUNDCRAFT_DIR`) | |
| SOUNDCRAFT_DIR | No | SoundCraft folder, one of its executables, a `.tar.gz` root (with `bin/`) or `SoundCraft.app`. Default: auto-detect | |
| SOUNDCRAFT_MCP_TIMEOUT | No | Maximum seconds per engine call (default 3600) | 3600 |
| SOUNDCRAFT_CONTROL_PORT | No | Control port of the desktop app (default 7801) | 7801 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sessionB | Build a song, podcast or soundtrack with SoundCraft (a Pro Tools-class DAW) and mix it down: audio tracks from files placed at times (clip gain, fades), instrument tracks played by the built-in subtractive synth, General MIDI drum synth or a sampler from notes in beats, imported MIDI files, per-track volume, pan, mute, solo, insert effects (EQ, compressor, reverb, delay, chorus, saturation...) and sends to aux busses, tempo, meter, key and markers. Writes the mixdown (wav, aiff, flac), the stems, the MIDI and the editable .scraft session, reports peak and integrated loudness (LUFS) and returns a waveform picture of the mix. |
| edit_sessionA | Open a .scraft session (or start from audio files) and change it: tempo, meter, key, markers, busses, add tracks (audio, instrument, MIDI file), change existing tracks by name (rename, volume, pan, mute, solo, add effects and sends), remove tracks, then write a new mixdown, stems, MIDI or a new copy of the session. The original session is never changed. |
| export_sessionA | Mix down one .scraft session, a list or every session in a folder: wav / aiff / flac mixdown (range, normalize, bit depth), stems (one file per track), MIDI, with peak and loudness (LUFS) of each mix. |
| process_audioB | Run audio files (one, a list or a folder) through SoundCraft: trim, AudioSuite processing (normalize to a peak, gain, reverse, invert, pitch shift in semitones, time stretch keeping the pitch, varispeed), insert effects (EQ, compressor, gate, de-esser, maximizer, reverb, delay, chorus, flanger, phaser, saturation, lo-fi...), fades, volume and pan, then write WAV, AIFF or FLAC at any bit depth, with peak and loudness (LUFS). Inputs are only read. |
| convert_audioB | Convert audio files (one, a list or a folder; WAV, AIFF, FLAC, MP3, OGG, M4A/AAC, ALAC, CAF in) to WAV, AIFF or FLAC, optionally changing the sample rate and bit depth or normalizing, with SoundCraft's converter. |
| get_audio_infoB | Format, channels, sample rate, bit depth and length of audio files, or the tracks, clips, plugins, busses, markers and tempo of a .scraft session. With loudness=true also the peak, true peak and integrated loudness (LUFS); with waveform=true a picture of it. |
| list_soundcraft_catalogA | What SoundCraft can do: commands (the engine commands with parameters and menu place, for run_soundcraft_commands), plugins (the built-in effects and instruments with every parameter id, range and unit, for |
| run_soundcraft_commandsA | Advanced: run any SoundCraft engine commands in order (session., file., edit., track., clip., mix., automation., event. (tempo, meter, key, MIDI edits), midi., markers., audiosuite.process...) plus the engine tools new_session / open_session / import_audio / inspect_session / bounce_mix / save_session (step id = the tool name), on a new or an opened session, then write outputs. Positions are samples, {"seconds": x} or "bars_beats:5|1|000". Parameters can use "$steps[N].field" for a value returned by step N (0-based). With live=true the steps drive the open SoundCraft app instead. |
| open_in_soundcraftA | Open a .scraft session in the SoundCraft desktop app to listen and keep editing by hand. With control=true the app also starts its loopback-only control channel so run_soundcraft_commands live=true can drive it (play, edit, screenshots). |
| get_soundcraft_statusA | Check the SoundCraft installation: platform, executables, version, engine commands, built-in plugins, Pro Tools feature coverage, formats, whether the app is running / listening for control. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target distinct lifecycle stages: create_session builds new, edit_session modifies existing, export_session only mixes down, process_audio transforms files, convert_audio changes formats. The main ambiguity is run_soundcraft_commands, a raw escape hatch that overlaps nearly everything, and export_session's mixdown overlaps the export capability embedded in create_session/edit_session, but the detailed descriptions keep boundaries usable.
Nearly all names follow a clean verb_noun snake_case pattern (edit_session, create_session, export_session, process_audio, convert_audio, get_audio_info, list_soundcraft_catalog, run_soundcraft_commands, get_soundcraft_status). The only minor deviation is open_in_soundcraft, which uses verb_prep_noun. Consistency is strong overall.
10 tools is well-scoped for a Pro Tools-class DAW server, covering the full lifecycle without bloat. Each tool earns its place, and run_soundcraft_commands provides depth without inflating the surface.
The surface covers create/edit/export of sessions, audio processing, format conversion, inspection, capability discovery, live app control, and status checks. The raw run_soundcraft_commands plus catalog tool act as escape hatches for any missing granular operations, leaving no obvious dead ends.