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
The official MCP Server for the Mux API
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
A Model Context Protocol (MCP) server that gives Claude direct control over Strudel.cc for AI-assisted music generation and live coding.
Unreal Engine MCP server — 19 tools, 300+ actions for AI-driven editor control
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 may reference outdated configurations. For the most reliable setup, follow the manual instructions below.
# Create and activate virtual environment (Python 3.10+ required)
python3.10 -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
# Install the package
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.
Install the bridge:
./scripts/install_bridge.sh
Load the bridge in REAPER:
mcp_bridge_file_v2.lua from your Scripts folderStart the MCP server:
# Default profile (dsl-production: 53 tools with natural language interface)
python -m server.app
# Or with a specific profile
python -m server.app --profile dsl # Natural language tools only (15 tools)
python -m server.app --profile full # All tools (600+ tools)
Important Architecture Note:
lua/mcp_bridge.lua) that supports ALL profilesmcp_bridge_file_v2.lua for backward compatibilityWhile the Lua script lua/mcp_bridge.lua exists for socket-based communication, there is no corresponding Python serve