A Lua daemon in REAPER connects track, routing, MIDI and transport operations to external clients. For Claude Code, 3 routes are explicitly documented by the integration maintainer.
A Lua daemon executes JSON file commands in REAPER, with results returned to a local agent or script.
Platforms: Windows, macOS, Linux
The maintainer documents Claude Code setup for this connection.
REAPER with the Lua daemon running and the external Python bridge configured.
The in-application daemon must be active; optional plugins and audio operations have additional prerequisites.
A ReaScript TCP bridge exposes REAPER project operations through MCP.
Platforms: Windows, macOS, Linux
The maintainer documents Claude Code setup for this connection.
REAPER with the companion TCP ReaScript bridge and the documented MCP server environment.
The bridge must be running inside REAPER; availability of individual FX depends on the local installation.
REAPER’s native ReaScript interface exposes application functions to scripts.
Platforms: Windows, macOS, Linux
The native interface is documented, but no setup for this coding agent is established by this source.
REAPER with a supported scripting environment; an external agent needs a script delivery or bridge mechanism.
This is an in-application scripting API, not an MCP server or a ready-made coding-agent setup.
REAPER can receive external control messages through its OSC control-surface interface.
Platforms: Windows, macOS, Linux
The native interface is documented, but no setup for this coding agent is established by this source.
REAPER configured with an OSC control surface and a compatible external OSC client.
Requires an OSC client or custom bridge. The documented protocol does not itself provide an AI-agent integration.
An optional stdio MCP wrapper exposes the REAPER Daemon file bridge as tools for MCP clients.
Platforms: Windows, macOS, Linux
The maintainer documents Claude Code setup for this connection.
REAPER with the Lua daemon running and the external Python bridge configured.
The in-application daemon must be active; optional plugins and audio operations have additional prerequisites.
An MCP server and Lua bridge operate the open REAPER project via local files.
Platforms: macOS, Windows, Linux
MCP support suggests compatibility; this client is not documented by the maintainer.
REAPER, Python 3.10 or newer and the REAPER bridge script.
The bridge uses a file mailbox; its previous HTTP transport was removed.
A Python MCP server connects to REAPER through its distant scripting API.
Platforms: Not documented
MCP support suggests compatibility; this client is not documented by the maintainer.
REAPER 7 or newer, Python 3.10 or newer and the REAPER distant API enabled.
The REAPER distant API must be enabled and REAPER restarted during setup.
| Integration | Claude Code compatibility | Requirements |
|---|---|---|
| REAPER Daemon · file bridge | Documented setup Setup guide | REAPER with the Lua daemon running and the external Python bridge configured. |
| REAPER MCP · TCP bridge | Documented setup Setup guide | REAPER with the companion TCP ReaScript bridge and the documented MCP server environment. |
| REAPER ReaScript | Not documented | REAPER with a supported scripting environment; an external agent needs a script delivery or bridge mechanism. |
| REAPER OSC | Not documented | REAPER configured with an OSC control surface and a compatible external OSC client. |
| REAPER Daemon · MCP | Documented setup Setup guide | REAPER with the Lua daemon running and the external Python bridge configured. |
| TwelveTake REAPER MCP | MCP compatibility (inferred) | REAPER, Python 3.10 or newer and the REAPER bridge script. |
| REAPER MCP · bonfire systems | MCP compatibility (inferred) | REAPER 7 or newer, Python 3.10 or newer and the REAPER distant API enabled. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Claude Code and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All REAPER integrations