§ Guide · For developers & agents

Edit Logic and Ableton projects with Claude

Published August 2026 · Updated September 2026

Yes — Claude can edit your DAW project, and not only by handing you a new file. Connect one MCP server and it can list the sessions in your account, read one as a full arrangement, and change it: move a region, rewrite the MIDI, pull a fader down, insert a plugin by name. With the Doseedo desktop app running on your Mac, those edits land in the Logic Pro project open in front of you, within seconds. With it closed they persist and bake in when the session next opens. Reading, building, converting and downloading cover Logic Pro, Ableton Live, FL Studio, Pro Tools and REAPER; the live editing described here targets Logic Pro today.

Setup: one command

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

The first tool call opens a browser; sign in to Doseedo and approve. For a headless client, append --header "X-API-Key: dsk_live_..." with a key from Settings → API keys. The same URL installs as a custom connector in the Claude phone and web apps (Settings → Connectors → Add custom connector), in Claude Desktop, in Cursor, and in any client that speaks Streamable HTTP MCP. There are 21 tools behind that one endpoint; the full reference is on the MCP server page. Nothing runs locally for the MCP itself, and calls meter like using the site — same account, quotas and credits, revocable per client.

What Claude sees when it reads a session

A session read is not a file dump. It arrives as an arrangement an agent can reason about:

What Claude can change

The edit surface is a list of operations applied to that arrangement: move and trim regions, rewrite MIDI notes, add and delete tracks, set faders, pan and mute, insert plugins by name, change tempo, add markers, create submix buses and route tracks into them, load samples into Quick Sampler. In practice you name none of that; you say what you want:

> List my sessions.

> Read "luckbe" — what's on track 4, and how long is
  the intro?

> In luckbe: shorten the intro by 4 bars, bring the sax
  in at bar 17 instead of 25, and pull the vocal up 2 dB.

> Add a submix bus called DRUMS, route the kick, snare
  and overheads into it, and put a compressor on it.

> Bounce the guitar tracks through their plugin chains
  and give me the stems.

How an edit reaches the project on your desk

Logic Pro has no scripting API, which is why "control your DAW with AI" was for years a description of nothing. The bridge is the Doseedo desktop app: it runs on your Mac, subscribes to the session, and applies each edit to the open project — moving the real region, rewriting the real notes — within seconds, keeping the .logicx on disk in sync.

If the desktop app is closed, nothing is lost: the edits are stored against the session and bake in next time it opens or is downloaded. The agent can see which case it is in, so it can tell you whether the change is live yet. That is also why the phone works: ask from a train, and the change is in Logic when you sit down, or it applies as the session opens.

Bouncing through your real plugins, with the DAW closed

The desktop app can also print tracks to audio through their actual third-party plugin chains while the DAW is closed. Stock DAWs cannot do a headless bounce through installed plugins; it normally means opening the project and sitting through it. Here the agent queues the bounce and gets stem files back.

The limit, stated plainly: audio tracks are covered; instrument and MIDI tracks need the DAW open to render. That is reported per track rather than silently dropped, so a bounce never hands you a stem that quietly lost its instrument.

Where your audio actually lives

For a file already on your disk — a drum pack, a recording, a folder of takes — the agent passes its local path. The cloud builds the session structure around it (tracks, regions, buses, routing) and the download hands back copy commands that place your files into the project. Audio uploads only when the server genuinely needs the samples: separation, transcription, conversion, generation and bounce.

The file-level half: convert, build, download

The same connection also moves whole project files. Claude converts a complete project between Logic Pro, Ableton Live, FL Studio, Pro Tools and REAPER — all 20 directions, rebuilt natively rather than bounced. It turns a stereo mix into a native session with separated stems on named tracks, a tempo map, per-stem MIDI and a chord guide. And it downloads any session as a native project file. Which fields survive which direction is documented at what carries over.

Scope, without the hand-waving

Try it on a real session

Install the connector, open a project in Logic with the desktop app running, and ask Claude to move something. It happens in the arrangement window.

Set up the MCP server →

The REAPER text trick, and when it is still useful

Before session control existed, the way to make an agent edit a project was a round-trip: convert it to REAPER's .rpp, which is plain text, edit the text, convert back. It worked, and it is no longer the recommended path — it cannot touch an open project, and the text leg carries tracks, MIDI, audio clips, tempo and markers but not automation, sends or plugin state.

It remains useful for bulk text surgery: renaming four hundred tracks by regex, diffing two arrangements line by line, scripting a transformation you would rather write as a text edit than as a list of operations. For that, convert out to .rpp, do it, convert back. For everything else, edit the session directly.

FAQ

Can Claude edit my Logic Pro project?

Yes. Through the Doseedo MCP server Claude reads a session as a full arrangement and changes it — regions, MIDI, mixer, plugins, tempo, markers, buses. With the Doseedo desktop app running on your Mac, those edits are applied to the open Logic Pro project within seconds and the file stays synced. With it closed, they persist and bake in the next time the session is opened or downloaded.

Can Claude edit an Ableton Live project the same way?

Not live. Live session editing and offline bounce target Logic Pro today — that is what the desktop bridge drives. For Ableton Live, FL Studio, Pro Tools and REAPER, Claude reads projects, builds sessions from audio, converts between all five DAWs in all 20 directions, and downloads a native project file. To drive the running Live application in realtime you want a different tool: AbletonOSC over its Python remote-script API.

Do I need the desktop app?

Only for the live half. Reading sessions, editing the stored session, converting projects and downloading a native project file all work with nothing but the MCP connector. The desktop app is what applies edits to an open Logic Pro project within seconds, and what renders an offline bounce through your installed plugins.

Can I edit my DAW project from my phone?

Yes. Add https://api.doseedo.com/mcp as a custom connector in the Claude phone or web app and sign in once. If the desktop app is running on your Mac with the project open, the edit lands there within seconds; if not, it is stored and applied the next time the session opens.

Does this control the DAW transport or move my playhead?

No. There is no transport control and no remote control surface. Claude changes the session itself — arrangement, MIDI, mixer, plugin chain — and the desktop app writes those changes into the open project. Nothing starts playback or takes over your screen.

Does my audio get uploaded to the cloud?

Not for session building. For a file already on your disk the agent passes its local path, the cloud builds the session structure around it, and the download hands back copy commands that place your files into the project. Audio uploads only when the server needs the samples: separation, transcription, conversion, generation and bounce.

Related