Cubase MCP server: what an agent can actually do

Published October 2026

Doseedo runs a hosted MCP server at https://api.doseedo.com/mcp that lets an AI agent work with Cubase projects as files: read the tracks, tempo, time signature and MIDI parts in a .cpr and rebuild them in Logic Pro, Ableton Live, FL Studio, Pro Tools or REAPER, and bring a project from any of those into Cubase as a .dawproject, which Cubase 14 and Nuendo open natively. It does not press buttons in a running Cubase. This page says what each half covers, including the parts of a .cpr it does not decode.

Two different things called "Cubase MCP"

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

• Remote-controlling a running Cubase. Steinberg's scripting surface is the MIDI Remote API: JavaScript (ES5) device scripts, introduced in Cubase 12 and at version 1.3 in Cubase 15.0.20. It is built for writing drivers for hardware controllers, mapping knobs and pads onto host functions, rather than as a general automation interface. The older Generic Remote maps MIDI CC messages to commands. The community Cubase MCP servers ride on these: they send MIDI through a virtual port into a mapping, which covers transport, volume, pan, mute and solo. If you want an agent pressing play, that is the route.
• Agent access to the project. Reading what is in a .cpr, converting it, carrying it into another DAW, bringing another DAW's work in. Cubase can stay closed, and the machine running the agent does not need Cubase installed. That is what the Doseedo MCP server does.

The two never touch the same object: a controller mapping cannot open a project on disk, and a file-level tool never sees Cubase's transport.

Setup

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

That is the Claude Code line; Cubase rooms are as often Windows as Mac, and the same URL registers on either in ChatGPT, Cursor, VS Code, Gemini CLI and Codex. The first call signs you in through a browser; a client that cannot open one sends X-API-Key: dsk_live_… from Settings → API keys. The tool reference covers all 43.

The directions doseedo_convert_project accepts with Cubase on one side, from its enum:

cubase2logic    logic2cubase
cubase2ableton  ableton2cubase
cubase2fl       fl2cubase
cubase2reaper   reaper2cubase
cubase2protools protools2cubase
cubase2dorico   dorico2cubase
cubase2studioone studioone2cubase
cubase2bitwig   bitwig2cubase
                garageband2cubase
auto2cubase     (detect the source, write for Cubase)

What crosses from a .cpr, said plainly

A conversion's report is the part to read, and the agent relays it. For a Cubase source the report says what the reader decoded and what it did not, in these words:

"the .cpr mixer, automation, plugin state and folder nesting
 are not decoded — tracks arrive at unity gain and centre pan"

• Read: tracks with their names, the tempo and time signature, and the MIDI parts on each track, each at its own position in the arrangement.
• Not read: the audio pool (audio tracks arrive named and empty, ready for the files), mixer levels, automation, plugin state and folder structure.
• Verified range: the note reader is checked against Cubase SX through 10.5 part layouts. When a newer project's parts are not recognised, the report says no notes were found rather than inventing any, and the dependable route is Cubase's own MIDI export alongside the project.

For a project that is mostly MIDI (a sketch, a score mockup, a writing session), that is most of the work. For a mixed record, plan on exporting stems and treating the conversion as the arrangement map. The Cubase to MIDI page does the notes-only job in a browser.

Bringing a project into Cubase

This direction is the cleaner one. Cubase 14 added DAWproject import, so a Logic, Ableton, FL Studio, Pro Tools, REAPER, Studio One, Bitwig or GarageBand project arrives as one .dawproject with its tracks, MIDI, audio and tempo map, and the audio inside the file. Nuendo reads the same file. Cubase 13 and earlier cannot open a DAWproject; for those the route is a MIDI file plus stems.

> Convert this Logic session for my mixer, who's on Cubase 14.
  Put the audio inside the file.

> I have a .cpr from 2019. Turn it into an Ableton set and tell
  me which tracks came across empty.

For edits, doseedo_import_project opens Logic, Ableton, FL Studio, REAPER and Pro Tools projects as sessions, so the agent converts a .cpr into one of those, edits, and converts the result to a .dawproject for Cubase.

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 live control of Cubase: no transport, no MixConsole moves, no reading the project open on your screen.
• No .cpr written. Cubase receives a .dawproject; the native project format is not documented, and a file that cannot be verified to open is not a conversion.
• No .cpr audio pool, mixer or automation on the way out, as above: the report states it on every conversion.
• Writing edits into a project on your Mac targets Logic Pro, through Dø Desktop.

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

• Cubase project to MIDI
• Cubase project to WAV
• Any DAW to .dawproject
• Convert Logic to Nuendo
• What is a .dawproject file
• What carries over between DAWs