dschuler36/reaper-mcp-server

This is an MCP server that connects Reaper projects to an MCP client like Claude Desktop, enabling you to ask questions about your projects and get comprehensive audio analysis for mixing feedback.
This server is read-only by design. It exposes no tools that lets AI modify your project. What it's good for is understanding what you've already made and learning how to improve it. Let AI suggest some ideas and you can try tweaking the knobs and understand how it affects your music by doing.
Tools
Project Discovery & Parsing
- **find_reaper_projects**: Finds all Reaper projects in the directory you specified in the config.
- **parse_reaper_project**: Parses a Reaper project file (.RPP) and returns detailed information including tempo, tracks, FX chains, and audio items.
Each track carries its position and identity (track_number matching Reaper's display order, guid), its routing (is_folder/folder_depth, main_send, receives, num_channels, midi_hardware_out), and its mixer state (volume, pan, mute, solo). Each item carries position, length, start_offset, playrate, mute, fades, and every take — with the active take marked, since that is the one that plays.
receives entries name the source track by index and by name, which is what distinguishes a live signal path from a leftover track: a track with main_send: false does not reach the master, and its audio is only audible through whatever receives from it.
These tools work in tandem. When you ask Claude a question about a specific Reaper project, it will use the find_reaper_projects tool to find the project, then use the parse_reaper_project tool to parse the project and answer your question.
Installed FX Discovery
- **list_installed_fx(plugin_type=None, search_query=None)**: Lists all installed FX/plugins available in Reaper.
**Parameters:**
- plugin_type (optional): Filter by plugin type (VST2, VST3, AU, JS, CLAP)
- search_query (optional): Search plugins by name, manufacturer, or type
**Returns:** List of installed plugins including:
- Plugin name
- Plugin type (VST2, VST3, AU, JS, CLAP)
- File path
- Manufacturer (when available)
**Example Questions:**
- "What synth plugins do I have installed?"
- "Show me all my Waves plugins"
- "I'm looking for a warbly synth. What options do I have from my already installed plugins?"
- "List all my VST3 plugins"
- "Do I have any reverb plugins?"
- "What iZotope plugins do I have?"
- "Show me all my Audio Unit plugins"
**Note:** This tool scans your Reaper plugin cache files. If you recently installed new plugins and haven't scanned them in Reaper yet, they won't appear in the results. Make sure to open Reaper and let it scan for new plugins first.
Audio Analysis
- **analyze_audio_files(project_path, track_filter=None, whole_file=False)**: Analyzes the audio in a Reaper project for mixing feedback.
**Parameters:**
- project_path (required): Path to the .RPP project file. Must be inside --reaper-projects-dir.
- track_filter (optional): Filter tracks by name (e.g., "Vocal" to analyze only vocal tracks)
- whole_file (optional): Analyze entire source files instead of only the region each item plays. Off by default.
**Returns:** Comprehensive audio analysis including:
- **Level Analysis**: Peak levels, RMS, clipping detection, DC offset
- **Frequency Analysis**: Spectral centroid, and each band's share of total energy