laive-mcp is strongest today in Session View. The bridge-backed MCP surface has been validated against a real Ableton Live session, not just fixture mode.
get_project_summaryget_selected_contextlist_trackslist_mixer_trackslist_return_tracksget_master_trackget_track_detailsget_device_treerefresh_stateget_capabilities
These let an agent inspect the current set, mixer topology, clips, devices, parameters, and selected context.
set_tempoplay_transportstop_transportcreate_trackcreate_scenecreate_cliprename_clipmove_session_clipset_clip_loop_or_lengthduplicate_clipdelete_clipinsert_notesreplace_noteslaunch_cliplaunch_scenestop_track_clipsstop_all_clips
This is the current core music-making surface.
get_arrangement_summaryget_arrangement_track_detailsset_arrangement_transportjump_to_arrangement_clipselect_clipcreate_arrangement_clipduplicate_clip_to_arrangementduplicate_arrangement_cliprename_arrangement_clipmove_arrangement_clipset_arrangement_clip_boundssplit_arrangement_clipdelete_arrangement_clip
The current v0.7.0 slice now includes:
- arrangement clip enumeration now flows through track details and arrangement summaries
- arrangement clip selection and jump helpers, with arrangement-aware
get_selected_contextreadback - arrangement clip creation on visible tracks
- session-to-arrangement clip duplication
- arrangement-to-arrangement clip duplication
- arrangement-focused rename/delete wrappers on the MCP surface
- explicit arrangement clip movement
- explicit arrangement clip bound editing with start/end beat control
- MIDI arrangement clip splitting with trimmed left/right note timing
- song readback now includes Arrangement transport position plus loop start, length, and enabled state
- arrangement loop and transport-region control is exposed without requiring the Session View surface
Next up beyond v0.7.0:
- deeper arrangement navigation and automation helpers beyond selection/jump/transport control
- clip-envelope read/write in
v0.8.0
create_return_trackset_track_volumeset_track_panningset_send_levelset_monitor_stateset_track_routing
The current mixer slice also includes:
- return-track and master-track discovery
- return/master device targeting
- alias-aware send and routing resolution against the live-advertised choices
- readback of available routing choices and send metadata in track details
get_browser_treeget_browser_itemsload_browser_itemset_parameter
Parameter writes support:
- lookup by track/device/parameter name
- enum-label targeting for quantized parameters when metadata is available
The sidecar is optional. It is not the main bridge.
Current sidecar-related tools:
get_component_statuslist_sidecar_workflowsrun_sidecar_workflowensure_sidecar_on_tracksidecar_snapshot_selection_contextsidecar_transform_selected_clipsidecar_replace_clip_notessidecar_capture_device_snapshotsidecar_apply_device_snapshotsidecar_observe_device_parameters
If the sidecar is not installed or not active in the set, laive returns structured setup guidance instead of silently failing.
Current sidecar workflow focus:
- selected-clip note transforms on the currently selected MIDI clip
- selected or explicitly targeted device-parameter snapshots
- applying previously captured device snapshots back onto a device
- selected-context snapshots and device observation
The UI helper is also optional and used as a fallback for workflows that are awkward or unavailable through the primary bridge.
Current UI-helper-related tools:
list_ui_workflowsrun_ui_workflowui_browser_search_and_loadui_capture_contextui_export_audio_videoui_export_with_presetui_focus_section
If Accessibility is not granted or the helper is not installed, laive returns setup guidance.
- Arrangement View is exposed through first-class MCP tools, but higher-level composition/navigation abstractions are still thin.
- Clip-envelope editing currently focuses on Session clips. Arrangement clips expose target discovery and selection, but real Live 11 rejects envelope creation through the current Remote Script API path.
- The sidecar is complementary, not required for the main control path.
- The UI helper is a fallback, not the preferred path.
For planned follow-up work:
For the lower-level tool list: