Bitwig MCP server: what an agent can actually do

Published October 2026

Bitwig co-wrote DAWproject, the open project format, and that is the door an agent uses. Doseedo runs a hosted MCP server at https://api.doseedo.com/mcp that converts a .dawproject exported from Bitwig Studio into a native Logic Pro, Ableton Live, FL Studio, Pro Tools, REAPER or Cubase project, or Dorico MusicXML, and writes a .dawproject Bitwig 5 and later open from any of those. It does not read Bitwig's own .bwproject, and it does not drive the Bitwig on your screen; Bitwig has a real API for that, covered first.

Two different things called "Bitwig MCP"

The phrase "Bitwig MCP" names two unrelated capabilities, and mixing them up is how people end up disappointed:

• Controlling a running Bitwig. Bitwig Studio ships a documented Controller API: extensions in Java or JavaScript with access to the transport, tracks, devices and their parameters, and the clip launcher. DrivenByMoss exposes much of it over OSC. Community MCP servers sit on both, some speaking OSC through DrivenByMoss for transport, mixer and device parameters, others running their own extension to write MIDI clips into the launcher. Bitwig is one of the better-served DAWs for live agent control, and nothing below competes with that.
• Agent access to a project as a file. Taking a Bitwig project into another DAW, bringing another DAW's project into Bitwig, reading what is in it. Bitwig can be closed, or not installed on the machine the agent runs on. That is what the Doseedo MCP server does.

Setup

claude mcp add --transport http --scope user doseedo https://api.doseedo.com/mcp

Bitwig runs on macOS, Windows and Linux, and so does every client that can register this URL: Cursor, VS Code, Gemini CLI and Codex on all three, ChatGPT in the browser. The first call opens a browser to sign in; a client without one sends X-API-Key: dsk_live_… from Settings → API keys. The reference lists all 43 tools.

The fourteen directions with Bitwig on one side, plus the auto form, from the enum of doseedo_convert_project:

bitwig2logic    logic2bitwig
bitwig2ableton  ableton2bitwig
bitwig2fl       fl2bitwig
bitwig2reaper   reaper2bitwig
bitwig2protools protools2bitwig
bitwig2cubase   cubase2bitwig
bitwig2dorico   dorico2bitwig
auto2bitwig     (detect the source, write for Bitwig)

Export a DAWproject first

In Bitwig Studio, File › Export… › DAWproject. The result is one .dawproject file with the audio inside it, so there is no folder to compress and nothing left behind on your disk. A native .bwproject is refused: its format is Bitwig's own and undocumented, and the server says so instead of guessing.

The same tool accepts a .dawproject from anywhere: Studio One 6.5 and Cubase 14 export the format too. That is also why the enum has no bitwig2studioone: Bitwig and Studio One read each other's DAWproject files directly, with no converter in between.

> I exported my Bitwig track as a DAWproject. Make it a Logic
  project and tell me what the report flags.

> Turn this Pro Tools session into something Bitwig opens.

> Which tracks in this .dawproject have MIDI on them, and
  what's the tempo?

What the agent can do with it

• Out of Bitwig, natively. A .dawproject becomes a native .logicx, .als, .flp, .ptx or .rpp with the tracks, MIDI, audio and tempo map in place, or MusicXML for Dorico when the destination is a score.
• Into Bitwig as one file. A Logic, Ableton, FL Studio, Pro Tools, REAPER, Cubase or Dorico project arrives as a .dawproject Bitwig Studio 5 or later opens, with the audio inside.
• Read it without Bitwig. DAWproject is a documented container (XML describing the project, with the audio files beside it in one archive), so an agent can answer "what is in here?" from the file itself. What a .dawproject holds explains the layout.
• Edit it as a session. doseedo_import_project opens Logic, Ableton, FL Studio, REAPER and Pro Tools projects, so the agent converts the DAWproject to one of those, edits regions, notes, faders and tempo, and converts back to a .dawproject.

Long jobs follow one shape everywhere: the submit tool returns a job_id, doseedo_wait_task polls it server-side (one call holds at most 50 seconds, so the agent calls again while it is still running), and the result arrives as pre-signed download links that work with a plain curl for 24 hours, with no key on the download. Those links are reusable as the input of the next tool, so a separated stem feeds the transcriber and a generated take lands on a session track without a round trip through your disk.

What it does not do

• No .bwproject in or out. Bitwig receives and sends .dawproject.
• No live control: no transport, no clip launching, no device tweaks on the running app. That is the Controller API's job.
• Writing edits into a project on your Mac targets Logic Pro, through Dø Desktop; a Bitwig project is edited as a session and handed back as a file.

Scope, stated once. Writing an agent's edits into a project on your Mac (Dø Desktop saves the project, closes it, writes the edits in and reopens it) and the offline bounce target Logic Pro on macOS, through the Dø Desktop bridge. Reading, building, converting and downloading projects cover Logic Pro, Ableton Live, FL Studio, Pro Tools and REAPER, and conversion covers ten DAW formats (those five plus Cubase, Dorico, Studio One, Bitwig, and GarageBand in) in all 75 directions. Nothing here drives a transport or moves a playhead: the agent edits the session, not the console.

Related

• Open a .bwproject without Bitwig
• Convert Bitwig to Logic
• Convert Bitwig to Ableton
• Bitwig project to MIDI
• What is a .dawproject file
• DAWproject, Logic and Ableton