Skip to content
Back to search

reaper-mcp-server

An MCP Server for interacting with Reaper projects.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dschuler36--reaper-mcp-server/badge.svg)](/listings/dschuler36--reaper-mcp-server)

HTML

<a href="/listings/dschuler36--reaper-mcp-server"><img src="/api/listings/dschuler36--reaper-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You need [uv](https://docs.astral.sh/uv/getting-started/installation/) installed. You do **not** need to clone this repo or create a virtualenv — `uvx` fetches, builds, and runs the server for you, and it manages its own Python.

1. Configure Claude Desktop

Follow [the instructions to configure Claude Desktop](https://modelcontextprotocol.io/quickstart/server#core-mcp-concepts) for a custom MCP server, then use the sample in `setup/claude_desktop_config.json`:

{
    "mcpServers": {
        "reaper": {
            "command": "/path/to/your/uv-installation/uvx",
            "args": [
                "--from",
                "git+https://github.com/dschuler36/reaper-mcp-server",
                "reaper-mcp-server",
                "--reaper-projects-dir",
                "/path/to/your/reaper/projects"
            ]
        }
    }
}

Two paths to fill in:

- **`uvx`** — use the absolute path, not bare `uvx`. Claude Desktop does not inherit your shell's `PATH`, so a bare command name will fail to launch. Run `which uvx` to find it (typically `~/.local/bin/uvx`). - **`--reaper-projects-dir`** — the directory holding your Reaper projects.

To pick up new commits later, run `uvx --refresh --from git+https://github.com/dschuler36/reaper-mcp-server reaper-mcp-server --help` once, or restart Claude Desktop after clearing the uv cache.

Using Claude Code instead

claude mcp add reaper -- \
  uvx --from git+https://github.com/dschuler36/reaper-mcp-server \
  reaper-mcp-server --reaper-projects-dir /path/to/your/reaper/projects

2. Launch and Configure

- Open Claude Desktop - Click the '+' icon on the chat box - Click on 'Connectors' and you should see the 'reaper' connector enabled

3. Ask Away!

- Ask questions about your Reaper project - Always include the name of the specific Reaper project you're asking about - You can expand the tool boxes to see the raw project data being passed to Claude

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 171 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Reaper MCP Server
  2. 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.
  3. 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.
  4. ## Tools
  5. ### Project Discovery & Parsing
  6. - **`find_reaper_projects`**: Finds all Reaper projects in the directory you specified in the config.
  7. - **`parse_reaper_project`**: Parses a Reaper project file (.RPP) and returns detailed information including tempo, tracks, FX chains, and audio items.
  8. 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.
  9. `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.
  10. 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.
  11. ### Installed FX Discovery
  12. - **`list_installed_fx(plugin_type=None, search_query=None)`**: Lists all installed FX/plugins available in Reaper.
  13. **Parameters:**
  14. - `plugin_type` (optional): Filter by plugin type (VST2, VST3, AU, JS, CLAP)
  15. - `search_query` (optional): Search plugins by name, manufacturer, or type
  16. **Returns:** List of installed plugins including:
  17. - Plugin name
  18. - Plugin type (VST2, VST3, AU, JS, CLAP)
  19. - File path
  20. - Manufacturer (when available)
  21. **Example Questions:**
  22. - "What synth plugins do I have installed?"
  23. - "Show me all my Waves plugins"
  24. - "I'm looking for a warbly synth. What options do I have from my already installed plugins?"
  25. - "List all my VST3 plugins"
  26. - "Do I have any reverb plugins?"
  27. - "What iZotope plugins do I have?"
  28. - "Show me all my Audio Unit plugins"
  29. **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.
  30. ### Audio Analysis
  31. - **`analyze_audio_files(project_path, track_filter=None, whole_file=False)`**: Analyzes the audio in a Reaper project for mixing feedback.
  32. **Parameters:**
  33. - `project_path` (required): Path to the .RPP project file. Must be inside `--reaper-projects-dir`.
  34. - `track_filter` (optional): Filter tracks by name (e.g., "Vocal" to analyze only vocal tracks)
  35. - `whole_file` (optional): Analyze entire source files instead of only the region each item plays. Off by default.
  36. **Returns:** Comprehensive audio analysis including:
  37. - **Level Analysis**: Peak levels, RMS, clipping detection, DC offset
  38. - **Frequency Analysis**: Spectral centroid, and each band's share of total energy
  39. - **Stereo Imaging**: Stereo width, phase coherence, mono compatibility
  40. - **Dynamic Range & Loudness**: LUFS (loudness standards), true peak, crest factor
  41. **Example Questions:**
  42. - "Analyze all audio in my Rock Song project"
  43. - "Check the vocal tracks for clipping"
  44. - "Is my mix too loud for streaming platforms?"
  45. - "Are there any phase issues in my drum tracks?"
  46. **What is measured:** By default each item is analyzed over exactly the region it plays — its source start offset, length, and playrate — not its whole source file. Distinct regions are analyzed once and reused, so an item repeated across the arrangement costs one measurement. MIDI items have no audio source and are listed under `skipped` rather than reported as errors.
  47. **Frequency figures are relative.** Each band is reported as a share of that region's total spectral power (and the same share in dB). Absolute band energy scales with clip length, which makes a long file look tens of dB "hotter" than a short one of identical material and makes cross-file comparison meaningless.
  48. **These numbers are pre-FX.** Analysis reads the source files from disk, so it reflects neither the track's FX chain nor its fader. On a track running an amp sim or heavy EQ, the analysis describes the raw DI, not what you hear. Every response is labelled `signal_stage: pre-fx`.
  49. **Warning Thresholds:**
  50. - Peak > -0.3 dBFS: Risk of clipping
  51. - Clipping detected: Digital distortion present
  52. - 200–500 Hz more than 10 dB above 500–2000 Hz: Boxy low mids. Comparing these two bands to each other, rather than one band against the whole spectrum, is what keeps a bass part from being flagged simply for being a bass.
  53. - Mean sample value > 0.001: DC offset
  54. - Phase coherence < 0.5: Phase cancellation issues
  55. - LUFS > -8: Too loud for streaming (Spotify target: -14 LUFS)
  56. - Crest factor < 6 dB: Possibly over-compressed
  57. Loudness is reported as `null` rather than a stand-in value when it cannot be measured (regions shorter than 400 ms), and regions under 50 ms are measured but not warned about.
  58. To see all data structures parsed from projects, check out the `src/reaper_mcp_server/reaper_dataclasses.py` file.
  59. ## Setup
  60. You need [uv](https://docs.astral.sh/uv/getting-started/installation/) installed. You do **not** need to clone this repo or create a virtualenv — `uvx` fetches, builds, and runs the server for you, and it manages its own Python.
  61. ### 1. Configure Claude Desktop
  62. Follow [the instructions to configure Claude Desktop](https://modelcontextprotocol.io/quickstart/server#core-mcp-concepts) for a custom MCP server, then use the sample in `setup/claude_desktop_config.json`:
  63. ```json
  64. {
  65. "mcpServers": {
  66. "reaper": {
  67. "command": "/path/to/your/uv-installation/uvx",
  68. "args": [
  69. "--from",
  70. "git+https://github.com/dschuler36/reaper-mcp-server",
  71. "reaper-mcp-server",
  72. "--reaper-projects-dir",
  73. "/path/to/your/reaper/projects"
  74. ]
  75. }
  76. }
  77. }
  78. ```
  79. Two paths to fill in:
  80. - **`uvx`** — use the absolute path, not bare `uvx`. Claude Desktop does not inherit your shell's `PATH`, so a bare command name will fail to launch. Run `which uvx` to find it (typically `~/.local/bin/uvx`).
  81. - **`--reaper-projects-dir`** — the directory holding your Reaper projects. The server only opens `.RPP` files inside it.
  82. To pick up new commits later, run `uvx --refresh --from git+https://github.com/dschuler36/reaper-mcp-server reaper-mcp-server --help` once, or restart Claude Desktop after clearing the uv cache.
  83. ### Using Claude Code instead
  84. ```bash
  85. claude mcp add reaper -- \
  86. uvx --from git+https://github.com/dschuler36/reaper-mcp-server \
  87. reaper-mcp-server --reaper-projects-dir /path/to/your/reaper/projects
  88. ```
  89. ### 2. Launch and Configure
  90. - Open Claude Desktop
  91. - Click the '+' icon on the chat box
  92. - Click on 'Connectors' and you should see the 'reaper' connector enabled
  93. ![Claude Desktop Connectors](./docs/claude-desktop-connectors.png)
  94. ### 3. Ask Away!
  95. - Ask questions about your Reaper project
  96. - Always include the name of the specific Reaper project you're asking about
  97. - You can expand the tool boxes to see the raw project data being passed to Claude
  98. ![Claude Desktop Tools](./docs/example-question.png)
  99. ## Running from a clone
  100. If you want to modify the server, clone it and point Claude at your working copy. `uv run` syncs the locked dependencies on every launch, so there is no separate install step:
  101. ```bash
  102. git clone https://github.com/dschuler36/reaper-mcp-server
  103. cd reaper-mcp-server
  104. uv sync # optional — only needed for running tests
  105. uv run --group dev pytest
  106. ```
  107. Then use `setup/claude_desktop_config_local.json`, which runs the server out of your clone:
  108. ```json
  109. {
  110. "mcpServers": {
  111. "reaper": {
  112. "command": "/path/to/your/uv-installation/uv",
  113. "args": [
  114. "--directory",
  115. "/path/to/this/repo/reaper-mcp-server/",
  116. "run",
  117. "reaper-mcp-server",
  118. "--reaper-projects-dir",
  119. "/path/to/your/reaper/projects"
  120. ]
  121. }
  122. }
  123. }
  124. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.