About REAPER MCP Server
REAPER MCP Server connects AI agents to REAPER 7 or later for DAW project work, from MIDI and audio editing to mixing, mastering, rendering, and analysis. It offers tools across these stages and uses REAPER’s distant API.
Key features
- 01Project and track management
- 02MIDI creation and editing
- 03FX and instrument control
- 04Audio editing and mixing
- 05Rendering and mastering
- 06Loudness and audio analysis
Use cases
- 01Build a project with tracks and MIDI parts
- 02Adjust FX, levels, and track routing
- 03Render a mix or separate stems
- 04Check loudness, dynamics, and clipping
MCP support
It exposes REAPER project, track, MIDI, audio, mixing, rendering, mastering, and analysis operations as tools for MCP clients. Communication with REAPER uses its distant API.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEREAPER MCP Server
A Model Context Protocol (MCP) server that enables AI agents to control REAPER DAW — 61 tools covering project management, tracks, track templates, MIDI, FX, mixing, mastering, rendering, and audio analysis.
Requirements
Installation
pip install reaper-mcp-server
Or install from source:
git clone https://github.com/bonfire-systems/reaper-mcp.git
cd reaper-mcp
pip install -e .
Setting Up REAPER
The server communicates with REAPER via python-reapy, which requires REAPER's distant API to be enabled.
- Open REAPER
- Go to Actions > Run ReaScript
- Select
scripts/enable_reapy.pyfrom this repo (or create a new script with the contents below)import reapy reapy.config.enable_dist_api() - Restart REAPER
Usage
With Claude Desktop
Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"reaper": {
"command": "reaper-mcp-server",
"args": []
}
}
}
With Claude Code
claude mcp add reaper -- reaper-mcp-server
Standalone
reaper-mcp-server # start the server
reaper-mcp-server --debug # with debug logging
Tools (60)
Project Management
create_project load_project save_project get_project_info set_tempo set_time_signature set_cursor_position play_project stop_transport
Tracks
create_track delete_track rename_track list_tracks get_track_info set_track_color create_bus create_send remove_send list_sends
Track Templates
list_track_templates insert_track_template
Inserts saved .RTrackTemplate files from REAPER's TrackTemplates folder (subfolders included) with their exact FX state, routing, folder structure and items, optionally at a given track position.
MIDI
create_midi_item add_midi_note create_chord_progression create_drum_pattern
FX & Instruments
add_fx remove_fx bypass_fx list_track_fx get_fx_parameters set_fx_parameter load_fx_preset add_master_fx list_master_fx set_master_fx_parameter
Audio
import_audio_file edit_audio_item start_recording adjust_pitch adjust_playback_rate
Mixing
set_track_volume set_track_pan set_track_mute set_track_solo set_send_volume set_master_volume add_volume_automation add_pan_automation
Rendering
render_project render_stems render_time_selection render_regions
Mastering
apply_mastering_chain apply_limiter normalize_project
Analysis
analyze_loudness analyze_dynamics analyze_frequency_spectrum analyze_stereo_field analyze_transients detect_clipping
Contributing
See CONTRIBUTING.md. In short: one concern per pull request, tested against a real REAPER (say which version), and an issue first for new tools.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.