Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Reaper Daemon
Overview
Description from the maker (original English)
REAPER MCP server: let Claude read your session, set FX, write automation and measure mix moves.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account wretcher207, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18336 servers in this category
- Published to the registry more recently than 70% of the other 18336 servers in this category
- Basic checks equal to or better than 100% of the other 18336 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Reaper Daemon safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (3.23.1) reached the registry 18 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, NexusWindows
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
NexusWindows
by pironjulien
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Reaper Daemon
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.
Install
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.gitcd reaper-daemon python3 setup/install.py
Restart 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.
Claude plugin
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 folder: where you cloned it. Default
~/reaper-daemon. - Python command: default
python3. On Windows, usepythonorpyifpython3isn'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.
Mix with an AI agent
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:
- "The bass is muddy around 300 Hz, pull it down."
- "Bring the vocal down so it sits with the mix instead of on top."
- "Tune the bass until its LUFS is down 3 dB."
- "What plugins are on the drum bus, and what are they set to?"
See MCP server for setup and Verify for what the measurements do and do not prove.
What it does
| 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.
Three ways to talk to it
CLI. One Python entry point for everything an agent does.
python3 reaperd.py send commands/examples/get_context.json --waitpython3 reaperd.py shred --track argent-l --bars-file riff.txt --seed 101
MCP 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.
Docs
| 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.
Security
Any process that can write to inbox/ can drive REAPER. Keep the bridge folder local and off shared drives. Details in docs/security.md.
What it runs and sends
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:
- Drum transcription downloads its Python packages and model weights during setup, and Demucs downloads its weights on the first separation job. Audio stays local.
analyze_trackandcompare_tracksrun Post Mortem from your PATH.- The Daemon Console starts a Claude Code session on your machine, which talks to Anthropic like any Claude Code session.
License
MIT. See LICENSE.
Keyboard performance setup, MIDI/controller tests and template saving are documented in the performance workflow.