FL Studio Agent

Drive FL Studio from an AI agent: an MCP server that writes notes, sets tempo, levels and plugin parameters, checks which channels sound, and renders the mix, in your own FL Studio. Source, docs, and the native Bridge plugin: https://github.com/origami-research/fl-studio-agent

Claude Code:

claude mcp add --scope user fl-studio -- uvx --python 3.12 fl-studio-agent

Quick start

You need FL Studio 2026 on macOS or Windows and uv.

1. Install uv if you don't have it. macOS: curl -LsSf https://astral.sh/uv/install.sh | sh. Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex", then install loopMIDI and add two ports named exactly FLMCP Req and FLMCP Res (Windows has no virtual MIDI ports; macOS needs nothing).

2. Set up FL Studio once. Start FL once if you never have, close it, then run:

   uvx --python 3.12 --from fl-studio-agent fl-mcp-install
   

   It installs the controller and note scripts, assigns the controller's MIDI ports, and creates the agent's own project (FLMCP Agent.flp; your other projects are never touched). It is safe to rerun. To update later, run it with fl-studio-agent@latest in place of fl-studio-agent and restart FL and your client.

3. Add the server to your client with a button above or a config below, open FL Studio, and ask for "a 4-bar chord loop in A minor".

Live writes and render also need the native Bridge plugin, built once from source; without it notes still land, with FL reloading the project per write.

claude mcp add --scope user fl-studio -- uvx --python 3.12 fl-studio-agent

{
  "mcpServers": {
    "fl-studio": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "fl-studio-agent"
      ]
    }
  }
}

{
  "mcpServers": {
    "fl-studio": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "fl-studio-agent"
      ]
    }
  }
}

code --add-mcp '{"name": "fl-studio", "type": "stdio", "command": "uvx", "args": ["--python", "3.12", "fl-studio-agent"]}'

{
  "mcpServers": {
    "fl-studio": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "fl-studio-agent"
      ]
    }
  }
}

Troubleshooting

Run the doctor while FL Studio is open:

uvx --python 3.12 --from fl-studio-agent fl-mcp-doctor

It prints one JSON report of the control plane (controller script and MIDI ports), the note plane, and the agent project, with a fix for anything not connected. The usual fixes: open FL Studio before your client starts the server; after an upgrade rerun step 2 with fl-studio-agent@latest (a stale controller is reported); on Windows, keep loopMIDI running with both ports. Using the FL Studio trial? Set FLMCP_FL_LICENSE=trial in the server's env, because the trial cannot reopen saved projects. uvx --python 3.12 fl-studio-agent --version prints the installed version.

Tools

run (Python against the FL SDK; its docstring is the SDK cheatsheet), get_scene (what FL has now), check (play a few bars and read which channels sounded), render (record the mix to WAV), and analyze (WAV analysis). The full description is in the repository README.