Most DAW integrations stop at transport control — play, stop, record. This one opens the production surface: genre-tuned mix and master engines across 35 style profiles, a vocal-chop pipeline, drum and chord shorthand, sidechain and bus recipes, so a track can go from empty project to bounced stems in one conversation. Everything moves through a file-based bridge inside REAPER, which is why nothing is uploaded anywhere — and why REAPER has to be open with that script loaded before a single tool works.
A local bridge into REAPER. The assistant writes the notes, CC curves and arrangement itself and drives the DAW through a file-based Lua script running inside it, so the project, audio and MIDI never leave the machine.
- MIDI written note by note or in batches, with quantize, humanize, CC curves, program and bank changes, and note-name lookup
- Shorthand for what you would otherwise place by hand: multi-lane step notation for drum patterns, and a chord string like "Cm7, Fm7, Bb7, Eb" parsed into voiced MIDI
- Tracks, items, takes, markers, regions, tempo markers, time selection and loop points under direct control
- Automatic mixing and mastering across 35 style profiles — per-track EQ, compression and reverb buses, then a master chain aimed at that style's LUFS and true-peak targets
- A non-destructive repair pass that re-runs the mix pipeline on an existing session and keeps your tweaks where it can
- Ready-made bus recipes: parallel compression, a drum bus, a vocal chain, and pin-mapped kick-to-bass sidechain with a single amount dial
- FX added, removed, reordered and renamed, parameters set by name or index, presets read and set, plugin UIs opened
- Installed-plugin detection reporting the best EQ, compressor, reverb and limiter actually on the machine, with per-category preferences you can pin
- A vocal-chop pipeline end to end — split at transients, rearranged to a style's rhythm, pitched to chord tones, stacked and faded — plus the primitives on their own
- A loop-library workflow: scan a sample-pack folder for BPM, key and role, settle the common BPM, then batch-load the stems onto new tracks
- Project operations: new, open, save, save-as, backup, undo and redo, render metadata, and export to WAV, MP3, OGG, FLAC or AIFF
- Stems bounced per track, automation envelopes read, written and cleared, sends created and the whole routing drawn as a diagram
- ReaScript files in the project's Scripts tree discovered and run
Python 3.10 or newer, and REAPER 7 or newer already open. pip install xdarkzx-reaper-mcp gives you the reaper-mcp command; the repository's install.bat or install.sh does the same and also configures Claude Desktop and sets REAPER to auto-load the bridge. Either way REAPER needs reaper_scripts/reaper_mcp_server.lua running — it is not bundled into the PyPI package, and nothing works without it, because the server reaches REAPER through a file on disk and cannot launch it for you. No account, no key, no network calls. REAPER_MCP_PROFILE narrows the tool surface to composition, mixing, analysis or minimal for models that cap how many tools they accept, and the loudness, clipping and spectrum analysis tools need the optional analysis extra installed.
One command — pip install xdarkzx-reaper-mcp