In the REAPER pages we read (the ReaScript page and the 7.81 user guide), we found scripting and automation, not a built-in chat assistant. In the user guide, "AI" means Automation Item. That is not proof no AI feature exists, so check the current release notes.

REAPER's scripting feature. Scripts are written in EEL2, Lua 5.4 or Python and can call REAPER actions and much of the API that compiled extensions use. It is the layer an AI bridge builds on.

How do I connect Claude or another AI client to REAPER?

Through a third-party bridge. One example, Reaper-MCP, installs a local MCP server and a Lua script that you load and run in REAPER, then you add the server to your MCP client's configuration. It is a community project, not made by REAPER's authors.

Can the AI undo what it did in REAPER?

REAPER's API offers undo blocks, so a script can make an action one undo step. Whether a given bridge tool does that is not stated in the README we read, so test it in a throwaway project and press undo after each request.

How do I get MIDI from REAPER into another DAW?

Use File, Export Project MIDI, choose the time range and which items to include, and pick a merged Type 0 file or a multitrack Type 1 file. For audio, use File, Render with the Stems (selected tracks) source.

AI in music software

REAPER and AI: ReaScript, MCP bridges and moving parts in and out

What REAPER documents for scripting, how a community MCP bridge connects an AI client, a careful throwaway-project setup, and how to move MIDI and stems.

By monody4 October 20266 min read

The short answer. REAPER's own documentation covers scripting, called ReaScript, not an assistant. Community projects connect an AI client to REAPER through that scripting layer. They run on your machine, and what they can change depends on the project's tools. Try one in a throwaway project, check undo after each request, and move parts to other DAWs with MIDI and stem files.

People searching "REAPER AI" mean different things: a plugin, a chat that controls REAPER, or help writing scripts. REAPER's scripting is documented and open, which is why it comes up when producers want to automate something. This guide separates the pieces and shows a careful first setup, taken from the documentation. We did not run the setup, so the steps below are what the docs say, not our test results.

Three different things

Route	What it is	Who makes it
ReaScript	Scripts in EEL2, Lua 5.4 or Python that call REAPER's API	REAPER, Cockos
An MCP bridge	A local server that lets an AI client call tools that drive REAPER, usually through a ReaScript	A third party, such as Reaper-MCP
A separate DAW with an assistant	Another application where the assistant is built in, such as monody	The DAW's maker

REAPER's ReaScript page explains that a script can trigger REAPER's built-in actions and call into much of the same API that compiled extensions use. It lists EEL2, Lua and Python, notes that Python must be installed separately, and warns that a script can still crash REAPER, so save important projects before you test one. The full API, including undo blocks (Undo_BeginBlock and Undo_EndBlock) and InsertMedia, is listed in the ReaScript documentation that REAPER generates from its Help menu.

One example bridge: Reaper-MCP

Reaper-MCP is an open-source project (Apache-2.0 on GitHub, last pushed 4 October 2026 when we looked). Its README, as we read it, says it connects any MCP client, including Claude Desktop, Claude Code and Cursor, to REAPER through "153 tools across 24 modules". The project's GitHub description already gives a larger number, so counts move with each release. It lists tools for transport, tracks, MIDI notes and CC, FX and parameters, envelopes, sends, mixing and measuring. The README says the server runs on your machine and talks to REAPER through files and a Lua script, with no network sockets.

That is the README's description. We haven't reviewed the code or run it. This is one of several. A GitHub search for "reaper mcp" on 4 October 2026 also returned bonfire-systems/reaper-mcp, TwelveTake-Studios/reaper-mcp, dschuler36/reaper-mcp-server and shiehn/total-reaper-mcp, each describing itself differently, with different tool lists and licenses. This guide uses one as an example, not as a recommendation, and we haven't compared them. Claude for music production lists another one's approach, through python-reapy. Bitwig and AI covers the same idea for Bitwig, where an extension runs inside the DAW.

A careful first setup

Do all of this in a project you do not care about.

Make a throwaway project. In REAPER, create a new project and save it somewhere disposable. Do not open a real session for the first test. Keep REAPER's own backups on.
Install the bridge. The README offers an installer (install.bat on Windows, bash install.sh on macOS and Linux) or a manual pip install -e . from the repo folder. Read the installer first. It can edit your Claude Desktop configuration.
Add it to your MCP client with the command reaper-mcp, as the README shows. For Claude Desktop the configuration file is under ~/Library/Application Support/Claude on macOS. Restart the client after editing.
Load the script in REAPER. Actions, Show action list, Load ReaScript, choose reaper_scripts/reaper_mcp_server.lua, then Run. The README says the script must be running for the bridge to work, and that the bridge cannot launch REAPER for you.
Give it instruments. The README says the bridge can create tracks and write MIDI but can't browse or install plug-ins, so put a synth on a track yourself first.
Start small. Ask for one thing at a time:
- "Set the tempo to 100 BPM."
- "Add a track called Test Bass and write a four-note line on it."
- "Add ReaEQ to that track and cut below 60 Hz."
Press undo after each request. Look at the undo label in REAPER's Edit menu, undo once, and see whether the whole request went away or only part of it.

What to check before you trust it

Question	Why it matters	How to test it
Is one request one undo step?	REAPER's API lets a script group edits into one step, but a tool may not use it	Run a request that adds a track, a note and an effect, then undo once
Does it touch only what you asked?	A broad tool can change many tracks	Save a copy first, then diff by listening and by looking at the track list
Does it use your plug-ins or a default?	The README says it picks the best available EQ and compressor it detects	Ask which plug-in it added before you accept it
What leaves the machine?	The bridge is local, but your AI client sends your messages and what the tools return to its provider	Read your client's data policy, and keep client names and unreleased audio out of prompts
Does a mix tool replace your settings?	The README describes "mix" and "master" tools with style profiles	Use these only on a copy, and compare before and after by ear

Taking parts in and out of REAPER

MIDI and stems are the usual way to move work in and out of REAPER, as long as the other DAW reads them, and REAPER's user guide covers both.

MIDI out. File, Export Project MIDI. You choose the entire project or the time selection, all media items, selected tracks or selected items, and whether to merge to a single-track Type 0 file or keep tracks in a Type 1 file.
MIDI in. Drag a .mid onto the arrange view or use Insert, Media file. For a Type 1 file REAPER asks whether to expand the tracks and whether to import the tempo map, then offers multichannel items on one track or single-channel items on several tracks.
Stems out. File, Render, with the Source set to Stems (selected tracks). The guide says this applies the track FX and envelopes, unlike consolidating.
Whole projects. REAPER is not on the DAWproject support list in the format's repository, which names a third-party converter, ProjectConverter, for REAPER. We haven't tried it. DAWproject, MIDI and stems explains what a project bridge can and can't carry.

For the steps in other DAWs, see Move MIDI and stems between DAWs. A part written in monody leaves as a .mid, so it can be imported into REAPER the same way. AI basslines you can edit walks through one example. monody doesn't open REAPER project files.

If you don't want to build the bridge

An assistant built into a DAW needs no bridge, and a DAW that is itself an MCP server needs no script. monody's MCP page describes the second case for monody only. It is not a REAPER setup, and the two shouldn't be confused. If your DAW is REAPER and you want to stay in it, ReaScript, written by you or by an AI coding assistant and read before you run it, is the documented path.

Sources

REAPER: ReaScript, ReaScript API documentation, User Guide 7.81 (media import, Export Project MIDI, Render stems)
Reaper-MCP: repository and README
DAWproject: format repository (support list and converters)

Checked on 4 October 2026. We did not run the setup in this guide.

Questions

Does REAPER have AI?: In the REAPER pages we read (the ReaScript page and the 7.81 user guide), we found scripting and automation, not a built-in chat assistant. In the user guide, "AI" means Automation Item. That is not proof no AI feature exists, so check the current release notes.
What is ReaScript?: REAPER's scripting feature. Scripts are written in EEL2, Lua 5.4 or Python and can call REAPER actions and much of the API that compiled extensions use. It is the layer an AI bridge builds on.
How do I connect Claude or another AI client to REAPER?: Through a third-party bridge. One example, Reaper-MCP, installs a local MCP server and a Lua script that you load and run in REAPER, then you add the server to your MCP client's configuration. It is a community project, not made by REAPER's authors.
Can the AI undo what it did in REAPER?: REAPER's API offers undo blocks, so a script can make an action one undo step. Whether a given bridge tool does that is not stated in the README we read, so test it in a throwaway project and press undo after each request.
How do I get MIDI from REAPER into another DAW?: Use File, Export Project MIDI, choose the time range and which items to include, and pick a merged Type 0 file or a multitrack Type 1 file. For audio, use File, Render with the Stems (selected tracks) source.