§ Guide · For developers & agents

Edit Logic and Ableton projects with Claude

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 go into your Logic Pro project: it saves the project, keeps a backup, closes it, writes the edits and reopens it, in about 10–20 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; writing edits into a project on your Mac, as described here, targets Logic Pro today. ChatGPT and other MCP clients use the same server the same way.

Published August 2026 · Updated November 2026

Connect Doseedo to Claude

https://api.doseedo.com/mcp
  • Claude (phone, web, Desktop): Settings → Connectors → Add custom connector → paste the URL, sign in once
  • Claude Code: claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp

Then sign in to Doseedo once, when your AI asks. Another client? One line each.

Server
api.doseedo.com/mcphosted, nothing to install
Tools
53one URL, every client
Sign-in
OAuthor an API key header
Cost
Free to startthe site’s credits, no MCP pricing

Setup: one command

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

This is what a connected server looks like afterwards: the two commands that confirm it, run on the machine this page was written on:

$ claude mcp list
Checking MCP server health…
doseedo: https://api.doseedo.com/mcp (HTTP) - ✔ Connected

$ claude mcp get doseedo
doseedo:
  Scope: User config (available in all your projects)
  Status: ✔ Connected
  Type: http
  URL: https://api.doseedo.com/mcp

To remove this server, run: claude mcp remove doseedo -s user

Captured 2026-10-15, Claude Code on macOS

"Connected" appears before you have signed in, because the handshake is served without a credential; the OAuth prompt arrives on the first real tool call. If a terminal has ANTHROPIC_API_KEY set, Claude Code notes that claude.ai connectors are disabled in that session; the server added with claude mcp add is unaffected by that, which is one reason to add it this way rather than through the connector UI on a developer machine.

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 ChatGPT as a custom MCP server, in Cursor, and in any client that speaks Streamable HTTP MCP. There are 53 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.

Only the DAW tools: the DAW sessions connector

If you want Claude working on your projects and nothing else, connect https://api.doseedo.com/mcp/daw instead. It is the same account, the same sessions and the same sign-in, with only the DAW tools: list, read, create, edit, download, bounce and delete sessions; check the desktop app and the plugins it can load; upload, import and convert projects; and follow, list and cancel the conversion and bounce jobs. It generates no audio: every sound in a session comes from the project's own audio, instruments and plugins.

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

In the Claude web, desktop and phone apps, add the same URL under Settings → Connectors → Add custom connector. Listing the tools needs no sign-in; the first call that reads or changes your account opens the Doseedo sign-in.

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 for each batch of edits saves the open project (your unsaved work included), keeps a backup copy, closes it, writes the edits into the .logicx and reopens it, in about 10–20 seconds. If the project is not open, the edits go straight into the file. A notification after each apply offers Undo, which restores the backup. The first time, macOS asks to let Dø Desktop control Logic (Accessibility): click Allow in Dø Desktop; until then, edits wait while the project is open.

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 has reached the project 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 ten DAW formats (Logic Pro, Ableton Live, FL Studio, Pro Tools, REAPER, Cubase, Dorico, Studio One, Bitwig and GarageBand): all 75 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. The desktop app closes the project and reopens it with the change in, about 10–20 seconds later.

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, each batch goes into your Logic Pro project: the app saves it, keeps a backup, closes it, writes the edits and reopens it, in about 10–20 seconds. With it closed, they persist and bake in the next time the session is opened or downloaded. ChatGPT and other MCP clients edit the same way.

Can Claude edit an Ableton Live project the same way?

Not the same way. Writing edits into a project on your Mac, 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 ten DAW formats in all 75 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 to have edits written into a project on your Mac. 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 your Logic Pro project (it saves, closes and reopens it, about 10–20 seconds per batch), 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 (or as a custom MCP server in ChatGPT) and sign in once. If the desktop app is running on your Mac, the edit goes into the Logic project there in about 10–20 seconds; it closes and reopens the project to apply it; 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 project file, closing and reopening the project to do it. Nothing starts playback.

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.

The Doseedo MCP server · one URL, every client

By DAW
By AI client
By capability

Related

Also by Doseedo

AI soundtracks, 100+ AI instruments and AI vocal tools. One account, one pool of credits.