§ Guide · For developers & agents

Logic Pro MCP server: let Claude edit your session

Q: 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 then Connectors. For headless clients, append --header "X-API-Key: dsk_live_..." with a key from doseedo.com/settings/api-keys.

Published September 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 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 appear in your open Logic project within seconds. Nothing to self-host, no SDK.

Logic is the DAW where this works end to end, so this is the deep guide: install, live editing, 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 closes that gap. The MCP server writes to a cloud session and the desktop app applies each edit to the project Logic actually has open, keeping the .logicx on disk in sync. There is no realtime transport control — but the arrangement genuinely changes under your cursor.

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. Cursor and any other Streamable HTTP client register it the same way. There are 21 tools behind the endpoint; the full list is on the MCP server page.

For live editing you also need Doseedo Desktop running on the Mac that has the project. Everything else works with the connector alone.

What live 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 live on that session right now. Then it submits the edits. With Logic open and the desktop app connected, you watch the regions move.

What the edit set covers

Move and trim regions; rewrite MIDI notes.
Add and delete tracks; set fader, pan and mute.
Insert plugins by name, into a named track's chain.
Change tempo; add markers.
Create submix buses and route tracks into them.
Load samples into Quick Sampler.

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 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:

Project conversion — a complete project between Logic Pro, Ableton Live, FL Studio, Pro Tools and REAPER, all 20 directions, rebuilt natively.
Audio to session — a mix in, a native session out: separated stems on named tracks, tempo map, optional per-stem MIDI and a chord guide. See audio to session.
Stem separation, transcription, generation and covers.
Download — the session as a native project file, rebuilt server-side.

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

No realtime transport control. It will not start playback, arm a track, or move the playhead. It edits the arrangement, not the console.
Live editing and offline bounce are Logic Pro only, via the desktop bridge on macOS. Ableton Live, FL Studio, Pro Tools and REAPER projects can be read, built, converted and downloaded — they are not driven live. For a running Live set, that is AbletonOSC or pylive territory; see controlling Ableton with Python.
It does not replace the DAW. Mixing decisions, comping and anything you judge by ear stay where they are. This is for the structural and repetitive work.
Conversion fidelity has edges. Tracks, MIDI, audio, tempo and markers cross natively; automation, sends and plugin state are not universal. Field by field: what carries over.

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 21 tools, and the session-control tools let an agent list your sessions, read one as a full arrangement, and apply edits. With the Doseedo Desktop app running on your Mac, those edits are applied to the open Logic Pro project within 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 is what closes that gap: the cloud session holds the edits and the desktop app applies them to the running project.

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 is live on that session, so the agent always knows whether a change has landed 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.