A
licenseA
qualityC
maintenanceMCP server for Ableton Live that exposes the Live Object Model to LLMs, enabling natural language control of music production.
36
33 npm
6
MIT
ableton-live-mcp
by jterratsdev
Related Servers
Alternatives to ableton-live-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes Ableton Live control (session state, transport, tracks, devices, clips, MIDI note editing) as tools for LLM agents, enabling natural language manipulation of a Live session.1MIT
- AlicenseAqualityCmaintenanceMCP server that bridges Ableton Live with AI models, enabling real-time project inspection and control such as track overview, device parameters, and audio analysis.1236 PyPIMIT
- FlicenseBqualityCmaintenanceMCP server for Ableton Live 12 enabling full DAW control (tracks, devices, mixer, clips, transport) and audio analysis via loopback capture, allowing LLMs to create, modify, and measure music in real time.621-
- FlicenseBqualityDmaintenanceMCP server for controlling Ableton Live, enabling AI assistants to interact with Live sessions through tools for track/clip/scene management, playback control, and device parameter adjustments.48-
- AlicenseCqualityCmaintenanceA Model Context Protocol server that enables real-time interaction with Ableton Live, allowing AI assistants to control song creation, track management, clip operations, and audio recording workflows.2322 npm92MIT
TDQS
B3/5.0
Scored across 59 tools
Disambiguation4/5
Most tools have distinct purposes, though some overlap exists (e.g., ableton_analyze_audio vs. ableton_analyze_mix) but descriptions help differentiate. Overall, an agent can distinguish tools with minimal confusion.
Naming Consistency5/5
All tools follow a consistent 'ableton_verb_noun' pattern, e.g., get_status, create_midi_track, set_tempo. No mixing of conventions; names are predictable and readable.
Tool Count3/5
With 59 tools, the server covers many DAW functionalities but feels heavy for a single MCP server. While each tool has a place, some could be merged (e.g., multiple clip operations). The count is borderline high.
Completeness4/5
The tool surface is extensive, covering transport, tracks, clips, devices, mixing, analysis, and more. Minor gaps exist (e.g., no delete_regular_track, no create_audio_track/clip) but most core workflows are supported.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive