Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@REAPER MCP List all tracks with volume, pan, mute and solo in the current project."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Control a local REAPER project from Codex or another MCP client through a native C++ extension and the official Python MCP SDK. Windows 10/11 x64 is the first target. No ReaScript installation, web server, audio upload, or Python installation is required when using the standalone Windows installer.
Status: 0.1.0-alpha.1. Automated Python, native and packaging tests are provided. Real REAPER + Codex + third-party plugin acceptance must still be verified on a Windows workstation. Do not treat this alpha as a production-certified DAW tool.
Releases · CI · Tool behavior and limitations · Troubleshooting
Install REAPER 7.80+ x64 and the Codex CLI. Open REAPER once, then close it.
Download the Windows x64 setup.exe from Releases and run it as your normal user.
Leave REAPER paths blank for automatic detection. For a portable copy, select its folder; select the resource directory too if it is customized.
Open REAPER and a saved test .rpp project. Open a new terminal and run:
reaper-mcp doctorRestart Codex and ask: “Liste todas as tracks do projeto aberto.”
Expected diagnosis: [OK] installation, [OK] codex, [OK] native-bridge, exit 0.
The answer should contain the project's actual track names and GUIDs. If diagnosis
fails, see Troubleshooting; do not troubleshoot sockets
or copy DLLs manually. A Start menu diagnostic shortcut is also installed.
The installer bundles the Python runtime, installs the native extension, creates
a private local token, and calls the official codex mcp add command. The alpha
installer is unsigned. No PyPI publication is currently claimed. For standalone
ZIP, source builds, security policy and other clients, see Installation.
Related MCP server: reaper-reapy-mcp
“Mostre o volume, pan, mute e solo de todas as tracks.”
“Reduza a track Voice em 3 dB e confirme o valor resultante.”
“Liste os plugins disponíveis antes de adicionar um efeito.”
“Desfaça a última alteração.” (Undo requires approval and can include manual edits.)
Use the supplied test project or a disposable copy for initial acceptance.
Area | Implemented in this alpha | Boundaries |
Projects | Inspect tabs/current project, save, native Undo/Redo | Save an existing path; Save As planned |
Tracks | List/get/create/delete/rename; dB, pan %, mute, solo | Normal tracks; use GUIDs for duplicate names |
Items and takes | List/get/split/move/trim/delete, gain/fades; inspect takes | Locked items rejected; source files never deleted |
Transport | Play/stop/pause, state and edit cursor | Read-only policy blocks changes |
FX | Discover installed plugins; add/remove/bypass; normalized parameters | Top-level normal track FX; plugin-dependent behavior |
Markers/regions | List/create/update/delete by persistent GUID | Requires modern REAPER API baseline |
Automation | Read envelopes; volume/pan base-point creation/update; point deletion | Existing envelopes only; no automation-item pools |
Render | Settings and isolated queued master-mix output | Experimental; nonempty output is not audio validation |
Environment | Versions, sample rates, resource paths, FX chains/templates discovery | Discovery only; preset application planned |
Administration | Install/uninstall, doctor/status/version/logs, official Codex registration |
|
Semantic mixing, LUFS/true-peak analysis, video, Linux/macOS/ARM runtime support, master/input/take FX and multi-instance selection are planned. See Roadmap for the acceptance gate before a stable release.
flowchart LR
C[Codex / MCP client] <-->|MCP stdio| P[Python MCP server]
P <-->|Authenticated loopback JSON-RPC| E[Native REAPER extension]
E <-->|Main-thread timer / official API| R[REAPER project]The native bridge binds only 127.0.0.1 on an ephemeral port. Requests require a
per-installation secret stored with private Windows ACLs. There is no arbitrary
shell, ReaScript, generic REAPER action, or remotely exposed HTTP endpoint. All
REAPER API access runs on its main thread. Requests are bounded and mutations are
never automatically retried after a timeout.
Default policy is confirm-destructive. Read-only and full-control are available.
confirm: true is the client's assertion that approval was obtained; it is not
proof of human consent. Use client approval controls and read-only when needed.
Undo covers supported project edits; saving, transport and rendering are not
transactional. Security explains the trust boundary.
python -m venv .venv
# Activate .venv using your shell, then:
python -m pip install -c packaging/constraints.txt -e ".[dev]"
ruff check src tests scripts
ruff format --check src tests scripts
mypy src
pytest -q
python -m buildNative build requires Windows x64, CMake and MSVC:
cmake -S reaper-extension -B build/extension -A x64
cmake --build build/extension --config Release
ctest --test-dir build/extension -C Release --output-on-failureMocks and synthetic installation fixtures are confined to tests. The CI builds on Linux/Windows with Python 3.11/3.14, tests native C++, then exercises the frozen executable, official Codex CLI registration and Setup installation/removal on Windows. Validation scope and acceptance testing distinguish these checks from a real REAPER session.
Architecture, protocol, ADRs, contributing, changelog, agent instructions, code of conduct.
MIT license for this project. Bundled dependencies retain their own licenses. REAPER is a separate product and is not redistributed. This is an independent community project, not an official Cockos or OpenAI product.
This server cannot be deployed
Create, co-edit, analyze, publish, and export collaborative step-sequencer sessions through MCP.
Log and read REPS time logs, properties, and categories via MCP. Requires REPSLog Premium.
MCP server for Producer/Riffusion AI music generation
Manage feature requests, votes, roadmaps, and changelogs from any MCP client.
