Control your DAW from VS Code

Published October 2026

VS Code's agent mode uses MCP servers as tools, and the Doseedo MCP server is a remote HTTP server — so a three-line mcp.json gives Copilot real DAW tooling: read the sessions in your account as full arrangements and edit them, open a Logic, Ableton, FL Studio, REAPER or Pro Tools project as a session, convert projects across ten DAW formats, separate stems, transcribe audio and render written parts with modelled instruments. With Dø Desktop running, edits to a Logic project land live; the rest is a file in and a file out.

Install in VS Code

The shortest route is the code command-line tool, which has an --add-mcp flag that takes the server definition as JSON. This is the real run on VS Code 1.131:

$ code --add-mcp '{"name":"doseedo","type":"http","url":"https://api.doseedo.com/mcp"}'
Added MCP servers: doseedo

Captured 2026-10-15 against a fresh user profile

It writes the user-level file — ~/Library/Application Support/Code/User/mcp.json on macOS, %APPDATA%\Code\User\mcp.json on Windows, ~/.config/Code/User/mcp.json on Linux — and this is exactly what lands in it:

{
  "servers": {
    "doseedo": {
      "type": "http",
      "url": "https://api.doseedo.com/mcp"
    }
  },
  "inputs": []
}

Through the UI instead: Chat: Open Customizations from the Command Palette → MCP Servers → Add Server (also reachable as MCP: Add Server) → HTTP → paste the URL → name it doseedo and pick the user or workspace target. Or, to keep it with one project, write .vscode/mcp.json by hand:

{
  "servers": {
    "doseedo": {
      "type": "http",
      "url": "https://api.doseedo.com/mcp"
    }
  }
}

Start the server from the editor (the Start action above the entry, or the MCP Servers view) and VS Code runs the OAuth sign-in: a browser opens on Doseedo, you approve, and the grant appears under Settings → API keys as MCP · VS Code. To use a key instead — for a Codespace, say — add a header and keep the secret out of the file with an input variable:

{
  "inputs": [
    { "id": "doo-key", "type": "promptString", "password": true,
      "description": "Doseedo API key (dsk_live_…)" }
  ],
  "servers": {
    "doseedo": {
      "type": "http",
      "url": "https://api.doseedo.com/mcp",
      "headers": { "X-API-Key": "${input:doo-key}" }
    }
  }
}

In agent mode the tools picker should show doseedo with 33 tools. Deselect the ones a project will never need; the reads, quotes and analysis tools are the ones to leave on.

What to ask it

> List my Doseedo sessions and read "Bridge Demo".

> Shorten the intro by four bars, pull the vocal up 2 dB, and
  download the project to ~/Downloads.

> Convert every .flp in ./beats to Ableton and write a
  CHANGELOG.md of what each one lost.

> Analyse ./ref.wav, write a bass line in its key, render it
  on upright bass, and add the best take to a new track.

Where an editor pays off is around the tools: the agent can loop over a folder, keep a log, turn the place_local_files copy commands into a task and run it, and diff two session reads as JSON in the editor you are already in.

What the editor adds, and the limits

The server is the same one every client sees — live edits are Logic Pro on macOS with Dø Desktop, the other DAWs are files in and files out, nothing presses play; the hub has the scope table. What VS Code adds is the workspace around the tools. Agent mode can open the replay report a download returns as JSON in a tab, keep the place_local_files copy commands as a task in tasks.json and run it after every download, and keep a .vscode/mcp.json next to a song's folder so the server travels with the project when a collaborator clones it — with the key in an input variable, never in the file.

Tool budget: agent mode caps the tools enabled per request, and this server contributes 33. If a project only converts, keep the session-control family deselected in the tools picker; if it only edits sessions, drop the generation tools. The reads, doseedo_quote and the analysis tools are free and worth leaving on everywhere.

Related

• Control your DAW with an AI agent — what works today
• The same server in Cursor
• All 33 tools, what each does
• Convert DAW projects from an AI agent
• FL Studio MCP server