Flstudio MCP

What rosasynthesiz/flstudio-mcp MCP server does

The rosasynthesiz/flstudio-mcp MCP server connects an MCP client to FL Studio for music production tasks. It can inspect and modify mixer settings, routing, channels, patterns, piano-roll notes, and project state through natural-language requests. The project is aimed at both mixing and composition rather than only sending notes.

Its mixing features include whole-song peak tracking, gain-staging suggestions, level-aware compression, reference comparison, EQ and dynamics adjustments, reverb and delay changes, group mute or solo controls, and track or channel coloring. Mix diagnosis reports evidence such as clipping, limited headroom, level imbalance, missing high-pass filtering, ungrouped related tracks, and overlapping EQ boosts.

Composition tools can create and organize patterns, write notes and chords, quantize notes, build arrangements, compose within named scales or modes, and export a multi-track arrangement as a standard MIDI file. Audio tools estimate tempo and key and can transcribe melody to MIDI using CREPE pitch tracking with a lighter fallback.

How it works

The rosasynthesiz/flstudio-mcp MCP server communicates with FL Studio through a controller and two virtual MIDI ports named FLStudioMCP RX and FLStudioMCP TX. On Windows, the ports can be created with loopMIDI; on macOS, they use the IAC Driver. A daemon can hold the MIDI connection and route the MCP server over TCP.

Project changes use a snapshot, write, readback, and rollback workflow. The material describes changes as individually reviewable and reversible. Live resources expose project, mixer, transport, channels, patterns, and status information to the MCP client.

Note writing requires an additional FL Studio step: open the piano roll and run the seeded MCP_Apply script once per session. On macOS, Accessibility permission is needed for the application running the server or daemon so the note bridge can retrigger the script.

Setup and configuration

The rosasynthesiz/flstudio-mcp MCP server supports Windows 10/11 and macOS, with FL Studio 2025 or newer and Python 3.10+. Clone the repository, then run the platform installer: scripts\\install_windows.bat on Windows or ./scripts/install_macos.sh on macOS. These installers copy the controller and note bridge, install the server, and check for the required MIDI ports.

Configure FL Studio's MIDI settings with the RX port as an input using controller type FLStudioMCP, and the TX port as an output using the same port number. Start fl-studio-mcp-daemon, then register fl-studio-mcp in the MCP client's configuration. Setting FLSTUDIO_MCP_TRANSPORT to tcp routes the server through the daemon; leaving it unset allows direct MIDI-port access. Optional audio extras can be installed with the documented editable-install commands, and ffmpeg is optional for MP3 analysis.

Limitations and notes

FL Studio's scripting API cannot load plugins, load audio files, or render audio. Plugin and preset tools therefore recommend items from the installed library, while loading and rendering remain manual. Audio can be analyzed after it has been rendered manually.

Linux is not supported. Microtonal intervals and gamaka-heavy traditions are approximated through 12-tone MIDI, so the scale framework may be retained without exact microtonal or ornamental playback.