MCP server for controlling REAPER DAW with AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"reaper-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# REAPER 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 - [REAPER](https://www.reaper.fm/) 7 or later, installed and running - Python 3.10+ - REAPER's distant API enabled (see [Setup](#setting-up-reaper)) ## Installation ```bash pip install reaper-mcp-server ``` Or install from source: ```bash 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](https://github.com/RomeoDespres/reapy), which requires REAPER's distant API to be enabled. 1. Open REAPER 2. Go to Actions > Run ReaScript 3. Select `scripts/enable_reapy.py` from this repo (or create a new script with the contents below) ```python import reapy reapy.config.enable_dist_api() ``` 4. Restart REAPER ## Usage ### With Claude Desktop Add to your Claude Desktop config (`claude_desktop_config.json`): ```json { "mcpServers": { "reaper": { "command": "reaper-mcp-server", "args": [] } } } ``` ### With Claude Code ```bash claude mcp add reaper -- reaper-mcp-server ``` ### Standalone ```bash 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, optional…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.