§ Guide · For developers & agents

Edit Logic and Ableton projects with Claude

Published August 2026

This is a workflow, not a concept piece: connect one MCP server and Claude Code can take your .logicx or .als, convert it between four DAWs, restructure the session by editing it as text, and hand you back a native project that opens in your DAW. Here's the setup, what a session actually looks like, and where the edges are.

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. (Headless alternative: append --header "X-API-Key: dsk_live_..." with a key from Settings → API keys.) Claude Desktop and Cursor connect to the same endpoint the same way. Full tool reference: the MCP server page.

What a session looks like

Zip your project folder — the zip carries the audio with it — and talk to Claude in its terms, not in API calls:

> Convert ~/Music/Demos/BridgeSong.zip (a Logic project)
  to an Ableton set.

> This Ableton set has 40 unnamed tracks. Convert it to
  REAPER, rename every track from what's actually on it,
  group the drums together, then give it back to me as
  an Ableton set again.

> Here's a stereo bounce of a song idea — build me a Logic
  session from it, with MIDI for the piano and bass and a
  chord guide track.

Claude handles the mechanics itself: it requests a presigned upload, PUTs the file, submits the job, polls until it's done, and downloads the artifact. Conversions come back in fifteen seconds to two minutes; a full audio-to-session build is about four.

How the "edit" actually works

There's no realtime wire into the DAW on your screen — the tools read and write project files. The editing trick that makes the middle example above real: REAPER's .rpp format is plain text. So Claude converts your Logic or Ableton project to .rpp, edits the session the way it edits any text file — tracks, names, region positions, MIDI notes, tempo entries — then converts back to a native .logicx or .als. Because the converter (unlike a text edit by hand) is the thing writing the final project, what you get back is a set your DAW actually opens.

The honest caveat, stated plainly: the text leg carries tracks, MIDI, audio clips, tempo and markers, not automation, sends or plugin state — those travel at full fidelity only on the direct Logic↔Ableton directions. Restructure arrangements this way; don't round-trip a mix you've spent a week automating. The field-by-field truth table is at what carries over.

Try it on a real project

Install the MCP server, zip a project, and ask Claude to convert it. The first one takes about two minutes end to end.

Set up the MCP server →

What Claude can and can't do here

Can: convert any pair of Logic, Ableton, FL Studio and REAPER (12 directions), natively.
Can: build a new Logic or Ableton session from a mix — separated stems, tempo map, per-stem MIDI, chord guide.
Can: separate stems, transcribe audio to notes, generate and cover music — same connection.
Can: answer "what's inside this set?" — an .als is gzipped XML Claude can read directly; a .logicx needs the parser (see the format guide).
Can't: control the running DAW — no transport, no live faders. (For that, on Ableton specifically, see AbletonOSC and pylive.)
Can't: preserve automation and plugin state through the text round-trip — direct Logic↔Ableton conversion is the full-fidelity path.

Billing is the boring kind: MCP calls meter exactly like using the site — same account, same quotas and credits, revocable per client from Settings → API keys.

FAQ

Can Claude edit my Logic Pro project?

Structurally, yes. Through the Doseedo MCP server Claude converts the .logicx to REAPER's plain-text format, edits the session as text — track names, region positions, MIDI, tempo — and converts back to a native .logicx. It reads and rewrites the project file; it does not control the Logic app itself.

What can Claude do with an Ableton project?

Convert it natively to Logic, FL Studio or REAPER (and back), build a new .als from a mix with separated stems and a tempo map, or restructure it through the same text round-trip. Ableton's .als is gzipped XML, so Claude can also read it directly to answer questions about what's inside.

Does this control the DAW app on my screen?

No. The tools operate on project files, not the running application. Nothing moves your playhead or touches an open session; you get back a new project file and open it yourself.

What's the honest fidelity caveat?

The text round-trip goes through REAPER's format, which carries tracks, MIDI, audio clips, tempo and markers — but not automation, sends or plugin state. Those travel at full fidelity only on the direct Logic↔Ableton conversions. Use the round-trip for structural edits, not automated mixes.