FL Studio MCP server: what an agent can actually do

Published September 2026 · Updated October 2026

Doseedo runs a hosted MCP server at https://api.doseedo.com/mcp that lets an AI agent convert, read and download FL Studio projects: move an .flp between ten DAW formats, read what is inside one with FL closed, restructure an arrangement as text, hand you back a project you open in FL. What it does not do is drive the FL Studio window open on your screen right now: no transport, no mixer moves, no pattern triggering. FL has its own Python API for that, and this page will point you at it rather than blur the line.

Two different things called "FL Studio MCP"

Search for "FL Studio MCP" and the results are two unrelated kinds of thing, and the page you land on rarely says which one it is:

• Realtime control of a running project. FL Studio ships a built-in Python interpreter and a MIDI Controller Scripting API (since FL 20.7) reaching Channels, Mixer, playlist patterns, Arrangement and Transport. Flapi wraps it for remote use, and several community MCP servers sit on top of that. Its edges are real and worth knowing before you build on it: it cannot load new plugins, it cannot create patterns programmatically, and notes it triggers do not persist unless FL is recording. Nothing here replaces it.
• Agent access to the project itself. Reading what is in a project, converting it, restructuring it, downloading it. That is a file-level problem: it works with FL closed, and on machines without FL installed: a Linux server, a phone. It is what the Doseedo MCP server does.

The two do not compete; they barely touch the same objects. A controller script never opens an .flp on disk, and a file-level tool never sees your playhead. Use both: prepare the project with one, perform it with the other.

Setup

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

Claude Code is the one-line case; the first tool call opens a browser to sign in and approve, and a headless client sends X-API-Key: dsk_live_… from Settings → API keys instead. FL producers are more often on Windows than the other DAW crowds, and nothing here is Mac-only: ChatGPT, Cursor, VS Code, Gemini CLI and Codex all register the same URL on Windows, and the tool reference is the same 33 tools.

The seventeen directions doseedo_convert_project accepts for an .flp, from the tool's own enum: fl2logic logic2fl fl2ableton ableton2fl fl2reaper reaper2fl fl2protools protools2fl fl2cubase cubase2fl fl2dorico dorico2fl garageband2fl fl2bitwig bitwig2fl fl2studioone studioone2fl, plus auto2fl to detect the source.

What the agent can do with an FL project

You talk to it in project terms; it handles uploads, polling and downloads itself:

> Convert ~/Projects/beat.flp to Logic, and tell me what
  won't survive the trip.

> What's actually in this .flp? List the channels, the mixer
  routing and every sample it references.

> This project has 60 unnamed mixer tracks. Convert it to
  REAPER's text format so you can name them from what's
  routed to each, then convert it back to .flp.

Concretely, the capabilities that apply to FL Studio:

• Convert, natively. All 75 directions across ten DAW formats (Logic Pro, Ableton Live, FL Studio, Pro Tools, REAPER, Cubase, Dorico, Studio One, Bitwig and GarageBand), seventeen of them involving .flp. Tracks, MIDI, audio clips, tempo and markers arrive editable.
• Read a project. An agent can answer "what is in here?" with FL closed: channels, patterns, mixer routing, referenced samples. The browser .flp reader shows the same on a page, and opening an .flp without FL Studio covers the manual route.
• Restructure from code. Convert to REAPER's plain-text .rpp, edit the arrangement as text, convert back to .flp. Structural work survives; a week of automation does not; see what carries over.
• Download the result as a native project file you open in FL Studio.

Long jobs are async: the submit tool returns a task_id and a wait tool polls it until the artifact is ready. A conversion is typically well under two minutes.

Building an FL project from a mix takes two hops

The audio-to-session builder (full mix in, separated stems on named tracks, tempo map, optional per-stem MIDI and a chord guide) targets Logic Pro and Ableton Live. For FL, the agent builds one of those and then converts it to .flp. The stems, tempo map and MIDI survive that hop; it is one extra step rather than a different result, and worth knowing before you plan around it.

What travels with an .flp

An .flp stores sample paths, not samples, which is why a project opens with missing-sample dialogs on another machine. The same rule applies to a conversion: send the project folder compressed, or FL's own Export → Zipped loop package, so the audio travels with the project; the agent lists every referenced sample from the file first and tells you what the archive is missing before it spends a credit. Audio uploads only for the jobs that have to read it (conversion, separation, transcription, a bounce); for a session built around samples already on your disk the agent passes paths and the download hands back copy commands.

What it does not do: read this before you install

• No live control of a running FL Studio. No transport, no mixer moves, no pattern triggering on the open project. That is the MIDI Controller Scripting API and Flapi.
• Writing edits into a project on your Mac targets Logic Pro today. That half of this product runs through the Doseedo Desktop bridge on macOS, which saves, closes and reopens the Logic project to write each batch of edits in.
• Offline bounce is Logic-side too. Printing tracks through their real third-party plugin chains with the DAW closed runs through that same bridge.
• Session building reaches FL by conversion, not directly; see above.
• Plugin state and automation have limits into FL Studio. Out of FL, the stock mixer effects map onto native devices with their settings and third-party inserts keep their state; into FL, third-party instruments and effects arrive with their settings, but no stock effect from another DAW maps to FL's yet and automation beyond volume, pan and tempo is reported rather than carried.

Why Logic gets the desktop bridge and FL does not

It is the inverse of what the APIs suggest. Logic ships no public realtime scripting surface (its Scripter plugin is JavaScript confined to a single channel strip), so Doseedo reaches a Logic project through a native app instead: the desktop app saves it, closes it, writes the edits into the file and reopens it (the Logic side, in detail). FL already has a scripting API, but it is controller-shaped: built for hardware talking to a running instance, deliberately walled off from the filesystem, and unable to load plugins or author patterns. So the gap worth closing for FL was never realtime control. It was the project file: converting one, reading one, restructuring one without hand-editing a binary format FL will refuse to open.

Which tool for which job

• Move the transport or the mixer on a project that is open right now: the MIDI Controller Scripting API, or Flapi to drive it remotely.
• Ship control logic that lives with the project: an FL controller script.
• Convert, read, restructure or download projects, from a phone, a server, or a machine without FL: the MCP server.
• Have an agent's edits written into a project on your Mac: Logic Pro, with Doseedo Desktop running; it closes and reopens the project to apply them.

Related

• The Doseedo MCP server
• Ableton Live MCP server
• Logic Pro MCP server
• REAPER MCP server
• Control your DAW with ChatGPT
• All 33 tools, what each does
• What is an .flp file
• Open an .flp without FL Studio
• Convert FL Studio to Logic