LiveMCP
Related Servers
Alternatives to LiveMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Ableton Live through a Max for Live device and optional Remote Script, covering tracks, clips, MIDI notes, mixer settings, transport, and plugin search and insertion.1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server to control Ableton Live via the Live API, offering curated tools for transport, tracks, clips, devices, automation, and more, plus a generic layer to access the entire Live Object Model.MIT
- AlicenseAqualityAmaintenanceEnables an MCP client to inspect and modify a running digital audio workstation session through a local Python remote-script TCP bridge, exposing tools for session and track structure, clip slots and MIDI notes, devices and browser items, and mixer/transport control. Read and bulk-write operations cover tempo, naming, clip creation and note editing, muting/soloing/arming, playback and scene launching, and device parameter loading and adjustment.322MIT
- AlicenseBqualityAmaintenanceLocal Python MCP server for inspecting and automating Ableton Live Sets, including MIDI editing, device control, audio analysis and groove tools. Connects MCP clients to a MIDI Remote Script and extension bridge on the user’s machine.974MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP client to control Ableton Live 12 through 56 tools covering tracks, clips, MIDI notes, devices and racks, mixer parameters, transport, browser loading, automation, and arrangement editing. It also provides optional audio analysis (key, chords, groove, transcription, stem separation, mastering listen) and session memory.MIT
- 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-
TDQS
Scored across 220 tools
Many tools have clear, distinct purposes, but there is notable overlap between pairs like add_notes_to_clip/add_notes_extended, get_notes_from_clip/get_notes_extended, set_track_volume vs set_track_properties, and the various device parameter getters. These overlapping tool pairs create potential misselection, though descriptions do help clarify which to prefer.
The vast majority of tools follow a consistent snake_case verb_noun pattern (get_track_info, set_track_volume, create_scene). Minor deviations like 'duplicate_to_arrangement', 'trigger_back_to_arrangement', and 'toggle_browse' are few and still readable, so the pattern is largely predictable.
With 220 tools, the server far exceeds any reasonable scope for a single MCP instance. Even for a DAW control server, this is an extreme number that will overwhelm agents and make tool selection expensive and error-prone.
The tool surface covers an extremely wide range of Ableton Live functionality: transport, tracks, scenes, clips, devices, parameters, browser loading, Max patcher manipulation, and docs. Minor gaps exist (e.g., no arrangement clip envelope editing, no project save/export), but the core workflows are well covered.