FL Studio and Ableton Live, Windows and Mac, one installer each. Since 1.4 VibeMind has its own window: type a sentence, press Build, no AI account needed. Claude (Claude Desktop, Claude Code) or ChatGPT (via Codex CLI) are optional extras. Three steps: install, let your DAW pair, open VibeMind.

You need

• Windows 10 or 11 (64-bit), or a Mac with Apple silicon on macOS 13 or later.
• FL Studio 2024 or later (any edition), and/or Ableton Live 11 or 12.
• Optional, one AI client: Claude Desktop (free plan works, with daily usage limits), Claude Code or Codex CLI.
• Ableton only: Max for Live (Live Suite, or Standard with the add-on) for the PluginHost and Arranger devices. The session, track, clip, device, browser and Serum 1 preset tools work without it.

1. Quit your DAW and your AI client first. With FL Studio closed, the installer pairs FL’s MIDI ports for you; with it open, you pair them by hand in step 2.
2. Windows: run the VibeMind Setup .exe from your download page. If SmartScreen says “Windows protected your PC”, click More info, check that the publisher line reads DMCSITE LLC (the company behind ROLLA Audio), then Run anyway (a new publisher’s file warns until it has download reputation; the installer is signed). It installs vibemind-mcp.exe and the FL bridge vibemind-fl-bridge.exe (started at logon) into %LOCALAPPDATA%\Programs\VibeMind\bin\.
3. Mac: open the VibeMind .pkg from your download page and click through. It installs the server into /Library/Application Support/VibeMind/bin/vibemind-mcp, the FL bridge as a launch agent, and, if Live is installed, the Live control surface script and the Max for Live devices into ~/Music/Ableton/User Library.
4. Both installers register VibeMind with every AI client they find (Claude Desktop, Claude Code, Codex CLI) without touching your other MCP servers, and, if FL Studio is installed and closed, install the two FL scripts under Documents\Image-Line\FL Studio\Settings\ and pair the MIDI ports (Windows: a reg export backup is taken first). Everything they did is logged in install.json and fl-setup.json: Windows %LOCALAPPDATA%\VibeMind\Logs\, Mac ~/Library/Logs/VibeMind/.

Claude Desktop only, either OS: the .mcpb bundle from the same download page is the alternative. Double-click it; Claude Desktop asks once.

Installed a client after VibeMind, or using a second user account? Run, as that user:

Mac:      "/Library/Application Support/VibeMind/install-user.sh"
Windows:  "%LOCALAPPDATA%\Programs\VibeMind\bin\vibemind-mcp.exe" --install-user

1. Ports. If the installer ran with FL closed, skip this. Otherwise open FL > Options > MIDI settings: input VibeMind FL → controller type VibeMind FL Bridge; output VibeMind FL Return → the same Port number as the input. Or close FL and ask Claude to “run the VibeMind setup check”; it repeats the pairing while FL is closed.
2. Mac permissions. System Settings > Privacy & Security: Accessibility for VibeMind (and for Claude Desktop or your terminal if you build from them), because FL has no API for its menus. Screen Recording only for loading samples and placing playlist clips. VibeMind never changes permissions; the setup check opens the right pane when one is missing. Windows needs no permissions.
3. Once per FL session: open any piano roll > Tools > Scripting > VibeMind Notes (it does nothing visible). FL only re-runs the last used script and forgets it on restart; the setup check tells you when it is not armed.
4. Restart FL once after the first setup so its Add menu lists the “VM nn”, “VM Shaper” and “VM SC Limiter” entries (a one-time FL read at start).

Two rules during a build

• Hands off FL while VibeMind builds. Sample loading and playlist placement drive FL’s own dialogs with real clicks; a click or keystroke of yours landing on a closing panel can crash FL. Save your own work before a build, then watch until VibeMind says it is done.
• No dialog on screen when a build starts. A licence nag, an update prompt or a crash report would catch the clicks, so VibeMind refuses to click and reports it. If FL opens a dialog mid-build (the FL trial’s save nag does), the build stops at that step with a MANUAL line: close the dialog and start a new project and press Build again (with Claude, ask it to continue).

1. Open Live > Settings (Live 11: Preferences) > Link, Tempo & MIDI.
2. In an empty Control Surface slot choose VibeMind. Leave Input and Output at None.
3. Live’s status bar shows “VibeMind: Listening on ports 9877 (control) and 9878 (browser)”.
4. For hosted synths with every parameter (Serum 2, Vital, Diva...) drag VibeMind_PluginHost from the Live browser (User Library > VibeMind) onto a MIDI track; up to four hosts run at once (instance 1-4). For Arrangement-view clips and automation drag VibeMind_Arranger onto any track.

Open your AI client (restart it if it was open during the install). First prompt, always:

• “Run the VibeMind setup check.” Every line is a check with its one-line fix: DAW found and version, bridge running, scripts installed, ports paired, FL answering, Mac permissions, VibeMind Notes armed. Green across means setup is done.
• “What’s the VibeMind status?” shows the version, trial or licence state and the DAW it detected.

Then:

• “Make me a Future type beat in FL Studio.” (Or a Playboi Carti or UK drill type beat, in FL or Live. About two minutes; install Vital first, it is free and runs the synths.)
• “Make me a tech house loop at 126: kick, clap, hats and a bassline, 8 bars.”
• “Grade this bounce against Future.” (the Report Card)
• “Search my plugins for Serum and load it on a new track.”

Claude Desktop

VibeMind appears under the tools (hammer/plug) icon after a restart. If it does not, check that claude_desktop_config.json (Mac ~/Library/Application Support/Claude/, Windows %APPDATA%\Claude\) contains the server; the Mac form is:

{ "mcpServers": { "vibemind": { "command": "/Library/Application Support/VibeMind/bin/vibemind-mcp", "args": [] } } }

On Windows the command is %LOCALAPPDATA%\Programs\VibeMind\bin\vibemind-mcp.exe (written with the full path, doubled backslashes).

Claude Code

Run claude mcp list; vibemind should be listed. To add it by hand (Mac shown; Windows uses the .exe path above):

claude mcp add --scope user vibemind "/Library/Application Support/VibeMind/bin/vibemind-mcp"

Codex CLI (ChatGPT)

Codex uses your ChatGPT account. Run codex and ask it to use the VibeMind tools; /mcp lists the servers. By hand, add to ~/.codex/config.toml:

[mcp_servers.vibemind]
command = "/Library/Application Support/VibeMind/bin/vibemind-mcp"
args = []
startup_timeout_sec = 30

The ChatGPT desktop app itself only accepts remote (web) connectors, so it cannot talk to VibeMind directly; use Codex CLI.

VibeMind runs fully for 7 days from the first time your AI client starts it; no card, no account. After that only vibemind_status, vibemind_activate and the setup check answer until you paste a key. Projects you built keep everything.

To activate, paste the whole key block from your purchase email (including the comment lines) into the chat: “Activate VibeMind with this key: ...”. Or in a terminal:

Mac:      "/Library/Application Support/VibeMind/bin/vibemind-mcp" --activate -
Windows:  "%LOCALAPPDATA%\Programs\VibeMind\bin\vibemind-mcp.exe" --activate -
# paste the key block, then press Ctrl-D (Windows: Ctrl-Z, Enter)

• One key covers FL Studio and Ableton, Windows and Mac, and is not machine-locked: the same key works on your laptop and desktop.
• Ask “What’s the VibeMind status?” to see trial days left or who it is licensed to.
• Old VibeMind lifetime keys and Pro membership keys (within their period) unlock everything too.
• To keep it, buy a licence ($49, one-time). The key arrives by email within minutes; check spam. The Gumroad receipt or order number is not the key.

Start with “Run the VibeMind setup check” in the chat, then “What’s the VibeMind status?”. In a terminal:

Mac:      "/Library/Application Support/VibeMind/bin/vibemind-mcp" --status
Windows:  "%LOCALAPPDATA%\Programs\VibeMind\bin\vibemind-mcp.exe" --status

FL Studio

• FL is not answering: the bridge is not running (Windows: vibemind-fl-bridge.exe starts at logon, log out and in or run it from %LOCALAPPDATA%\Programs\VibeMind\bin\; Mac: the launch agent starts at login), or the ports are not paired (step 2a, item 1). The setup check names which.
• Notes do not land in the piano roll: run Piano roll > Tools > Scripting > VibeMind Notes once in this FL session.
• “MANUAL” lines in a build: a dialog was open in FL, or a Mac permission is missing. Close the dialog or grant the permission, then ask Claude to continue. If a new FL version moves the playlist, placement falls back to a MANUAL list for that step and the rest of the build still lands; we test each FL release within a week.
• Windows MIDI ports: VibeMind uses Windows MIDI Services loopback ports where Windows has them, otherwise loopMIDI (free); the setup check says which it found and what to install if neither is there.

Ableton Live

• “Could not connect to Ableton on port 9877”: Live is not running, or Control Surface is not set to VibeMind. Check the status shows control.reachable: true.
• Port already in use: another control surface (an older AbletonMCP script, the old VibeMind Node device) owns 9877/9878. Remove it from Live’s Control Surface list. To move VibeMind to other ports, set control_port / browser_port in ~/.vibemind/config.json and restart Live and your AI client.
• PluginHost / Arranger tools time out: the device is not on a track, or Max for Live is missing (Live Standard without the add-on, or Live Intro/Lite). Drag VibeMind_PluginHost onto a MIDI track.
• VibeMind is not in Live’s Control Surface list: your User Library is not in the default place. Copy /Library/Application Support/VibeMind/payload/Remote Scripts/VibeMind into the Remote Scripts folder of your User Library (Live > Settings > Library shows where it is) and restart Live. Do the same with payload/User Library/VibeMind.

Clients

• Claude Desktop shows no VibeMind tools: restart Claude Desktop (it reads its config at start). If claude_desktop_config.json had a JSON error the installer left it untouched (see install.json); fix the file, then re-run the install-user step above, or install the .mcpb bundle instead.
• Logs: Windows %LOCALAPPDATA%\VibeMind\Logs\, Mac ~/Library/Logs/VibeMind/.

Help

• support@rollaaudio.com. Include your OS, FL or Live version, your AI client, the setup-check output and the exact error text. A one-line reply is enough.

Windows: Settings > Apps > Installed apps > VibeMind > Uninstall. It removes the FL scripts and port pairing, the bridge, the server and the VibeMind entry from each AI client (your other servers stay).

Mac:

sudo "/Library/Application Support/VibeMind/uninstall.sh"

Removes the Remote Script, the M4L devices, the FL bridge and scripts, ~/.vibemind, the logs, the server, the knowledge packs, the installer receipts, and the VibeMind entry from Claude Desktop, Claude Code and Codex CLI. Your licence key is kept so a reinstall stays activated; add --purge to remove it too. Restart your DAW and your AI client afterwards.

Try free for 7 days ↗Buy VibeMind · $49 ↗FL Studio pageAbleton page