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 your agent — Claude Code, Claude Desktop, Cursor, anything that speaks MCP — can convert projects between Logic Pro, Ableton Live, FL Studio and REAPER, turn a mix into a native DAW session, separate stems, transcribe audio to notes, and generate music. No SDK, no local process.
Install
One command in Claude Code (OAuth — the first tool call opens a browser, you sign in and approve):
claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcpOr 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 other MCP client works the same way: register https://api.doseedo.com/mcp as a Streamable-HTTP server and either complete the OAuth prompt or send the key as an X-API-Key header.
What the agent gets
| Tool | What it does |
|---|---|
| doseedo_convert_project | Convert a complete project between Logic Pro, Ableton Live, FL Studio and REAPER — all 12 directions, rebuilt natively. Tracks, MIDI, audio clips, 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 | Generate multi-stem music from a text brief. |
| doseedo_cover_song | Re-render a song in another style or instrumentation. |
| doseedo_get_upload_url | Presigned upload for the agent's own audio — PUT the bytes, get an audio_key. |
| doseedo_get_project_upload_url | Presigned upload for a DAW project (compress the project folder so its audio travels with it). |
| doseedo_check_task / doseedo_wait_task | Long jobs are async: submit tools return a task_id; these poll it. Transcription is ~15 s, a full session build ~4 min. |
| doseedo_account | Plan tier and remaining credits, read-only. |
Finished artifacts come back as plain https download URLs — the agent fetches them with curl, no auth needed on the download itself.
Connect an agent now
Mint a key, run the install command, and the next thing you type to your agent can be "convert this Ableton set to Logic."
Get an API key →Editing a Logic or Ableton project with Claude
The tools read and write project files; they don't puppet a running DAW. That still covers a workflow that wasn't possible before: an agent that restructures your session for you. A concrete loop that works today in Claude Code:
- Compress the
.logicxproject folder and ask Claude to convert it — it uploads and runslogic2reaper. - The returned
.rppis plain text. Claude edits it directly: renames and reorders tracks, moves regions, transposes MIDI, fixes tempo entries. - Claude runs
reaper2logicand hands back a native.logicxthat opens in Logic.
The honest caveat: the REAPER leg carries tracks, MIDI, audio clips, tempo and markers, but not automation, sends or plugin state — those travel at full fidelity only on the direct Logic↔Ableton directions. Use the text round-trip for structural edits, not for a mix you've automated. What each direction carries is documented field by field in what carries over.
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 — Claude Code, Claude Desktop, Cursor — connects with one command and gets eleven music-production tools: DAW project conversion, audio-to-session, stem separation, transcription, generation and covers. Nothing runs on your machine.
Can an AI agent edit my Logic Pro or Ableton project through it?
It can read, convert and build them. The converter parses .logicx, .als, .flp and .rpp natively and writes any of the four back, so an agent can restructure a project by converting it — including through REAPER's plain-text .rpp, which agents edit directly before converting back. There is no realtime control of a running DAW.
Which DAWs does it support?
Logic Pro (.logicx), Ableton Live (.als), FL Studio (.flp) and REAPER (.rpp) — conversion in all 12 directions; session building targets Logic or Ableton.
How is it authenticated and billed?
OAuth (approve once in the browser) or a dsk_ API key from Settings → API keys. Either way calls are metered exactly like using the site — same quotas, same credits, revocable per key.
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.