Skip to main content
Glama
Dysron

Ableton MCP

by Dysron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
test_connectionA

Test if Ableton Live is running and AbletonOSC is enabled.

list_tracksC
List all tracks in the current Ableton Live session.

Args:
    include_clips: If True, include clip count for each track

Returns:
    Formatted list of tracks with their properties
list_groupsA

List all group tracks (folders) in the current Live session.

get_track_infoB
Get detailed information about a specific track.

Args:
    track_index: The index of the track (0-based)

Returns:
    Track details including name, type, mute status, and clips
find_trackB
Find tracks by name (partial match).

Args:
    name: Text to search for in track names

Returns:
    List of matching tracks
select_track_by_indexB
Select a track in Ableton Live.

Args:
    track_index: The index of the track to select (0-based)

Returns:
    Confirmation message
set_export_rangeC
Set the loop/punch range for export.

Args:
    start_beats: Start position in beats
    length_beats: Length in beats

Returns:
    Confirmation with time info
export_selected_trackA
Export the currently selected track using GUI automation.

IMPORTANT: Requires Accessibility permissions for Terminal/Python.
macOS only.

Args:
    output_folder: Where to save the exported file

Returns:
    Status message
prepare_track_for_exportA
Prepare a track for export by selecting it and setting the loop range
based on its audio clips.

Args:
    track_index: The index of the track to prepare

Returns:
    Status with range info, ready for export_selected_track

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between 'find_track' and 'list_tracks' that could cause confusion, as both involve retrieving track information. However, their specific functions (search vs. list all) are clarified in descriptions, preventing major misselection issues.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear verb_noun structure, such as 'export_selected_track', 'find_track', and 'list_tracks'. This predictability makes it easy for agents to understand and use the toolset without naming confusion.

Tool Count5/5

With 9 tools, the server is well-scoped for managing Ableton Live tracks, covering operations like listing, finding, selecting, preparing, and exporting. Each tool serves a specific role without unnecessary redundancy, making the count appropriate for the domain.

Completeness4/5

The toolset provides good coverage for track management and export workflows, including preparation and range setting. However, there are minor gaps, such as no tools for modifying track properties (e.g., mute, volume) or handling non-track elements like clips or effects, which agents might need to work around.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources