Do I need an SDK or a local server?

No. It is hosted Streamable HTTP — the client speaks MCP straight to api.doseedo.com/mcp. There is nothing to install beyond registering the endpoint with your client.

§ Developers · Model Context Protocol

Give your AI agent a DAW.

Published August 2026

The Doseedo MCP server is a hosted Model Context Protocol endpoint at api.doseedo.com/mcp. Connect it once and Claude — on your phone, in Claude Desktop, in Claude Code — can read and edit your DAW sessions: move and trim regions, rewrite MIDI, change the mixer, insert plugins, set tempo. With Dø Desktop running on your Mac, those edits land in your open Logic project live, and the file stays synced. It also converts projects between Logic Pro, Ableton Live, FL Studio, Pro Tools and REAPER, turns a mix into a session, separates stems, transcribes and generates. No SDK, no local server for the MCP itself.

Install

On your phone or the web — the Claude apps (iOS, Android, claude.ai): open Settings → Connectors → Add custom connector, paste https://api.doseedo.com/mcp, and sign in when prompted. Now you can tell Claude "move the sax in in my luckbe session" from anywhere, and it reaches Logic on your Mac.

Claude Code — one command (OAuth; 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

Claude Desktop — Settings → Connectors → Add custom connector → the same URL.

Or headless, with an API key from Settings → API keys — for CI, servers, or clients without a browser:

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

Any MCP client works the same way: register https://api.doseedo.com/mcp as a Streamable-HTTP server and complete the OAuth prompt or send the key as an X-API-Key header.

The point

You're away from your desk. You open Claude on your phone, say "in my session, shorten the intro and pull the vocal up 2 dB," and when you're back at your Mac it's already done in Logic — the edit was applied live and the project saved. That's what this connects.

What the agent gets

Two families: session control — read and edit the sessions in your account — and audio tools — generate, separate, transcribe, convert.

Tool	What it does
doseedo_list_sessions	List the sessions in your account — names, ids, DAW.
doseedo_get_session	Read a session as an arrangement: every track with its ids, its regions in beats and seconds, mixer levels (with dB), plugin chain, tempo, markers — plus whether Dø Desktop is live on it right now.
doseedo_edit_session	Apply a list of edits — move/trim a region, rewrite MIDI notes, add or delete a track, set a fader/pan/mute, insert or tweak a plugin, change tempo, add a marker. With Logic open they appear live within seconds; otherwise they persist and apply next time the session opens.
doseedo_bounce_session	Print tracks to audio through their real plugin chains, offline — Dø Desktop renders them in the background without you opening the DAW (stock plugins can't do this). Returns downloadable stems.
doseedo_add_audio_to_session	Drop a generated song or a separated stem straight onto a session, ready to place on a track.
doseedo_desktop_status	Is Dø Desktop running and connected to your DAW, which sessions it holds, how far it has applied — read-only.
doseedo_download_session	Save the session to your device as a native `.logicx`, rebuilt server-side — no desktop needed. Returns a short-lived, no-auth link, so the agent drops it straight into your Downloads with a plain `curl -o` (no key, no header).
doseedo_list_plugins	The plugins you can insert by name — the stock Logic catalog always, plus the plugins installed on your Mac when Dø Desktop is connected.
doseedo_convert_project	Convert a complete project between the five DAWs — all 20 directions (Logic Pro, Ableton Live, FL Studio, Pro Tools, REAPER), rebuilt natively. Tracks, MIDI, audio, tempo and markers arrive editable; Logic↔Ableton also carries automation, buses/sends and plugin state.
doseedo_audio_to_session	A full mix in, a native Logic or Ableton session out: separated stems on named tracks, tempo map, optional per-stem MIDI and a chord guide.
doseedo_separate_stems	Split a mix into isolated stems (vocals, drums, bass, melodic parts), sample-accurate.
doseedo_transcribe	Audio in, editable notes out — per-instrument models behind one surface.
doseedo_generate_music / doseedo_cover_song	Generate multi-stem music from a text brief, or re-render a song in another style.
doseedo_account	Plan tier and remaining credits, read-only.

Async jobs (generation, a session build, a bounce) follow one shape: the submit tool returns a task_id, and doseedo_wait_task polls it. Finished artifacts come back as plain https download URLs — the agent fetches them with curl, no auth needed on the download.

How a live edit reaches your DAW

This is the part that wasn't possible before. Logic has no automation API — you can't script it. Dø Desktop bridges that gap:

Claude calls doseedo_get_session to see the arrangement, then doseedo_edit_session with the edits — those land in the cloud session and the edit log.
Dø Desktop, running on your Mac, is subscribed to that session. It applies each edit to your open Logic project through its own bridge — moving the real region, rewriting the real notes — within seconds, and keeps the .logicx on disk in sync with the server.
If the desktop is closed, nothing is lost: the edits are saved and applied the next time that session opens. doseedo_get_session's sync block tells the agent which case it's in, so it always knows whether the change is live yet.

The one requirement for live edits is Dø Desktop running with the project open — everything else (reading, editing the stored session, bouncing, downloading a project) works with nothing but the connector. Bounces run whenever the desktop next runs, live through Logic if it's open or headless if it isn't.

Auth and metering — nothing new to learn

OAuth access tokens are ordinary dsk_ API keys; approving a client just mints one scoped to it. Every call is metered exactly like using the site — same quotas, same credits, and failed jobs refund. Revoke any client from Settings → API keys, where OAuth grants appear as MCP · <client name>. There is no separate MCP pricing and no separate account.

Design, briefly

Stateless Streamable HTTP — plain JSON-RPC over POST, no session ids, no server-initiated streams, so it works from short-lived processes and CI. Long jobs follow one async shape everywhere: submit returns a task_id, doseedo_wait_task polls server-side and tells the agent to call again if the job is still running. The endpoint lives on the same edge as the API, and the full HTTP surface behind the tools is documented in the docs.

FAQ

What is the Doseedo MCP server?

A hosted Model Context Protocol endpoint at api.doseedo.com/mcp. Any MCP client — the Claude phone/web apps, Claude Desktop, Claude Code, Cursor — connects with one command and can read and edit the DAW sessions in your account, plus convert projects, build sessions from audio, separate stems, transcribe and generate. The MCP itself runs nothing on your machine.

Can Claude actually edit my Logic project while it's open?

Yes. With Dø Desktop running on your Mac, an edit Claude makes through the connector — move a region, rewrite MIDI, change a fader, insert a plugin — is applied to your open Logic project within seconds, and the file is kept synced with the server. If the desktop is closed the edits persist and apply the next time the session opens; the agent can see which case it's in. This is real session editing, not the old convert-and-reimport workaround.

Can I use it from my phone?

Yes. Add https://api.doseedo.com/mcp as a custom connector in the Claude iOS/Android app (or on claude.ai), sign in once, and you can drive your sessions from anywhere. As long as Dø Desktop is running on your Mac, the edits reach Logic there; otherwise they're queued and applied at next open.

Can it bounce my tracks through third-party plugins without opening the DAW?

Yes — doseedo_bounce_session queues an offline print, and Dø Desktop renders each track through its real plugin chain in the background: live via Logic if it's open, headless if it isn't. Stock DAWs can't do a headless bounce through your installed plugins; this can. The result is downloadable stem files.

Which DAWs does it support?

Live session editing and bounce target Logic Pro today (the Dø Desktop bridge). Reading, building and converting cover Logic Pro (.logicx), Ableton Live (.als), FL Studio (.flp), Pro Tools (.ptx) and REAPER (.rpp) — conversion in all 20 directions.

How is it authenticated and billed?

OAuth (approve once) or a dsk_ API key from Settings → API keys. Calls are metered exactly like using the site — same quotas, same credits, revocable per key.