1. Conduid
  2. Developer Tools
  3. Flstudio MCP
MCP server · Developer Tools

Flstudio MCP

Agent tools for inspecting, editing, exporting, and launching FL Studio projects through CLI and MCP tools.

47Fair

Scored 7 days ago · breakdown

About Flstudio MCP

Flstudio MCP is an MCP server published by veenastudio in the Developer Tools category: agent tools for inspecting, editing, exporting, and launching FL Studio projects through CLI and MCP tools.

The repository has 107 stars and 10 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/veenastudio/flstudio-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Flstudio MCP

Powered by Claude · Grounded in docs

I know everything about Flstudio MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository yesterday. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • !Dependencies pinnedNo lockfile. Installs can pull different code over time.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

flstudio MCP

This is an MCP server that connects Claude to FL Studio.

Made this in 3 days. We're open sourcing it to see what we can actually get out of it. The possibilities are endless.

If you're running to any issues, join our discord and we can setup it for you.

(also join if you interested in the future of music and AI or want to request features. we're building this with you)

https://discord.gg/ZjG9TaEhvy

Check out our AI-Powered DAW for musicians at www.veena.studio

All in browser. All for free.

Step 1: Download the Files

You should see two main items.

  • A folder called Test Controller
  • A python file called trigger.py The Test Controller folder has a file called device_test.py that receives information from the MCP server. trigger.py is the MCP server.

Place the Test Controller folder in Image-Line/FL Studio/Settings/Hardware (Don't change the name of this file or folder)

Step 2: Set up MCP for Claude

Follow this tutorial to see how to setup MCP servers in Claude by edyting the claude_desktop_config files.

https://modelcontextprotocol.io/quickstart/server

If you followed this process, make sure to change whatever mentions of weather.py to trigger.py

If the Hammer icon doesn't show up, open Task Manager and force close the Claude process.

It should then show up.

This is what my config file looks like

mcp

Step 3: Set Up Virtual MIDI Ports

For Windows

For Windows, download LoopMIDI from here.

https://www.tobias-erichsen.de/software/loopmidi.html

Install LoopMIDI and add a port using the + button.

This is what mine looks like: loopmidi2

For Mac

Your MIDI Ports would be automatically setup to receive data.

Step 4: Setup MIDI Controller

Open FL Studio.

Go To Options > MIDI Settings.

In the Input Tab, click the MIDI Input you just created with LoopMIDI.

Change controller type from (generic controller) to Test Controller.

Step 5: Download Packages

Go to the folder with the trigger.py file. (This is the MCP Server file)

Activate the conda environment (like you learned in the Claude MCP Setup Tutorial)

Run this command to download the necessary packages: uv pip install httpx mido python-rtmidi typing fastmcp FL-Studio-API-Stubs (uv should be installed from the Claude MCP setup)

Step 6: Verify MCP Connection

Tell Claude to get available MIDI ports.

This should use the MCP to get the ports from FL Studio.

If Windows, copy the port you created with LoopMIDI and the number in front of it.

If Mac, copy the default port.

loopmidi

In my case, I copy loopMIDI Port 2

Open trigger.py in a text editor and replace the default port with the name of the port you just copied. output_port = mido.open_output('loopMIDI Port 2')

Step 7: Make Music

Use the MCP to send melodies, chords, drums, etc.

Click on the instrument you want to record to and it will live record to the piano roll of that instrument.

I tend to use this prompt when I start a new chat: Here is format for notes: note(0-127),velocity(0-100),length in beats(decimal),position in beats(decimal)

Step 8: Share what you made

Share what you made on our Discord: https://discord.gg/ZjG9TaEhvy

Credits

FL Studio API Stubs: https://github.com/IL-Group/FL-Studio-API-Stubs Ableton MCP: https://github.com/ahujasid/ableton-mcp

Nerd Stuff

If you want to contribute please go ahead.

The way this works is that device_test.py behaves as a virtual MIDI Controller. The MCP server (trigger.py) communicates with this MIDI Controller by opening a Virtual Port and sending MIDI messages through a library called MIDO.

The issue with MIDI messages is that its only 7 bits so we can only send in number from 0-127.

So we encrypt all of our MIDI data like note position, etc in multiple MIDI notes that the device knows how to read.

Hopefully, Image Line can give us more access to their DAW via their API so we don't have to do this MIDI nonsense.

README fetched from the repository yesterday. The original is authoritative.

Questions

About Flstudio MCP

How do I install Flstudio MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Flstudio MCP safe to use with an AI agent?

Its trust score is 47 out of 100 (fair). It passes 2 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Flstudio MCP still maintained?

The last commit was a year ago and 3 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.