REAPER MCP server: what an agent can actually do

Published October 2026

Doseedo runs a hosted MCP server at https://api.doseedo.com/mcp that gives an AI agent file-level access to REAPER projects: open an .rpp as an editable session, convert it to or from Logic Pro, Ableton Live, FL Studio, Pro Tools and five more formats, read what is inside one, and hand you back a project REAPER opens. REAPER is also the one DAW whose project format is plain text, which makes it the agent's favourite intermediate for restructuring any other DAW's project. What this server does not do is drive the REAPER window that is open on your screen — that is ReaScript's job, and the community MCP servers built on it. This page keeps the two apart.

Two different things called "REAPER MCP"

The phrase "REAPER MCP" names two unrelated capabilities, and mixing them up is how people end up disappointed:

• Realtime control of a running REAPER. REAPER ships the most complete scripting surface of any DAW: ReaScript in Lua, EEL2 and Python, with thousands of API functions over tracks, items, envelopes, FX and the transport, plus OSC and the SWS extension. Several open-source MCP servers sit on that API — they run on the machine with REAPER open and let an agent add tracks, insert FX and move the playhead live. Nothing here replaces them; if that is the job, pick one of those.
• Agent access to the project itself. Reading an .rpp, converting it, importing it as an editable session, building a new project, downloading the result. That is a file-level problem: it works with REAPER closed, from a phone, on a server without REAPER installed. It is what the Doseedo MCP server does.

The two combine well. ReaScript never reads a Logic project; a file-level tool never sees your playhead. Convert and restructure with one, perform and mix with the other.

Setup

claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp

That line is for Claude Code; the first tool call opens a browser to sign in and approve. The same URL installs in ChatGPT, Cursor, Gemini CLI, Codex, VS Code and the Claude phone and web apps — one page per client in the block below. Headless clients send X-API-Key: dsk_live_… from Settings → API keys instead of the browser. Nothing to self-host; the full tool reference lists all 33 tools.

What the agent can do with a REAPER project

You talk to it in project terms; it handles uploads, polling and downloads itself:

> Convert ~/Projects/live-set.rpp to Ableton, and tell me
  what won't survive the trip.

> Open this .rpp as a session, list the tracks and every
  FX on them, then mute everything but the drums and
  give me the project back.

> This Logic project has 40 unnamed tracks. Take it through
  REAPER's text format, name them from what's on each one,
  and bring it back as .logicx.

Concretely, the capabilities that apply to REAPER:

• Import an .rpp as an editable session. doseedo_import_project reads the project — tracks, items, MIDI, FX chains with their state, envelopes, sends — into a session the agent then edits with the same ops it uses on a Logic project: regions, notes, faders, plugins, tempo, markers, buses. Download the result as a native Logic project, or convert it back to .rpp.
• Convert, natively. REAPER to and from Logic Pro, Ableton Live, FL Studio, Pro Tools, Cubase, Dorico, Studio One and Bitwig, and GarageBand in — part of the 75 directions. The REAPER pairs with Logic and Ableton carry VST, VST3 and AU plugin state, envelopes and sends, with the stock plugins mapped (ReaEQ to Channel EQ and back); see what carries over, field by field.
• Read a project with REAPER closed. An .rpp is text, so an agent answers "what's in here?" directly — tracks, items, FX, referenced media — and the browser .rpp player shows the same on a page.
• Use REAPER as the text intermediate. Any other DAW's project converts to .rpp, where renaming, reordering and deleting are text edits an agent is good at, then converts back. Structural work survives the round trip; a week of fine automation is the kind of thing to check in the breakdown first.
• Build a project from a mix. doseedo_audio_to_session targets Logic and Ableton; for REAPER the agent builds one of those and converts — the stems, tempo map and MIDI survive the hop.

Long jobs follow one shape everywhere: the submit tool returns a job_id, doseedo_wait_task polls it server-side (one call holds at most 50 seconds, so the agent calls again while it is still running), and the result arrives as pre-signed download links that work with a plain curl for 24 hours — no key on the download. Those links are reusable as the input of the next tool, so a separated stem feeds the transcriber and a generated take lands on a session track without a round trip through your disk.

What it does not do — read this before you install

• No live control of a running REAPER. No transport, no live FX tweaks, no reading the project REAPER has open right now. That is ReaScript, OSC, and the MCP servers built on them.
• Live session editing targets Logic Pro today. The agent-edits-your-open-project half of this product runs through the Dø Desktop bridge on macOS, and Logic is the DAW it drives. A REAPER project is edited as a session and handed back as a file.
• Offline bounce is Logic-side too. Printing tracks through their real plugin chains with the DAW closed runs through that same bridge.
• No one-shot .rpp session download. Saving a session directly as a native file targets Logic; REAPER is reached by converting from it — one extra call, which the agent makes for you.

Scope, stated once. Live editing — an agent's change landing in the project that is open on your screen — and the offline bounce target Logic Pro on macOS, through the Dø Desktop bridge. Reading, building, converting and downloading projects cover Logic Pro, Ableton Live, FL Studio, Pro Tools and REAPER, and conversion covers ten DAW formats (those five plus Cubase, Dorico, Studio One, Bitwig, and GarageBand in) in all 75 directions. Nothing here drives a transport or moves a playhead: the agent edits the session, not the console.

Why REAPER is a file surface here and Logic is a live one

Because the gaps are in opposite places. Logic ships no public realtime scripting API — Scripter is JavaScript confined to one channel strip — so the only way to reach an open Logic project is a native bridge, which is what the desktop app is (the Logic side, in detail). REAPER has the opposite problem: it is the most scriptable DAW there is, and realtime control was solved by ReaScript years ago. What REAPER did not have was a way to get a project out and into another DAW with the arrangement intact, or to take a Logic, Ableton or Pro Tools project in — that is the part this fills.

Which tool for which job

• Drive the REAPER that is open right now: ReaScript (Lua, EEL2, Python), OSC, or a ReaScript-based MCP server.
• Move a project between REAPER and another DAW, either direction: the Doseedo MCP server.
• Restructure any DAW's project as text: convert to .rpp through the MCP server, edit, convert back.
• Have an agent edit an open project as you watch: Logic Pro, with Dø Desktop running.

Related

• What is an .rpp file
• Open an .rpp in the browser
• Convert REAPER to Logic
• Convert REAPER to Ableton
• Control Logic Pro with Python
• What carries over between DAWs