A
licenseNot graded
qualityC
maintenanceA custom Ableton Live MCP focused on keeping sets tidy and creating MIDI that fits material already in the set.
MIT
Ableton MCP
Related Servers
Alternatives to Ableton MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceTurns Ableton Live into an MCP-accessible control surface, providing tools for controlling transport, tracks, clips, and devices, as well as resources for reading live state.1003MIT
- 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-
- FlicenseNot gradedqualityBmaintenanceMCP bridge for Ableton Live with Lyra digital avatar companion, enabling live control, arrangement coaching, MIDI manipulation, and project memory via Producer Pal integration.-
- 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-
- AlicenseBqualityBmaintenanceEnables AI agents to control Ableton Live 12 for music production, including generating grooves, basslines, and percussion, and executing live set operations through MCP.32MIT
TDQS
A3.5/5.0
Scored across 38 tools
Disambiguation4/5
Most tools clearly target distinct resources and actions (tracks, clips, devices, transport, arrangement). A few overlaps exist, such as get_master_track_info duplicating get_track_info with track_kind='master', and load_drum_kit being a specialized version of load_instrument_or_effect, but descriptions help clarify the intended usage.
Naming Consistency4/5
The naming is largely consistent with a verb_noun pattern (get_*, set_*, create_*, delete_*). Minor deviations include 'fire_clip' instead of 'play_clip' or 'start_clip', and 'add_notes_to_clip' uses 'add' instead of 'create'. These are readable but not perfectly uniform.
Tool Count2/5
With 38 tools, the server exceeds the typical MCP scope and falls into the 'too many' category (>25). While the domain of DAW control is broad, many tools could be consolidated or omitted (e.g., get_master_track_info is redundant). This number may overwhelm agents and increase selection difficulty.
Completeness4/5
The tool surface covers core Ableton workflows well: session transport, track management, clip creation and editing, device control, browser navigation, and arrangement placement. Minor gaps exist, such as no way to delete a single arrangement clip (only clear all), no scene management, and no undo/redo, but agents can work around these.
Maintenance
ActivityInactive
ResponsivenessNo issues