An open-source MCP server for inspecting mixes, adjusting supported plug-in controls, and creating MIDI with an MCP-capable AI client.
Built around your workflow
Keep making music in FL Studio, with an AI client alongside your session. The local integration connects supported DAW controls to conversational requests, so you can investigate a mix or shape a musical idea without losing the context of the project.
The documented Mix Doctor workflow inspects concerns such as clipping, headroom, levels and EQ, then proposes targeted changes. Review the proposed action and its reported result. Approval, readback and rollback support do not mean every operation is reversible.
Read or set exposed plug-in parameters by name, then check what changed. You choose and load the plug-ins yourself. Available controls and value behavior depend on the plug-in and FL Studio’s API.
Work with patterns, notes, chords, quantization and step-sequencer parts, or export MIDI. Optional tempo/key analysis and audio-to-MIDI capabilities have additional dependencies and model downloads; they are separate from the basic setup.
The first steps
The project documents Windows 10/11 and macOS. Windows has broader reported testing; macOS coverage is more limited. Follow the README for current, version-matched commands.
Read the full setup guideCreate the named virtual MIDI ports using loopMIDI on Windows or IAC Driver on macOS.
Follow the operating-system-specific setup script in the project README.
Configure FL Studio’s MIDI and controller settings, then start the local daemon.
Connect your MCP client. Arm MCP_Apply once per session for piano-roll note writing.
Good to know
No. You need FL Studio installed and running, the local controller/MIDI setup and an MCP-capable client. The repository supplies the integration, rather than a new DAW.
The FL API used by this project does not load plug-ins or audio files, or render/export audio. Those actions remain manual. MIDI export is a separate supported workflow.
Coverage varies. Some parameters reject requested values or snap to a supported value. Check reported results rather than assuming every control can be changed accurately.
Use the public GitHub source and README setup. Release v1.0.0 does not include a standalone installer. Installing a Python package alone does not replace the local controller and virtual MIDI configuration.
Review the returned result and check the affected control in FL Studio. A requested value may be rejected or snapped to a supported value. Readback and rollback support vary by operation, so keep a saved project before making larger changes.
Source, setup & support
Start with the source and current setup documentation. These MCP integrations require a local developer setup; standalone app installers are not available.
