§ Guide · For developers & agents

Logic Pro MCP server: let Claude edit your session

Published September 2026 · Updated October 2026

There is an MCP server for Logic Pro, and it is hosted: https://api.doseedo.com/mcp. Connect it to Claude Code, Claude Desktop, the Claude phone app, ChatGPT or any other MCP client, and the agent can read your Logic sessions as a full arrangement and change them: move a region, rewrite the MIDI, pull a fader, insert a plugin by name. With the Doseedo Desktop app running on your Mac, those edits go into your Logic project: it saves the project, keeps a backup, closes it, writes the edits and reopens it, about 10–20 seconds per batch. Nothing to self-host, no SDK.

Logic is the DAW where this works end to end, so this is the deep guide: install, how edits reach the project, what happens with the desktop app closed, the offline bounce, and what it does not do.

Why Logic needs a bridge at all

Apple ships no public realtime scripting API for Logic Pro. The one scripting surface is Scripter, a MIDI-FX plugin running JavaScript inside a single channel strip: it sees MIDI passing through that strip and nothing else; it cannot read the arrangement, add a track, or touch another region. Logic's AppleScript dictionary is close to empty. That is why "automate Logic Pro" has historically meant nothing, while a running Ableton set has at least been reachable through AbletonOSC and pylive.

The Doseedo Desktop app works around that gap by editing the project file itself. The MCP server writes to a cloud session; for each batch of edits, the desktop app saves the open project (your unsaved work included), keeps a backup copy in ~/Music/Logic/Dø Desktop Backups/<project>/ (the last 20 are kept), closes it, writes the edits into the .logicx and reopens it. If the project is not open, the edits are written straight into the file. It is not real-time and there is no transport control: the project closes and reopens.

Install

One command in Claude Code. OAuth handles auth; the first tool call opens a browser to sign in and approve:

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

For a client without a browser (CI, a server, a script), use an API 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, paste the same URL, sign in once. The same URL installs in ChatGPT, Cursor, Gemini CLI, OpenAI Codex, VS Code and the Claude phone and web apps, one page per client. Any other Streamable HTTP client registers it the same way. There are 33 tools behind the endpoint; the reference lists every one.

To have edits written into your Logic project you also need the latest Doseedo Desktop running on the Mac that has the project. 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. Everything else works with the connector alone.

Hosted vs. local Logic Pro MCP servers

Search for a Logic Pro MCP server and most of what comes back is open-source projects you run on your own Mac: koltyj/logic-pro-mcp and MongLong0214/logic-pro-mcp are the best known. They are good at something different, so pick by the job:

Local servers (GitHub)Doseedo (hosted)
How it reaches LogicDrives the running app: AppleScript, Accessibility, CoreMIDI, key eventsEdits the project itself; Dø Desktop saves, closes and reopens the project to write each batch of edits in
SetupClone, build, run a stdio server on the Mac, grant Accessibility permissionsOne URL: claude mcp add, a Claude connector or a ChatGPT custom MCP server; Dø Desktop asks once for Accessibility
Transport and playbackYes: play, record, move the playheadNo, it edits the arrangement, not the console
Reads the whole arrangementWhat the UI exposes while Logic is openEvery track, region, fader and plugin, in beats and seconds, with Logic closed too
From your phone / Claude webNo, the agent has to run on that MacYes, with Dø Desktop running on the Mac the edits go into the project; otherwise at its next open or download
Beyond editing—Offline bounce through your plugins, convert across ten DAW formats, audio to session, stems, transcription

They also combine: a local server for transport while you sit at the Mac, this one for structural edits and everything you ask for when you are not there.

What editing looks like

You talk to the agent in session terms, not API calls:

> List my sessions.

> In "Bridge Demo", what is on track 4 and how loud is it?

> Shorten the intro by four bars, pull the lead vocal up
  2 dB, and put a Channel EQ on the drum bus.

> Add a submix bus called "Horns" and route the trumpet
  and sax into it.

The agent reads the session first: every track with its ids, regions in beats and seconds, mixer levels in real dB, plugin chains, tempo, markers, plus whether the desktop app is connected to that session right now. Then it submits the edits. With the desktop app connected, Dø Desktop closes the project and reopens it with the edits in, about 10–20 seconds later, and a notification offers Undo, which restores the backup.

What the edit set covers

When the desktop app is closed

Nothing is lost and nothing silently fails. The edits persist in the cloud session and bake in the next time the project opens, or immediately, if you ask the agent to download the session as a native .logicx, rebuilt server-side. Because the read tool reports the sync state, the agent knows which case it is in and tells you rather than guessing.

So you can work on a session from your phone, away from the machine: ask for the change on the train, and it is applied when the Mac next has the project open.

Set it up on a real project

Install the connector, install the desktop app, open a Logic project, and ask Claude or ChatGPT what is on track 3. The whole loop takes a few minutes.

The Doseedo MCP server →

Offline bounce through your real plugins

This is the capability with no stock equivalent. Ask for a bounce and each track is printed to audio through its real third-party plugin chain, with the DAW closed: the desktop app renders it in the background and hands back downloadable stems. Logic's own bounce requires the app open and the project in front of you; this does not.

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 dropped silently, so a bounce never hands you a stem that quietly lost its instrument.

Bounces are async, like the other long jobs: the submit tool returns a task_id, a wait tool polls it, and finished stems come back as plain https URLs.

Your audio stays on your machine

When you point the agent at a file already on your disk, it passes the local path: the cloud builds the session structure (tracks, regions, buses, routing) and the download hands back copy commands that place your own files into the project. Audio uploads only when the server genuinely needs the samples: separation, transcription, conversion, generation and bounce.

The rest of the surface

The same connection carries the tools that make session control useful:

Metering is the boring kind: MCP calls count exactly like using the site: same account, same credits, revocable per client.

What it does not do

FAQ

Is there an MCP server for Logic Pro?

Yes. The Doseedo MCP server is a hosted Model Context Protocol endpoint at https://api.doseedo.com/mcp. It exposes 33 tools, and the session-control tools let an agent list your sessions, read one as a full arrangement, and apply edits. With the latest Doseedo Desktop app running on your Mac, each batch is written 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.

How do I install the Logic Pro MCP server?

In Claude Code, run claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp. The first tool call opens a browser for OAuth. In the Claude phone and web apps it installs as a custom connector under Settings → Connectors. For headless clients, append --header "X-API-Key: dsk_live_..." with a key from Settings → API keys.

Does Logic Pro have a scripting API?

Not a public realtime one. Logic ships Scripter, a MIDI-FX plugin running JavaScript inside a single channel strip, which cannot read or change the arrangement. Its AppleScript dictionary is minimal. The Doseedo Desktop bridge works around that: the cloud session holds the edits, and the desktop app saves and closes the project, writes them into the file and reopens it.

What happens if the desktop app is not running?

Nothing is lost. The edits persist in the cloud session and bake in the next time the project opens, or when you download it as a native .logicx. The read tool reports whether the desktop app is connected to that session, so the agent always knows whether a change has reached the project yet.

Can it bounce tracks through third-party plugins with Logic closed?

Yes, for audio tracks. An offline bounce prints them to audio through their real third-party plugin chains with the DAW closed, rendered in the background by the desktop app. Instrument and MIDI tracks need the DAW open to render, and that is reported per track rather than dropped silently. A stock DAW cannot do a headless bounce through installed plugins. The result comes back as downloadable stem files.

Does my audio get uploaded?

Only when the server genuinely needs the samples: separation, transcription, conversion, generation, or a bounce. For a file already on your disk the agent passes the local path, the cloud builds the session structure, and the download hands back copy commands that place your files into the project.

How is it different from the open-source Logic Pro MCP servers on GitHub?

Those run on your Mac and drive the Logic app through AppleScript, Accessibility and MIDI, so they can control transport and playback while you sit at the machine. Doseedo is hosted: nothing to install for the MCP itself, it works from the Claude and ChatGPT phone and web apps, it reads the full arrangement even with Logic closed, and Dø Desktop writes its edits into the project by saving, closing and reopening it. It does not control transport. The two can be used together.

The Doseedo MCP server · one URL, every client

By DAW
By AI client
By capability

Related