Control your DAW with an AI agent

Published September 2026

Yes, this exists today: connect the Doseedo MCP server at https://api.doseedo.com/mcp and an AI agent — Claude Code, Claude on your phone, Cursor, any MCP client — can read the sessions in your account as full arrangements and edit them, then hand you back a project your DAW opens. With the Doseedo Desktop app running on macOS, those edits land in your open Logic Pro project within seconds: live editing and offline bounce are Logic Pro only, through the macOS desktop bridge. What it is not is a remote control for the running application: nothing drives your transport or moves your playhead.

That distinction — editing the session versus puppeting the app — is the whole subject. Almost everything people mean by "control my DAW with AI" is the first: restructure the arrangement, fix the MIDI, build the template, print the stems. That works now.

What an agent can actually do to a session

Twenty-one tools in total: session control, plus project conversion, audio-to-session, stem separation, transcription, generation and covers. The session-control family is the subject here, and read comes first: an agent that cannot see the arrangement can only guess. One call returns the session as structure: every track with its ids, every region positioned in both beats and seconds, mixer levels with real dB values, the plugin chain on each channel, tempo, markers — plus whether the desktop app is live on that session right now.

Then edit, as a list of operations applied in one call:

• Move, trim and rearrange regions.
• Rewrite MIDI notes — pitch, position, length, velocity.
• Add or delete tracks; load a sample into Quick Sampler.
• Set faders, pan and mute; create submix buses and route tracks into them.
• Insert plugins by name — the stock catalog always, plus the plugins installed on your Mac when the desktop app is connected.
• Change tempo, add markers.

Offline bounce is the one thing here that stock DAWs do not do: print tracks to audio through their real third-party plugin chains with the DAW closed — the desktop app renders headless, in the background. Audio tracks are covered; instrument and MIDI tracks still need the DAW open, and are reported per track rather than quietly dropped. Downloading is a separate tool and needs no desktop app: the session is rebuilt server-side as a native .logicx.

Live versus file — the distinction that matters

Every edit goes to the cloud session first. What happens next depends on the desktop app:

• Desktop running, project open: each edit is applied to the live Logic Pro project within seconds, and the .logicx on disk stays in sync. This is what lets you work from your phone, away from the machine.
• Desktop closed: nothing is lost. The edits persist on the session and bake in the next time it opens, or when you download the project.

Only the live-apply and the offline bounce need the desktop bridge, and both target Logic Pro on macOS. Everything else — reading, building, converting, downloading — needs nothing but the connector, and covers Logic Pro (.logicx), Ableton Live (.als), FL Studio (.flp), Pro Tools (.ptx) and REAPER (.rpp), in all 20 conversion directions.

Install

Nothing to self-host, no SDK. The endpoint is hosted Streamable HTTP at https://api.doseedo.com/mcp.

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

The first tool call opens a browser to sign in and approve. For CI, servers, or any client without a browser, append a key from Settings → API keys instead:

claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp \
  --header "X-API-Key: dsk_live_..."

In the Claude phone and web apps it installs as a custom connector: Settings → Connectors → Add custom connector → the same URL. Cursor and any other MCP client register the same URL in their own MCP config.

A worked example: build a template, then print it

The clearest test is making something from nothing. Ask for a track template:

> In my Doseedo sessions, make a new one called "Beat Template"
  at 92 BPM: four sampler tracks — Kick, Snare, Hat, Perc — with
  the one-shots from ~/Samples/Analog/ loaded, all four routed
  into a drum bus with a compressor and a channel EQ on it.
  Then bounce the bus and give me the file.

What the agent does, in order: creates the session and sets tempo; adds four tracks and loads each sample into Quick Sampler; creates the submix bus and routes all four into it; inserts the compressor and EQ on the bus by name, checking first which plugins your machine actually has; then queues the bounce and polls until the render is finished. The bounce prints through the real plugin chain, so what comes back is the sound of your inserts, not a dry sum.

Two details make this practical rather than a demo. Long jobs are async — the submit tool returns a task_id and a wait tool polls it. And your samples stay on your disk: the agent passes the local path, the cloud builds the session around it, and the download hands back copy commands that place your files into the project. The result downloads as a native .logicx; a separate conversion call hands back an Ableton, FL Studio, Pro Tools or REAPER project instead. Either way it opens as an ordinary session: real tracks, MIDI and audio, tempo and markers, editable.

Why this needs a bridge at all

Logic Pro ships no public realtime scripting API — its one scripting surface, Scripter, is a MIDI-FX plugin that sees events on a single channel strip and cannot read or change the arrangement (the full picture). Ableton is the opposite shape: a running Live set is drivable through AbletonOSC or pylive, but that talks to the app, not your project files, and it is Live-only (details). The bridge closes the Logic gap: the agent edits a session it can read, and a local app applies those edits to the open project.

What it does not do

• No realtime transport control. No play, stop, record, locate or live fader rides from the agent.
• No live driving of Ableton, FL Studio, Pro Tools or REAPER. Those are read, built, converted and downloaded as project files. Live editing and offline bounce are Logic Pro, macOS, desktop app running.
• It does not replace your DAW. Mixing decisions, listening and taste stay where they were; this handles the structural and mechanical work.
• Conversion fidelity has edges. Tracks, MIDI, audio, tempo and markers arrive editable in every direction; automation, sends and plugin state travel furthest on Logic↔Ableton. Field by field: what carries over.

For the file side — converting a project, restructuring it, building one from a mix — see editing Logic and Ableton projects with Claude and converting projects between DAWs.

Related

• The Doseedo MCP server
• Edit Logic and Ableton projects with Claude
• Control Logic Pro with Python
• Control Ableton Live with Python
• Convert projects between DAWs
• The Doseedo Desktop app