Reaper DAW MCP Server with 100% Reascript Coverage
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"total-reaper-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP (Model Context Protocol) server that exposes REAPER DAW functionality through a clean API interface.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in entertainment
MCP Security Weekly
Get CVE alerts and security updates for Total Reaper Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server that exposes REAPER DAW functionality through a clean API interface.

This project is developed and tested on macOS but should work on Windows and Linux with minimal adaptation, as REAPER provides consistent cross-platform support.
This project uses a hybrid Lua-Python approach:
The communication flow:
# Start with default profile (dsl-production: 53 tools)
# Includes natural language DSL + essential production tools
python -m server.app
# Or choose a specific profile:
python -m server.app --profile dsl # Minimal natural language only (15 tools)
python -m server.app --profile groq-essential # Traditional ReaScript tools (146 tools)
python -m server.app --profile full # All tools (600+ tools)
The default dsl-production profile is optimized for AI/LLM use, providing natural language commands plus essential MIDI, FX, and rendering tools.
./scripts/install.sh
This will:
Note: The quick install script is macOS-only. Windows users must follow the manual setup below.
macOS / Linux:
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
Windows (recommended — using uv):
uv venv --python 3.11
source .venv/Scripts/activate # Git Bash
# or: .venv\Scripts\activate.bat (CMD) / .venv\Scripts\Activate.ps1 (PowerShell)
uv pip install -e .
Windows (standard venv):
python -m venv .venv
.venv\Scripts\activate.bat # CMD
# or: .venv\Scripts\Activate.ps1 (PowerShell)
pip install -e .
Currently, only the file-based bridge is fully implemented and tested. The socket-based bridge exists but lacks a corresponding server implementation.
The MCP server communicates with REAPER through a file-based bridge. This requires no additional dependencies and is the most reliable method.
macOS / Linux:
./scripts/install_bridge.sh
Windows:
The install script is macOS-only. Copy the bridge manually:
# Git Bash
cp lua/mcp_bridge.lua "$APPDATA/REAPER/Scripts/"
Or in PowerShell:
Copy-Item lua\mcp_bridge.lua "$env:APPDATA\REAPER\Scripts\"
The bridge is copied as mcp_bridge.lua. REAPER's Scripts folder is typically:
C:\Users\<you>\AppData\Roaming\REAPER\Scripts\
Load the bridge in REAPER (all platforms):
mcp_bridge.lua (Windows) or mcp_bridge_file_v2.lua (macOS)
C:\Users\<you>\AppData\Roaming\REAPER\Scripts\