AbletonMCP
Related Servers
Alternatives to AbletonMCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables natural language control of Ableton Live through Claude, including session management, track and clip creation, device parameter adjustment, and browser browsing.1-
- AlicenseBqualityBmaintenanceEnables Claude or any MCP client to produce full tracks in Ableton Live from chat: building tracks, writing MIDI notes, loading and tweaking device parameters, arranging sections, and drawing real clip and Arrangement automation. It also exposes mixer state snapshots and clip editing so a live set can be inspected and reshaped end to end.43MIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude AI to control Ableton Live and Max for Live, allowing music production tasks like track management, MIDI editing, and pattern generation directly from conversation.-
- AlicenseNot gradedqualityDmaintenanceEnables natural language control over Ableton Live for generating musical patterns, melodies, and full song arrangements. It also provides tools for sample searching and mixing assistance through an OSC-based connection with Claude Desktop.1MIT
- AlicenseCqualityDmaintenanceConnects Ableton Live to Claude AI, enabling prompt-assisted music production, track creation, and Live session manipulation.100MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect and edit an Ableton Live set in real time, including tracks, devices, parameters, clips, MIDI, and undo-safe changes, with guardrails such as all-or-nothing validation and optional read-only mode.MIT
TDQS
Scored across 46 tools
Most tools map cleanly to a distinct resource+action (create_midi_track vs create_audio_track, set_clip_name vs set_arrangement_clip_name) and descriptions explicitly disambiguate. The main soft spots are four overlapping read tools (get_session_info, get_session_snapshot, get_tracks_overview, get_track_info), the per-setting set_track_* calls versus the bulk configure_tracks, and fire_clip versus start_playback.
Nearly everything is snake_case with a verb-first pattern (get_*, set_*, create_*, load_*, stop_*, record_*). A few read as noun-first or awkward (fire_clip, switch_to_arrangement_view) and the telemetry tools use a slightly different imperative vocabulary, but the convention is readable and predictable overall.
46 tools is heavy even for a DAW bridge. The six individual track setters (name, color, volume, pan, mute, solo) are all subsumed by configure_tracks, and six further tools are telemetry/preference logging (submit_intent, rate_last_action, prefer_candidate, reject_last_action, record_audition, set_dataset_consent) that sit outside the musical editing surface.
Core workflows are well covered: session reading, track creation, clip lifecycle, notes read/modify/write, device loading and parameters, browser browsing, transport, tempo, arrangement and locators. Notable gaps remain — no delete_track, no return/group track creation, no device or parameter reset/removal, no send-level control, and no way to list a track's devices.