REAPER MCP Servers Compared, 2026

I built one of these. Reaper Daemon is my open-source MCP server and file bridge for driving REAPER from Claude or any other agent, and I have a stake in you picking it. So here’s the deal. This article covers the main alternatives I could verify, says where they beat mine, and doesn’t pretend the field is smaller than it is.

A REAPER MCP server is a bridge that lets an AI agent read and change a REAPER session: tracks, FX, automation, sometimes the audio itself. They differ on three things that actually matter. How they talk to REAPER, whether they need anything installed beyond REAPER and Python, and whether they can tell you what a change actually did to the sound instead of just reporting that it ran. Pick on those three, not on the tool count in the README.

The comparison

Project	License	Connects to REAPER via	Installs beyond REAPER	Measures audio
Reaper Daemon	MIT	File bridge	Python only, no pip packages	Before and after a change
bonfire-systems/reaper-mcp	MIT	python-reapy	mcp, reapy, numpy, librosa, more	Yes, on a project render
shiehn/total-reaper-mcp	MIT	File bridge	mcp, uvicorn, websockets	Peak detection, no LUFS found
dschuler36/reaper-mcp-server	MIT	Reads .RPP files, no live connection	mcp, numpy, scipy, pyloudnorm	Yes, pre-FX source files
xDarkzx/Reaper-MCP	Apache-2.0	File bridge	mcp, optional analysis extras	Yes, LUFS and spectrum
TwelveTake reaper-mcp	MIT	File bridge	mcp	Peak meters only
fadelabs/phantom	AGPL-3.0	Fork of TwelveTake’s bridge	Essentia and related packages	Yes, on exported files
Reagent	Paid, $8 to $65/mo	Desktop app, mechanism not published	Cloud account	Claimed on its site
ReaAssist	Free, your API key	Lua script inside REAPER	ReaImGui, optional SWS	Not by itself

Every entry above comes from the project’s own README, site, or GitHub metadata as of September 13, 2026. Where a project’s own numbers disagreed with each other, both are noted.

Reaper Daemon

This is mine. It’s a JSON file bridge. The agent drops a command file in a folder, a Lua script inside REAPER reads it and writes the result back, and nothing ever opens a port. That part isn’t unique to me. xDarkzx, TwelveTake, and total-reaper-mcp all use the same file-bridge shape, and Hipare and Phantom build on top of two of those bridges. What actually sets Reaper Daemon apart is that it has no pip dependencies at all, just Python’s standard library, where every other Python server in this list needs at least the mcp package and usually several more on top of it. It also runs verify_change, a single tool that measures the track before and after a mutation and hands back what actually moved, plus tune_param for searching toward a target value. Phantom does something similar with its export, measure, change, re-export, re-measure workflow, so credit where it’s due, mine wraps the whole loop, capture, change, capture again, compare, into one tool call.

bonfire-systems/reaper-mcp

Bonfire has the deepest analysis suite of anything on this list. Loudness, dynamics, frequency spectrum, stereo field, transients, and clipping, all run against a real render of the project. It connects over python-reapy’s network bridge rather than a file drop, which adds python-reapy to the stack. If you want the broadest set of measurement tools and don’t mind the extra dependencies, numpy, librosa, pyloudnorm, soundfile, this is the one to look at first.

shiehn/total-reaper-mcp

This is the tool-count leader, with profiles running from 15 tools up to a claimed 600+ covering close to the whole ReaScript API. That breadth is real, and if you need a specific obscure REAPER function exposed as a tool, this is the project most likely to already have it. It was built macOS-first, though, and Windows users have to set an environment variable by hand to point it at the bridge folder.

dschuler36/reaper-mcp-server

This one doesn’t connect to a running REAPER session at all. It reads .RPP project files and the source audio directly off disk, which means no live control, but also means it can measure LUFS, true peak, spectral centroid and stereo phase on your actual pre-FX source files without REAPER open. If what you want is an agent that can tell you what’s wrong with your source material before you even touch a fader, this is a clean, narrow tool for that.

xDarkzx/Reaper-MCP and TwelveTake-Studios/reaper-mcp

Both run the same file-bridge shape as Reaper Daemon, and both are worth a look if tool count is what you’re after. xDarkzx reports somewhere between 172 and 182 tools depending on where you read the number, including genre-specific mix and mastering chains with named profiles. TwelveTake claims up to 176 and says it’s been live-tested on REAPER 7.79, though its audio analysis is limited to peak and peak-hold metering, no LUFS or spectrum. If you want an in-REAPER chat interface bundled on top of one of these bridges, Hipare wraps total-reaper-mcp’s bridge with a Node web UI, Windows only.

fadelabs/phantom

Phantom is the project that comes closest to what verify_change does. Its workflow exports the track, measures it, applies a change, exports again, and re-measures, with 20 tools covering spectrum, loudness, dynamics, stereo, and phase problem detection. The difference is mechanical. Phantom’s loop runs on exported files, Reaper Daemon’s runs as a single tool call inside the session. Phantom is also AGPL-3.0 and macOS or Linux only, so Windows users are out regardless of which approach they prefer.

Reagent and ReaAssist

Reagent is a paid desktop app, 8 to 65 dollars a month after trial credits, that claims plain-English REAPER control plus on-device loudness and spectral analysis, and it adds UCS classification and Wwise integration that none of the open-source tools here touch. ReaAssist is free and lets you bring your own API key from Claude, OpenAI, Gemini, or a local model, and it wraps every change in a per-message undo with an automatic backup before it runs anything. Neither one publishes enough about its internals for a full side-by-side on the mechanism, so take the audio-analysis claims from their own sites as unverified rather than confirmed.

How to choose

If you just want to ask an agent questions about a project, a few pull the mix, tempo and routing straight out of a REAPER session or a project file with no audio analysis needed, and dschuler36’s read-only tool is the simplest of those since it needs REAPER closed entirely.

If you want mixing help backed by actual measurement, bonfire has the widest suite of analysis tools, xDarkzx and Phantom both measure loudness and spectrum too, and Reaper Daemon’s verify_change is built specifically to prove a single move did what you asked before you trust it.

If you’re working in MIDI and composition rather than mixing, look at whichever server exposes the deepest ReaScript coverage, which right now is total-reaper-mcp, or a bridge with a dedicated MIDI toolset like Reaper Daemon’s drum DSL and humanization.

If you’re on Windows, check before you install. Phantom doesn’t run there at all, and total-reaper-mcp needs an environment variable set by hand. Hipare goes the other way and runs only on Windows. xDarkzx tests on all three operating systems in CI, and Reaper Daemon’s installer handles Windows directly.

If you want no installs beyond REAPER and Python, that’s where the dependency column in the table above earns its keep. Reaper Daemon needs nothing beyond the standard library. Everything else on this list needs at least the mcp package, and most need three or four more on top of it.

FAQ

What is the best REAPER MCP server?

There isn’t one best answer, there’s a best fit. Bonfire has the most analysis tools, total-reaper-mcp has the most REAPER functions exposed, dschuler36 is the simplest read-only source-file checker, and Reaper Daemon is the one with no pip dependencies and a single-call verification loop. Pick based on what you’re actually going to do with it, not the tool count in the README.

Do REAPER MCP servers need SWS or reapy?

Some do and some don’t. Bonfire and wegitor/reaper-reapy-mcp both run on python-reapy’s network bridge, so they need reapy working correctly. ReaAssist’s Cockos forum thread mentions SWS enabling loudness analysis, though that isn’t confirmed on ReaAssist’s own site. The file-bridge projects, Reaper Daemon, xDarkzx, TwelveTake, and total-reaper-mcp, don’t need either.

Can Claude control REAPER?

Yes, through any of the MCP servers or file bridges in this article. Claude Desktop and Claude Code can both talk to a stdio MCP server like reaper_mcp.py, and Claude Code, or any agent that can read and write files, can talk directly to a file bridge without MCP at all.

Is there a REAPER MCP server that measures loudness?

Several. Bonfire, dschuler36, xDarkzx, Phantom, and Reagent all measure LUFS in some form, and Reaper Daemon’s verify_change and tune_param measure it specifically before and after a mix move so you can see what a change actually did. TwelveTake’s public docs only show peak and peak-hold metering, no LUFS.