
Free, open source REAPER MCP server that lets an AI agent (Claude or any MCP client) drive REAPER
Free, open source REAPER MCP server that lets an AI agent (Claude or any MCP client) drive REAPER: read every plugin and parameter, set FX values, write automation, and measure a mix move before and after. MIT. macOS, Windows, Linux.
·
Reaper Daemon is a REAPER MCP server and file bridge for driving REAPER from an AI agent, including mixing your session with Claude or any other agent. No network socket, no port, no extensions.
The agent drops a JSON command file in a folder. A Lua script inside REAPER
runs it and writes a JSON result back. That's the whole protocol. It works
with Claude Code, Codex, Cursor, or anything else that can read and write
files, and an optional stdio MCP server, reaper_mcp.py, exposes the same
bridge as tools for Claude Desktop and any other MCP client.
macOS, Windows, Linux. Pure Lua inside REAPER, plain Python 3 outside, no pip packages for the core bridge and MCP server. Audio-to-drum MIDI transcription uses a separate optional model environment. Every change runs inside a REAPER undo block, so Ctrl+Z reverts anything an agent does.
Reaper Daemon has two halves, a Lua bridge that runs inside REAPER and the tools that talk to it. Both come from a clone of this repository on the computer REAPER runs on, so install here first, even if you found it through the Claude plugin directory.
git clone https://github.com/wretcher207/reaper-daemon.git
cd reaper-daemon
python3 setup/install.pyRestart REAPER, then check the bridge is alive:
python3 reaperd.py statusRendering and audio capture are off until you allow them, and every
measurement needs them, including verify_change. To do that, run:
python3 setup/install.py --allow-audio-writesSaving the project, changing REAPER preferences and running Lua scripts have their own switches; see docs/install.md.
Prefer ReaPack, or want to load the bridge by hand? See docs/install.md.
The repository is also a Claude plugin. It bundles the MCP server with five skills: setup, drum programming, drum humanizing, guitar and bass parts, and MIDI for an existing arrangement. The plugin drives the install above, so if you added it before installing, ask Claude to set up Reaper Daemon. The setup skill finds what's missing, runs the clone and installer with you, asks which disk writes to allow, and checks that REAPER answers.
When you add the plugin, Claude asks for two settings:
~/reaper-daemon.python3. On Windows, use python or py if
python3 isn't on your PATH.Cowork doesn't ask, so it uses those defaults. To try the plugin in Claude Code straight from your clone:
claude --plugin-dir /path/to/reaper-daemonThe MCP server runs on your computer, next to REAPER. It works in Claude Code and in Cowork sessions on your machine. Chat on claude.ai loads the skills but can't reach REAPER.
Point Claude, or any agent talking to Reaper Daemon, at your open REAPER
session and ask it to work on the mix. It reads every plugin and parameter
with scan_fx, sets FX values in real units like "-2.5 dB", and writes
automation. verify_change captures the track before and after a move and
reports what changed in the audio, so you are not taking its word for it.
Every move sits inside a REAPER undo block, and your ears make the call.
Example prompts:
See MCP server for setup and Verify for what the measurements do and do not prove.
| Area | Commands |
|---|---|
| Project | transport, tempo and the tempo map, cursor, time selection, render, save |
| Tracks | add, delete, rename, select, volume, pan, mute, solo, arm, color |
| Routing | read sends and receives, create sends, toggle master feed |
| FX | add, remove, bypass, reorder, set parameters, write automation, save chains |
| Markers, regions, media items | full read and write |
| MIDI | insert MIDI files, plus a drum DSL with humanization |
| Transcription | turn an audio item into drum MIDI with an optional local analysis runtime |
| Guitar and bass | shred renders a humanized riff, band cuts a whole rhythm section |
| Discovery | scan_fx dumps every plugin and parameter; discover_drum_map reads any kit's note map |
| Verify | measure loudness, spectrum and dynamics before and after a mix move |
| Actions and scripts | search and run anything in REAPER's action list; run Lua by source or path, behind its own switch |
The bridge knows nothing about any specific plugin or drum library. Agents discover what a project contains and act on it by name.
CLI. One Python entry point for everything an agent does.
python3 reaperd.py send commands/examples/get_context.json --wait
python3 reaperd.py shred --track argent-l --bars-file riff.txt --seed 101MCP server. reaper_mcp.py wraps the bridge as tools over stdio.
Ask Claude Desktop to "measure the drums" and it does.
Daemon Console. A chat panel docked inside REAPER, backed by a headless Claude Code session that always knows which track you have selected.
| Install | one-line installer, ReaPack, manual load |
| CLI | reaperd.py reference |
| MCP server | setup for Claude Desktop and other clients |
| Daemon Console | the in-REAPER chat panel |
| Drums | kit discovery, stem profiling, humanize |
| Composing workflow | writing full songs with sampled instruments: measure, articulate, vary cymbals, verify |
| Drum workshop | separate composition briefs, MIDI comparisons, scoped audition feedback |
| Drum transcription | audio to MIDI, background jobs, kit mapping |
| Guitar and bass | shred and band |
| Mix recipes | capture, compare and rebuild a mix setup |
| Verify | closed-loop mix moves with measured proof |
| Protocol | the file wire format |
| Troubleshooting | silent captures, stale heartbeats |
| Watchdog | unattended runs: relaunch REAPER, dialogs, stale queue files |
| Song planner | instrument library, song sheets, approved drafts |
| Security | trust model and the optional token |
| Develop | tests, CI, repo layout |
Agents should read AGENTS.md, CLAUDE.md, and bridge/command_schema.md. Two bundled skills, arrangement-midi and drum-humanize, cover MIDI composition and drum humanization. song-planner plans and drafts whole songs from a brief, a riff or a reference.
Any process that can write to inbox/ can drive REAPER. Keep the bridge
folder local and off shared drives. Details in docs/security.md.
Everything runs on your machine. The MCP server and CLI are plain Python with no network calls. The bridge is a Lua script inside REAPER. It trades JSON files with the server through the Reaper Daemon folder, which also holds logs and the MIDI files it generates. Renders and captures write audio files only if you turn on audio writes, which are off by default. Nothing leaves your computer.
Three optional pieces do more, and only if you install them:
analyze_track and compare_tracks run
Post Mortem from your PATH.MIT. See LICENSE.
Keyboard performance setup, MIDI/controller tests and template saving are documented in the performance workflow.
This repo does not document an install step we could read. Check the README on GitHub.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/reaper-daemon to learn what the "Reaper Daemon" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
This server doesn't publish a machine-readable tool manifest, and it doesn't expose a public endpoint we could ask. Connect the server locally to see what it exposes.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/reaper-daemon)Nothing comparable is listed yet.
v3.23.1Release notesv3.23.0Release notesv3.22.1Reaper Daemon 3.22.1Release notesv3.22.0Reaper Daemon 3.22.0Release notesv3.21.03.21.0: Audio-to-drum MIDI transcriptionRelease notesv3.20.0Reaper Daemon 3.20.0Release notesv3.19.0Reaper Daemon 3.19.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "reaper-daemon" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.