Control your DAW from Cursor

Published October 2026

Cursor's agent can drive a DAW the way it drives a codebase — through tools. One entry in mcp.json connects the Doseedo MCP server, and the agent can read the sessions in your account as full arrangements, edit them, open a Logic, Ableton, FL Studio, REAPER or Pro Tools project as a session, convert it between ten DAW formats, separate stems, transcribe audio and render parts with modelled instruments. Because Cursor runs on your machine, the audio it works with can stay on your disk: it passes local paths, and the finished project lands in ~/Downloads with a curl.

Install in Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json (every project) or .cursor/mcp.json in a project (that project only). Add one entry:

{
  "mcpServers": {
    "doseedo": {
      "url": "https://api.doseedo.com/mcp"
    }
  }
}

That is the whole install. Doseedo is a remote Streamable HTTP server, so there is no command to run, no package to install, no process to keep alive. The first tool call answers with an OAuth challenge; Cursor opens a browser to Doseedo's sign-in page, you approve, and the grant appears under Settings → API keys as MCP · Cursor. Cursor supports OAuth for servers that require it and registers its client automatically, so no client id is needed.

For a machine without a browser, or to pin one key, send the header instead of signing in:

{
  "mcpServers": {
    "doseedo": {
      "url": "https://api.doseedo.com/mcp",
      "headers": { "X-API-Key": "${env:DOO_API_KEY}" }
    }
  }
}

Cursor interpolates ${env:…}, so the key lives in your shell environment, not in a file you might commit. Open Cursor Settings → MCP: doseedo should list 33 tools, inside the per-chat tool budget, so nothing needs disabling.

The companion skills install with npx skills add doseedo/skills — the audio, session and convert skills land in ~/.cursor/skills/ and teach the agent the recipes before it calls a tool.

What to ask it

In the agent panel, talk about the project. The agent reads the session or recipe first, then acts:

> Open ~/Music/Logic/Bridge Demo.logicx as a Doseedo session,
  list the tracks, and tell me which ones have no plugins.

> In that session, add a submix bus called DRUMS, route the
  kick, snare and overheads into it, and put a compressor
  on the bus. Then download the project to ~/Downloads.

> Build a drum template from the one-shots in ~/Samples/Analog
  — four sampler tracks into a drum bus — without uploading
  the samples.

> Convert every .als in ./sets to Logic and write a table
  of what each one lost.

> Separate ./mix.wav into stems, transcribe the bass stem,
  and show me the notes as a chart.

Where Cursor pays off is the loop around the tools: it can iterate over a folder of projects, keep a log of what each conversion dropped, write the place_local_files copy commands into a script and run them, and compare two session reads as JSON. A chat client cannot do that part.

Local files never leave the machine

When you point the agent at a sample or a recording already on your disk, it passes the local path and the file's header numbers. The cloud builds the session structure — tracks, regions, buses, routing — around a reference to the file, and the download hands back copy commands that place your own files into the project. Uploads happen only when the server genuinely has to read the audio: separation, transcription, conversion, a cover, a bounce.

What this cannot do from Cursor or anywhere else: drive the DAW that is open on your screen. Live edits are Logic Pro with Dø Desktop; the other DAWs are files in and out. The hub has the table.

Cursor-specific notes

• Approvals. Cursor asks before a tool runs unless you allow a server's tools; the Doseedo tools that write (an edit, a conversion, a render) are the ones to keep on confirmation, while reads, quotes and the free analysis tools are safe to allow.
• Long jobs. A session build from a mix takes about four minutes and a render one to three; the agent waits through doseedo_wait_task in 50-second holds, so a long job is several calls, not one hang.
• Project scope. Put the entry in .cursor/mcp.json inside a music project's folder and the server is there only when that folder is open — handy when the repo is a song, not code.

Price a folder before converting it

The batch pattern above is where a quote earns its place: before looping over twelve sets, the agent asks doseedo_quote once and multiplies. This is the real response for a Logic-to-Ableton conversion, captured 2026-10-15 — the basis line is the price rule in words, and affordable is whether the connected account can pay for it now:

{
  "job": "convert_project",
  "estimate": { "generation": 1 },
  "basis": "a DAW conversion: 1 credit + 1 per GB past the first, from the monthly credit pool",
  "assumptions": [
    "estimate only — the plane gate is authoritative and a refusal names the exact price",
    "failed jobs are refunded; free accounts also have a monthly ceiling"
  ],
  "affordable": true
}

Twelve sets, twelve credits, and the agent knows before the first upload. The quote spends nothing and needs no sign-in, so it is also the cheapest way to check that the connection works at all.

Related

• Control your DAW with an AI agent — what works today
• Edit Logic and Ableton projects with Claude
• Swap a project onto a new drum pack
• All 33 tools, what each does
• Logic Pro MCP server