Studio One MCP server: what an agent can actually do

Published October 2026

Doseedo runs a hosted MCP server at https://api.doseedo.com/mcp that gives an AI agent file-level access to Studio One songs. It opens a .song directly, with no export step in Studio One, and rebuilds it natively in Logic Pro, Ableton Live, FL Studio, Pro Tools, REAPER or Cubase. Work from any of those comes the other way as a .dawproject, which Studio One 6.5 and later import. Studio One was renamed Fender Studio Pro in version 8; the song format and everything on this page are the same under either name. What the server does not do is operate the Studio One window on your screen, and the honest reason is below.

Two different things called "Studio One MCP"

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

• Operating a running Studio One. Studio One publishes no scripting API for this and has no OSC. Its control-surface support runs on JavaScript device scripts that PreSonus never documented for outside use. The community MCP servers that drive a running Studio One work around that: an in-app bridge device that relays commands, Mackie Control messages for the mixer and transport, or mapped keyboard shortcuts for editing. They are young and version-specific (a bridge written against Studio One 5 is not guaranteed on Studio Pro 8), so check which version a project was tested on before you rely on it.
• Agent access to the song file. Reading a .song, converting it, carrying an arrangement into another DAW and back. That is a file problem: it needs no running Studio One, no plugin installed in it, and no particular version on your machine. It is what the Doseedo MCP server does.

Because Studio One has no public API, the file is the most dependable surface an agent has: a song folder is the same bytes whichever version saved it last.

Setup

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

Claude Code takes that one line and opens a browser to sign you in on the first tool call. Studio One users split between macOS and Windows, and so does this: the same URL registers in ChatGPT, Cursor, VS Code, Gemini CLI and Codex on either, and a client with no browser sends X-API-Key: dsk_live_… from Settings → API keys. All 43 tools are in the reference.

With Studio One on one side, doseedo_convert_project accepts these twelve, plus the auto form, from the tool's own enum:

studioone2logic   logic2studioone
studioone2ableton ableton2studioone
studioone2fl      fl2studioone
studioone2reaper  reaper2studioone
studioone2protools protools2studioone
studioone2cubase  cubase2studioone
auto2studioone    (detect the source, write for Studio One)

What the agent can do with a Studio One song

Ask in song terms; the agent compresses, uploads, waits and downloads on its own:

> Here's my Studio One song folder. Convert it to Logic and
  tell me what the report says didn't make it.

> My co-writer sent an Ableton set. Turn it into something
  Studio One opens, with the audio inside.

> What tempo changes and markers are in this .song?

• Out of Studio One, natively. A .song becomes a native .logicx, .als, .flp, .ptx or .rpp. Into Logic, for example, that means tracks with their names, volume, pan and mute, MIDI notes, audio events, markers, sends, and the tempo and time-signature maps with every change in them, with third-party effects arriving as the same plugin and its saved settings when it is installed on the Logic machine. The Studio One to Logic page lists the field-by-field detail, and each conversion's report lists what did not carry for its own target.
• Send the song folder, not just the file. Studio One keeps a song's recordings in Media/ beside the .song. Compress the whole folder and the audio travels; a bare .song converts the arrangement, MIDI and mixer, and the report lists the audio it could not find.
• Into Studio One as one file. The other direction is a single .dawproject with the audio inside it, which Studio One 6.5 and later imports, Fender Studio Pro included. Not a .song: that format is undocumented, and a file nobody can verify opens would only look like a conversion.
• Edit it as a session. doseedo_import_project opens Logic, Ableton, FL Studio, REAPER and Pro Tools projects for editing, so for a song the agent converts first (REAPER's text format is the usual stop), edits regions, notes, faders and tempo there, and converts the result back to a .dawproject for you.
• Just the notes or just the audio. On the site, Studio One to MIDI and Studio One to WAV handle a song that only needs to become a MIDI file or a render.

Studio One and Bitwig need no converter between them

DAWproject is the open format Bitwig and PreSonus wrote together, and both apps export and import it. That is why the enum has no studioone2bitwig: export DAWproject from Studio One, open it in Bitwig, and the reverse. The server earns its place on the pairs Studio One cannot reach by itself, which is every other DAW in the list.

What it does not do

• No live control. No transport, no mixer moves on the running app, no reading the song Studio One has open right now.
• No native .song written. Studio One receives a .dawproject; it imports cleanly from 6.5 on, and an older Studio One needs updating or a MIDI-and-stems route.
• Writing edits straight into a project on your Mac is a Logic Pro feature. Dø Desktop saves, closes and reopens a Logic project to apply an agent's edits; a Studio One song 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

• What is a .song file
• Open a .song without Studio One
• Convert Studio One to Logic
• Convert Studio One to Ableton
• What is a .dawproject file
• What carries over between DAWs