REAPER MCP Server
Servidor REAPER MCP
Un servidor integral de Protocolo de Contexto de Modelo (MCP) que permite a los agentes de IA crear pistas totalmente mezcladas y masterizadas en REAPER con capacidades de audio y MIDI.
Características
Gestión completa del proyecto (creación, guardado, renderizado)
Operaciones de seguimiento (creación, enrutamiento, ajuste de parámetros)
Composición y edición MIDI
Grabación e importación de audio
Gestión de instrumentos y efectos virtuales
Mezcla y automatización
Dominando herramientas
Análisis y retroalimentación de audio
Related MCP server: REAPER MCP Server
Requisitos
REAPER DAW instalado
Python 3.8+
Soporte OSC habilitado en REAPER (para modo OSC)
API de ReaScript habilitada en REAPER (para el modo ReaScript)
Instalación
# Clone the repository
git clone https://github.com/itsuzef/reaper-mcp.git
cd reaper-mcp
# Create and activate a virtual environment
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
# Install the package
pip install -e .Uso
Inicio rápido
La forma más fácil de comenzar es utilizar el script de inicio proporcionado:
# Start REAPER first
open /Applications/REAPER.app # On macOS
# or start REAPER manually on other platforms
# Then start the MCP server
./scripts/start_reaper_mcp_server.sh # On Unix/MacUsuarios de Windows
Para los usuarios de Windows, utilice uno de los scripts de Windows proporcionados:
# Using Command Prompt (CMD)
scripts\start_reaper_mcp_server.bat
# Using PowerShell
powershell -ExecutionPolicy Bypass -File scripts\start_reaper_mcp_server.ps1Configuración
De forma predeterminada, el servidor usará el modo OSC, que es más fiable y no requiere que la API de ReaScript funcione correctamente. Puede configurar el servidor mediante argumentos de la línea de comandos:
# Start in OSC mode (default)
./scripts/start_reaper_mcp_server.sh --mode=osc # Unix/Mac
scripts\start_reaper_mcp_server.bat --mode=osc # Windows CMD
powershell -File scripts\start_reaper_mcp_server.ps1 -mode osc # Windows PowerShell
# Start in ReaScript mode
./scripts/start_reaper_mcp_server.sh --mode=reapy # Unix/Mac
scripts\start_reaper_mcp_server.bat --mode=reapy # Windows CMD
powershell -File scripts\start_reaper_mcp_server.ps1 -mode reapy # Windows PowerShell
# Configure OSC settings (Unix/Mac)
./scripts/start_reaper_mcp_server.sh --host=192.168.1.110 --send-port=8000 --receive-port=9000
# Configure OSC settings (Windows CMD)
scripts\start_reaper_mcp_server.bat --host=192.168.1.110 --send-port=8000 --receive-port=9000
# Configure OSC settings (Windows PowerShell)
powershell -File scripts\start_reaper_mcp_server.ps1 -host "192.168.1.110" -sendPort 8000 -receivePort 9000
# Enable debug logging
./scripts/start_reaper_mcp_server.sh --debug # Unix/Mac
scripts\start_reaper_mcp_server.bat --debug # Windows CMD
powershell -File scripts\start_reaper_mcp_server.ps1 -debug # Windows PowerShellConfiguración de REAPER para OSC
Abrir REAPER
Vaya a Preferencias > Control/OSC/web
Haga clic en "Agregar" y seleccione "OSC (Open Sound Control)"
Configure los siguientes ajustes:
Nombre del dispositivo: ReaperMCP
Modo: Puerto local
Puerto de escucha local: 8000
IP local: 127.0.0.1 (o la dirección IP de su computadora)
Permitir vincular mensajes a acciones REAPER y aprendizaje de FX: Marcado (opcional)
Tamaño máximo de paquete saliente: 1024
Espera entre paquetes: 10ms
Configuración de REAPER para ReaScript
Abrir REAPER
Vaya a Preferencias > Complementos > ReaScript
Asegúrese de que la opción "Habilitar Python para ReaScript" esté marcada
Establezca la ruta de la DLL/dylib de Python en su instalación de Python
En macOS:
/opt/homebrew/Cellar/python@3.x/3.xx/Frameworks/Python.framework/Versions/3.x/PythonEn Windows:
C:\Path\to\Python\python3x.dll
Ejecute el script de configuración:
python scripts/setup_reaper_python.py
Estructura del proyecto
src/reaper_mcp/: Directorio principal del paquete__main__.py: Interfaz de línea de comandososc_server.py: implementación de servidor basada en OSCserver.py: implementación de servidor basada en ReaScript
examples/: Scripts de ejemplo que demuestran el usoscripts/: Scripts de utilidad para configuración y ejecución
Herramientas MCP
El servidor proporciona las siguientes herramientas MCP:
create_project: Crea un nuevo proyecto REAPERcreate_track: Crea una nueva pista en el proyecto actuallist_tracks: enumera todas las pistas del proyecto actualadd_midi_note: Agrega una nota MIDI a una pistaget_project_info: Obtiene información sobre el proyecto actual
Solución de problemas
Problemas con la API de ReaScript
Si tiene problemas con la API de ReaScript, intente utilizar el modo OSC en su lugar:
./scripts/start_reaper_mcp_server.sh --mode=oscProblemas de comunicación de la OSC
Asegúrese de que REAPER esté configurado correctamente para OSC:
Compruebe que la configuración OSC en REAPER coincida con la configuración del servidor
Verifique que ningún firewall esté bloqueando la comunicación
Intente utilizar la dirección IP local (127.0.0.1) en lugar de una IP de red
Solución de problemas específicos de Windows
Si tiene problemas al ejecutar el servidor MCP en Windows:
Problemas de ejecución de scripts :
Para los scripts de PowerShell, es posible que deba ajustar la política de ejecución:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUserAlternativamente, utilice el indicador
-ExecutionPolicy Bypasscomo se muestra en los ejemplos
Problemas de ruta :
Asegúrese de que la ruta REAPER en los scripts coincida con su ubicación de instalación
El valor predeterminado es
C:\Program Files\REAPER\reaper.exe, modifíquelo si es necesario
Entorno virtual :
Si creó el venv con un método diferente, el script de activación podría estar en una ubicación diferente
Intente activarlo manualmente antes de ejecutar:
venv\Scripts\activate
Bloqueo de firewall :
El Firewall de Windows puede bloquear la comunicación OSC
Agregar excepciones para Python y REAPER en la configuración del Firewall de Windows
Derechos de administrador :
Intente ejecutar el Símbolo del sistema o PowerShell como administrador si encuentra problemas de permisos
Licencia
Instituto Tecnológico de Massachusetts (MIT)
Available Tools
61 toolsadd_fxB
Add an FX plugin to a track. Works for both instruments (VSTi) and effects (VST/AU). Use the exact plugin name as shown in REAPER's FX browser. Built-in Cockos plugins: ReaEQ, ReaComp, ReaDelay, ReaVerb, ReaLimit, ReaSynth, ReaSamplOmatic5000, ReaTune, ReaGate, ReaFIR, ReaXcomp.
Inputs: fx_name (required), track_index (required).
add_master_fxC
Add an FX plugin to the master track.
Inputs: fx_name (required).
add_midi_noteB
Add a MIDI note to an existing MIDI item. pitch: MIDI note number 0–127 (60 = middle C, 69 = A4). start/length: seconds, relative to the item's start. channel: MIDI channel 0–15 (use 9 for drums).
Inputs: pitch (required), start (required), length (required), item_index (required), +3 more.
add_pan_automationC
Add a pan automation point on a track, showing its pan envelope if needed. pan: -1.0 (full left) to 1.0 (full right).
Inputs: pan (required), position (required), track_index (required).
add_volume_automationB
Add a volume automation point on a track, showing its volume envelope if needed. position: time in seconds. value_db: volume level in dB.
Inputs: position (required), value_db (required), track_index (required).
adjust_pitchB
Adjust the pitch of an audio item by semitones (can be fractional).
Inputs: semitones (required), item_index (required), track_index (required).
adjust_playback_rateC
Adjust playback rate of an audio item. 1.0 = normal speed, 0.5 = half speed.
Inputs: rate (required), item_index (required), track_index (required).
analyze_dynamicsB
Render the project and measure dynamic range: RMS, peak, crest factor, and a simplified DR score (average peak-to-RMS over 3-second blocks).
Inputs: no named parameters.
analyze_frequency_spectrumA
Render the project and analyze frequency band levels. Returns RMS level in dB for seven bands: sub_bass (20–60Hz), bass (60–250Hz), low_mids (250–500Hz), mids (500–2kHz), high_mids (2–4kHz), presence (4–8kHz), brilliance (8–20kHz).
Inputs: no named parameters.
analyze_loudnessA
Render the project to a temp file and measure integrated loudness (LUFS) and true peak (dBTP) using the ITU-R BS.1770 standard.
Inputs: no named parameters.
analyze_stereo_fieldA
Render the project and analyze stereo width and mono compatibility. Returns mid/side balance, stereo width ratio, and L/R correlation. Correlation near 1 = mono-like, near 0 = wide stereo, negative = phase issues.
Inputs: no named parameters.
analyze_transientsA
Render the project and detect transient events (note attacks, drum hits, etc.). Returns the count and timing of up to 100 transient onset events.
Inputs: no named parameters.
apply_limiterB
Add ReaLimit to the master track and set its threshold and release. threshold_db: -60 to +12 dB. release_db_per_sec: how fast gain reduction recovers, in dB per second as ReaLimit displays it (about 6 and up; higher recovers faster; default 15).
Inputs: threshold_db, release_db_per_sec.
apply_mastering_chainA
Add a standard mastering FX chain to the master track. Presets: default (EQ > Comp > Limiter), loud (EQ > Comp x2 > Limiter), gentle (EQ > light Comp > Limiter). After applying, use set_master_fx_parameter to dial in specific settings. Use list_master_fx + get_fx_parameters to discover parameter indices.
Inputs: preset.
bypass_fxB
Enable or bypass (disable) an FX plugin on a track.
Inputs: bypassed (required), fx_index (required), track_index (required).
create_busB
Create a new bus track and route the given tracks to it via sends. track_indices: list of track indices to feed into the bus.
Inputs: name (required), track_indices (required).
create_chord_progressionC
Create a chord progression on a track as a single MIDI item. chords: comma-separated chord names, e.g. "C,G,Am,F" or "Cm7,Fm7,Bb7,Ebmaj7". Supports: maj, min/m, dim, aug, maj7, min7/m7, dom7/7, dim7, hdim7, sus2, sus4. All chords are voiced around middle C (MIDI 60).
Inputs: chords (required), track_index (required), start_position (required), beats_per_chord.
create_drum_patternA
Create a drum pattern on a track using a step-sequencer string. Each character = one step. Characters: k=kick, s=snare, h=hihat(closed), o=hihat(open), t=tom(low), m=tom(mid), f=tom(high), c=crash, r=ride, .=rest. Example 4/4 rock beat (16 steps): "k...h...s...h..." All drum notes are placed on MIDI channel 9 (GM standard).
Inputs: pattern (required), track_index (required), start_position (required), beats, +1 more.
create_midi_itemC
Create an empty MIDI item on a track. Returns item_id for use with add_midi_note.
Inputs: length (required), track_index (required), start_position (required).
create_projectA
Create a new REAPER project, in a new project tab, with the given tempo and time signature. The current project stays open, unsaved changes included.
Inputs: name, tempo, time_signature.
create_sendC
Create an aux send from one track to another.
Inputs: dest_track_index (required), source_track_index (required), volume_db.
create_trackC
Create a new track at the end of the project. track_type: audio, midi, instrument, folder
Inputs: name (required), track_type.
delete_trackC
Delete a track by its index.
Inputs: track_index (required).
detect_clippingA
Render the project and detect digital clipping (samples at or above 0 dBFS). Returns clipped sample count, peak level in dB, and whether clipping was found.
Inputs: no named parameters.
edit_audio_itemB
Trim an audio item and/or add fades. All values in seconds. start_trim: seconds to remove from the beginning. end_trim: seconds to remove from the end. fade_in/fade_out: fade length in seconds.
Inputs: item_index (required), track_index (required), fade_in, end_trim, +2 more.
get_fx_parametersB
Get all parameters for an FX plugin, including names, indices, and current values.
Inputs: fx_index (required), track_index (required).
get_project_infoA
Get information about the current project: name, path, tempo, tracks, length.
Inputs: no named parameters.
get_track_infoC
Get detailed information about a track including FX and items.
Inputs: track_index (required).
import_audio_fileC
Import an audio file onto a track at the given position (seconds). Supports all formats REAPER can read: wav, aiff, mp3, flac, ogg, etc.
Inputs: file_path (required), track_index (required), position.
insert_track_templateA
Insert a saved track template into the current project, exactly like REAPER's own "Insert track from template": FX with their saved state, routing, folder structure, envelopes and items are all preserved. Templates can contain several tracks. template: a name or path from list_track_templates ("Vocal Chain", "Vocals/Lead Vox"), or an absolute path to a .RTrackTemplate file. position: 0-based track index the template's first track should occupy. Existing tracks at that index and below are shifted down. Omit to append at the end. The inserted tracks are left selected, matching REAPER's behaviour.
Inputs: template (required), position.
list_master_fxB
List all FX plugins on the master track.
Inputs: no named parameters.
list_sendsB
List all sends from a track.
Inputs: track_index (required).
list_track_fxB
List all FX plugins on a track.
Inputs: track_index (required).
list_tracksB
List all tracks in the current project with their basic parameters.
Inputs: no named parameters.
list_track_templatesA
List the track templates (.RTrackTemplate files) in REAPER's TrackTemplates folder, including subfolders. Each entry has 'name' (file name without extension), 'path' (relative to the TrackTemplates folder, e.g. "Vocals/Lead Vox"), the absolute 'file', and the names of the tracks the template contains. Pass either 'name' or 'path' to insert_track_template.
Inputs: no named parameters.
load_fx_presetC
Load a saved preset by name for an FX plugin.
Inputs: fx_index (required), preset_name (required), track_index (required).
load_projectB
Load a REAPER project (.rpp) from the given file path.
Inputs: project_path (required).
normalize_projectA
Measure the project's integrated loudness, then adjust the master volume so the output hits the target LUFS level. Common targets: -14 LUFS (streaming), -16 LUFS (podcasts), -23 LUFS (broadcast).
Inputs: target_lufs.
play_projectA
Start project playback from the current cursor position.
Inputs: no named parameters.
remove_fxC
Remove an FX plugin from a track by its index.
Inputs: fx_index (required), track_index (required).
remove_sendC
Remove a send from a track by its index.
Inputs: send_index (required), source_track_index (required).
rename_trackC
Rename a track.
Inputs: name (required), track_index (required).
render_projectB
Render the entire project to a file. format: wav, flac, mp3 (requires LAME), ogg. sample_rate: e.g. 44100, 48000, 96000. bit_depth: 16, 24, or 32 (WAV only; ignored for mp3/ogg/flac). channels: 1 (mono) or 2 (stereo).
Inputs: output_path (required), format, channels, bit_depth, +1 more.
render_regionsA
Render each region of the project to its own file, using the project's render settings. pattern: file name pattern; $region, $regionnumber, $project are available, and it may name subdirectories. REAPER numbers names that would clash ("take-001", "take-002"). selected_only: render only the regions selected in REAPER; with none selected, REAPER renders all of them. dry_run: return the project's regions and the files REAPER would write, without rendering. It sets the render settings and restores them. Fails without rendering if any output file already exists; never deletes files. Blocks until every file is written; status is then "complete". Gives up with "stalled" once the files stop growing for stall_timeout_seconds (longer while REAPER holds a scratch file), or "timeout" after timeout_seconds in total. Region "index" is the position among regions, as in get_project_info.
Inputs: output_directory (required), dry_run, pattern, selected_only, +2 more.
render_stemsA
Render each track as a separate stem file by soloing each track individually. track_indices: list of track indices, or null to render all tracks. Files are named after the track names in the output directory.
Inputs: output_directory (required), format, bit_depth, sample_rate, +1 more.
render_time_selectionB
Render a specific time range of the project to a file.
Inputs: end (required), start (required), output_path (required), format, +3 more.
save_projectA
Save the current project. If no path is given, saves to ~/Documents/REAPER Projects.
Inputs: project_path.
set_cursor_positionA
Move the edit cursor to a position in seconds.
Inputs: position (required).
set_fx_parameterA
Set a normalized parameter value (0.0–1.0) on an FX plugin. Use get_fx_parameters to discover available parameters and their indices.
Inputs: value (required), fx_index (required), param_index (required), track_index (required).
set_master_fx_parameterC
Set a normalized parameter (0.0–1.0) on a master track FX plugin.
Inputs: value (required), fx_index (required), param_index (required).
set_master_volumeB
Set the master track output volume in dB.
Inputs: volume_db (required).
set_send_volumeC
Set the volume of a send in dB.
Inputs: volume_db (required), send_index (required), source_track_index (required).
set_tempoB
Set the project tempo in BPM.
Inputs: bpm (required).
set_time_signatureB
Set the project time signature, e.g. 4/4, 3/4, 6/8.
Inputs: numerator (required), denominator (required).
set_track_colorB
Set track color using RGB values (0–255 each).
Inputs: b (required), g (required), r (required), track_index (required).
set_track_muteC
Mute or unmute a track.
Inputs: muted (required), track_index (required).
set_track_panA
Set track pan. -1.0 = full left, 0.0 = center, 1.0 = full right.
Inputs: pan (required), track_index (required).
set_track_soloC
Solo or unsolo a track.
Inputs: soloed (required), track_index (required).
set_track_volumeC
Set track volume in dB. Range: roughly -150 to +12 dB.
Inputs: volume_db (required), track_index (required).
start_recordingB
Arm a track and start recording. Call stop_transport when done.
Inputs: track_index (required).
stop_transportA
Stop playback or recording.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 61 tools
Most tools target clearly distinct resources and actions, and the descriptions make the intended use clear. There is some subtle overlap among master-FX tools (add_master_fx, apply_mastering_chain, apply_limiter) and among rendering/analysis families, but these are generally distinguishable by scope and output.
Tool names consistently use snake_case verb_noun patterns such as create_track, set_track_volume, render_project, and analyze_loudness. The convention is predictable throughout, with no mixed casing or chaotic verb styles.
At 61 tools this is an extreme surface for one MCP server, well beyond the typical ergonomic range even for a broad DAW domain. Many operations could be consolidated or grouped to reduce selection burden.
Coverage is strong across project lifecycle, tracks, FX, MIDI, audio import/edit, automation, transport, rendering, templates, and analysis. Minor gaps remain around deeper item editing, such as deleting/moving/splitting existing items or more advanced MIDI editing.
Maintenance
Related MCP Connectors
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for Producer/Riffusion AI music generation
Compose, mix, master and export in Logic Pro, REAPER or Ableton Live by talking to an AI engineer.
Related MCP Servers
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables real-time interaction with Ableton Live, allowing AI assistants to control song creation, track management, clip operations, and audio recording workflows.2343 npm94MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that exposes REAPER digital audio workstation functionality through a clean API interface, enabling programmatic control of 169+ REAPER operations across track management, MIDI editing, effects, automation and more.91MIT
- AlicenseCqualityAmaintenanceA comprehensive MCP server that enables AI assistants to control REAPER DAW for mixing, mastering, MIDI composition, and full music production workflows with 130 tools.1871,166 PyPI114MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets language models interact with the Reaper DAW1MIT