Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"ableton-for-ai": {
"env": {
"STEMS_SOURCE_DIR": "/path/to/your/exported/stems"
},
"args": [
"ableton-for-ai"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
For AI Agents: Please read AGENTS.md for detailed technical context and protocol specifications before working on this
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'ableton-for-ai' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked ableton-for-ai against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP Security Weekly
Get CVE alerts and security updates for io.github.peterkolbe/ableton-for-ai and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
[!IMPORTANT] For AI Agents: Please read AGENTS.md for detailed technical context and protocol specifications before working on this project.
Ableton for AI is the bridge between your DAW and AI models. It makes Ableton projects hearable and visible to AI models by implementing the Model Context Protocol (MCP) and exporting detailed project data.
Connect Ableton Live directly to MCP-capable AI clients (like Claude Desktop, Cursor, or Cline). The AI can inspect, analyze, and even modify your project in real-time.
Included Tools:
get_overview: SESSION DISCOVERY. Provides tempo, locators, and a list of all tracks with their current mixer state (volume, panning, etc.).get_track: TRACK INSPECTION. Comprehensive data for a single track: metadata, complete device chain, and all device parameters (with UI-readable strings).get_tracks: BULK TRACK INSPECTION. Query full data for a range of tracks in a single parallelized call.analyze_stems: DEEP AUDIO ANALYSIS. Triggers generation of audio summaries (.summary.json) and spectrograms (.spectrogram.webp) for all tracks.set_track_volume / set_track_panning: MIXER CONTROL. Remotely adjust track faders and panning.set_device_parameter: REMOTE CONTROL. Precisely adjust any parameter of any device in the project.Included Resources:
ableton://stems/{track_name}/summary: AUDIO SUMMARY. Compact analysis (JSON) containing LUFS, Peak, RMS, 10ms-frames, detected transients, and a legend field.ableton://stems/{track_name}/spectrogram: VISUAL ANALYSIS. Log-frequency spectrogram image (WebP) for visual frequency inspection.ableton://stems/available/summaries: Discovery resource for all tracks with available audio summaries.ableton://stems/available/spectrograms: Discovery resource for all tracks with available spectrograms.This project relies on AbletonOSC to communicate with Ableton Live.
uv lets you run the server directly without installing anything globally:
brew install uv # macOS (Homebrew)
# or: curl -LsSf https://astral.sh/uv/install.sh | sh (macOS/Linux)
# or: powershell -c "irm https://astral.sh/uv/install.ps1 | iex" (Windows)
Requires Python 3.11+ (python.org or brew install python):
pip install ableton-for-ai
Add the server to your MCP client configuration (e.g. Claude Desktop, Cursor, or Cline).
{
"mcpServers": {
"ableton-for-ai": {
"command": "uvx",
"args": ["ableton-for-ai"],
"env": {
"STEMS_SOURCE_DIR": "/path/to/your/exported/stems"
}
}
}
}
{
"mcpServers": {
"ableton-for-ai": {
"command": "ableton-for-ai",
"env": {
"STEMS_SOURCE_DIR": "/path/to/your/exported/stems"
}
}
}
}
[!NOTE]
STEMS_SOURCE_DIRmust point to the folder where your exported audio stems are located. You need to export stems manually from Ableton Live (e.g. via "Export Audio/Video" with individual tracks selected), as there is currently no OSC API for triggering exports. The audio analysis tools (analyze_stems) will look for files in this directory.