{
"mcpServers": {
"mcp-server-ableton": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 25 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Mcp Server Ableton and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol server for Ableton Live, enabling AI agents to control your Ableton session over OSC.
graph LR
Agent[AI Agent] -->|MCP JSON-RPC over stdio| Server[mcp-server-ableton]
Server -->|UDP :11000| OSC[AbletonOSC]
OSC -->|Max for Live| Ableton[Ableton Live]
graph TD
subgraph MCP Tools
A[Atomic Tools] --> T[Transport: play, stop, tempo]
A --> TR[Tracks: volume, mute, rename]
A --> C[Clips: fire, stop, notes]
A --> D[Devices: list, set params]
A --> S[Scenes: list, fire]
B[Compound Tools] --> MP[Musical Phrase: clip + notes + device params]
B --> ACS[Adjust Clip Sound: notes + device params]
B --> Batch[Batch: sequence of atomic actions]
B --> SS[Session State: full snapshot]
end
The server communicates with Ableton Live through AbletonOSC, a Max for Live device that exposes Ableton's API over OSC (UDP). The MCP server translates tool calls into OSC messages and parses the responses.
With uvx:
{
"mcpServers": {
"ableton": {
"command": "uvx",
"args": ["mcp-server-ableton"]
}
}
}
With rvx:
{
"mcpServers": {
"ableton": {
"command": "rvx",
"args": ["mcp-server-ableton"]
}
}
}
Nix:
nix run github:vaporif/mcp-server-ableton
Cargo:
cargo install --git https://github.com/vaporif/mcp-server-ableton
GitHub Releases:
Download prebuilt binaries from Releases.
Install the bundled AbletonOSC device into your Ableton User Library:
mcp-server-ableton install
Then drag AbletonOSC from your User Library onto any track in Ableton.
Tools are designed for bulk operations — compound tools combine multiple actions into a single MCP call to minimize round-trips between the agent and server.
| Category | Tools | |---|---| | Transport | play, stop, get/set tempo | | Tracks | list, rename, volume, mute/unmute, mixer, detail | | Scenes | list, fire | | Clips | fire, stop, name, create MIDI clip, add/get/remove notes | | Devices | list, parameters, set parameter(s) | | Templates | list template tracks, create track from template | | Compound | create clip with notes, musical phrase, adjust clip sound, set multiple device params | | Batch | execute a sequence of arbitrary actions in one call with configurable error handling | | Session | full session state snapshot (tracks, scenes, mixer, devices) |
Every tool response includes a session_summary with current tempo, playback state, and selected track for context.
RUST_LOG=debug mcp-server-ableton
nix develop
just setup-hooks
just check
GPL-3.0-or-later