Integrations
Enables repository cloning for installation of the MCP server, facilitating version control and distribution of the codebase
Hosts the repository for the REAPER MCP server, allowing users to access the codebase through the GitHub platform
Provides platform-specific support for running REAPER on macOS, with commands for launching the application specific to macOS environments
REAPER MCP Server
A comprehensive Model Context Protocol (MCP) server that enables AI agents to create fully mixed and mastered tracks in REAPER with both MIDI and audio capabilities.
Features
- Complete project management (creation, saving, rendering)
- Track operations (creation, routing, parameter adjustment)
- MIDI composition and editing
- Audio recording and importing
- Virtual instrument and effect management
- Mixing and automation
- Mastering tools
- Audio analysis and feedback
Requirements
- REAPER DAW installed
- Python 3.8+
- OSC support enabled in REAPER (for OSC mode)
- ReaScript API enabled in REAPER (for ReaScript mode)
Installation
Usage
Quick Start
The easiest way to get started is to use the provided startup script:
Windows Users
For Windows users, use one of the provided Windows scripts:
Configuration
By default, the server will use OSC mode, which is more reliable and doesn't require the ReaScript API to be working correctly. You can configure the server using command-line arguments:
Setting up REAPER for OSC
- Open REAPER
- Go to Preferences > Control/OSC/web
- Click "Add" and select "OSC (Open Sound Control)"
- Configure the following settings:
- Device name: ReaperMCP
- Mode: Local port
- Local listen port: 8000
- Local IP: 127.0.0.1 (or your computer's IP address)
- Allow binding messages to REAPER actions and FX learn: Checked (optional)
- Outgoing max packet size: 1024
- Wait between packets: 10ms
Setting up REAPER for ReaScript
- Open REAPER
- Go to Preferences > Plug-ins > ReaScript
- Make sure "Enable Python for ReaScript" is checked
- Set the Python DLL/dylib path to your Python installation
- On macOS:
/opt/homebrew/Cellar/python@3.x/3.x.x/Frameworks/Python.framework/Versions/3.x/Python
- On Windows:
C:\Path\to\Python\python3x.dll
- On macOS:
- Run the setup script:Copy
Project Structure
src/reaper_mcp/
: Main package directory__main__.py
: Command-line interfaceosc_server.py
: OSC-based server implementationserver.py
: ReaScript-based server implementation
examples/
: Example scripts demonstrating usagescripts/
: Utility scripts for setup and running
MCP Tools
The server provides the following MCP tools:
create_project
: Creates a new REAPER projectcreate_track
: Creates a new track in the current projectlist_tracks
: Lists all tracks in the current projectadd_midi_note
: Adds a MIDI note to a trackget_project_info
: Gets information about the current project
Troubleshooting
ReaScript API Issues
If you're experiencing issues with the ReaScript API, try using the OSC mode instead:
OSC Communication Issues
Make sure REAPER is configured correctly for OSC:
- Check that the OSC settings in REAPER match the server settings
- Verify that no firewall is blocking the communication
- Try using the local IP address (127.0.0.1) instead of a network IP
Windows-Specific Troubleshooting
If you're having issues running the MCP server on Windows:
- Script Execution Issues:
- For PowerShell scripts, you may need to adjust the execution policy:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
- Alternatively, use the
-ExecutionPolicy Bypass
flag as shown in the examples
- For PowerShell scripts, you may need to adjust the execution policy:
- Path Issues:
- Ensure the REAPER path in the scripts matches your installation location
- Default is
C:\Program Files\REAPER\reaper.exe
, modify if needed
- Virtual Environment:
- If you created the venv with a different method, the activation script might be in a different location
- Try activating manually before running:
venv\Scripts\activate
- Firewall Blocking:
- Windows Firewall may block OSC communication
- Add exceptions for Python and REAPER in Windows Firewall settings
- Administrator Rights:
- Try running the Command Prompt or PowerShell as Administrator if you encounter permission issues
License
MIT
This server cannot be installed
local-only server
The server can only run on the client's local machine because it depends on local resources.
A Model Context Protocol server that enables AI agents to create fully mixed and mastered tracks in REAPER DAW, supporting project management, MIDI composition, audio recording, and mixing automation.
Related MCP Servers
- -securityAlicense-qualityA Model Context Protocol server that provides seamless interaction with Workato's API through custom AI tools, enabling management of recipes, connections, connectors, folders, and activity logs.Last updated -TypeScriptMIT License
- -securityAlicense-qualityA Model Context Protocol server that enables AI assistants to interact with the Godot game engine, allowing them to launch the editor, run projects, capture debug output, and control project execution.Last updated -62JavaScriptMIT License
- -securityFlicense-qualityA Model Context Protocol server that enables role-based context management for AI agents, allowing users to establish specific instructions, maintain partitioned memory, and adapt tone for different agent roles in their system.Last updated -TypeScript
- -security-license-qualityA Model Context Protocol server that enables AI assistants like Claude to interact with DaVinci Resolve Studio, providing advanced control over editing, color grading, audio, and other video production tasks.Last updated -Python