Other MCP Server · MODEL CONTEXT PROTOCOL
veenastudio flstudio mcp
veenastudio flstudio mcp is a community-listed Model Context Protocol server. Review the source repository before installation.
WHAT IT CONNECTS
What veenastudio flstudio mcp gives an AI Agent
The source catalog does not include a structured feature list. Review the repository documentation before use.
SECURITY
An MCP listing is not a security review
An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.
README
Repository documentation
Made this in 3 days. We're open sourcing it to see what we can actually get out of it. The possibilities are endless.
(also join if you interested in the future of music and AI or want to request features. we're building this with you)
Check out our AI-Powered DAW for musicians at www.veena.studio
All in browser. All for free.
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)
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
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:
Your MIDI Ports would be automatically setup to receive data.
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.
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)
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.
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')
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)
Share what you made on our Discord: https://discord.gg/ZjG9TaEhvy
FL Studio API Stubs: https://github.com/IL-Group/FL-Studio-API-Stubs Ableton MCP: https://github.com/ahujasid/ableton-mcp
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.
COMMUNITY