Skip to main content
Glama
kevinzhang03

Ableton MCP Extended

by kevinzhang03
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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_session_infoA

Get detailed information about the current Ableton session

get_track_infoC
Get detailed information about a specific track in Ableton.

Parameters:
- track_index: The index of the track to get information about
create_midi_trackB
Create a new MIDI track in the Ableton session.

Parameters:
- index: The index to insert the track at (-1 = end of list)
set_track_nameB
Set the name of a track.

Parameters:
- track_index: The index of the track to rename
- name: The new name for the track
create_clipA
Create a new MIDI clip in the specified track and clip slot.

Parameters:
- track_index: The index of the track to create the clip in
- clip_index: The index of the clip slot to create the clip in
- length: The length of the clip in beats (default: 4.0)
add_notes_to_clipC
Add MIDI notes to a clip.

Parameters:
- track_index: The index of the track containing the clip
- clip_index: The index of the clip slot containing the clip
- notes: List of note dictionaries, each with pitch, start_time, duration, velocity, and mute
set_clip_nameB
Set the name of a clip.

Parameters:
- track_index: The index of the track containing the clip
- clip_index: The index of the clip slot containing the clip
- name: The new name for the clip
set_tempoC
Set the tempo of the Ableton session.

Parameters:
- tempo: The new tempo in BPM
load_instrument_or_effectB
Load an instrument or effect onto a track using its URI.

Parameters:
- track_index: The index of the track to load the instrument on
- uri: The URI of the instrument or effect to load (e.g., 'query:Synths#Instrument%20Rack:Bass:FileId_5116')
fire_clipC
Start playing a clip.

Parameters:
- track_index: The index of the track containing the clip
- clip_index: The index of the clip slot containing the clip
stop_clipB
Stop playing a clip.

Parameters:
- track_index: The index of the track containing the clip
- clip_index: The index of the clip slot containing the clip
start_playbackB

Start playing the Ableton session.

stop_playbackB

Stop playing the Ableton session.

get_browser_treeB
Get a hierarchical tree of browser categories from Ableton.

Parameters:
- category_type: Type of categories to get ('all', 'instruments', 'sounds', 'drums', 'audio_effects', 'midi_effects')
get_browser_items_at_pathA
Get browser items at a specific path in Ableton's browser.

Parameters:
- path: Path in the format "category/folder/subfolder"
        where category is one of the available browser categories in Ableton
load_drum_kitB
Load a drum rack and then load a specific drum kit into it.

Parameters:
- track_index: The index of the track to load on
- rack_uri: The URI of the drum rack to load (e.g., 'Drums/Drum Rack')
- kit_path: Path to the drum kit inside the browser (e.g., 'drums/acoustic/kit1')

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 16 tools

Disambiguation4/5

Most tools have distinct purposes, such as create_clip vs. add_notes_to_clip, but there is some potential overlap between fire_clip and start_playback, as both initiate playback in different contexts. The descriptions clarify that fire_clip targets specific clips while start_playback controls the entire session, but an agent might occasionally confuse them without careful reading.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, such as create_clip, get_session_info, and set_tempo. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions across the 16 tools.

Tool Count4/5

With 16 tools, the server is slightly on the heavier side but remains reasonable for controlling an Ableton session, covering essential operations like clip management, track creation, and playback control. It avoids being overwhelming while providing comprehensive functionality, though it could be streamlined by merging closely related tools like start_playback and stop_playback into a single toggle.

Completeness4/5

The tool set covers key aspects of Ableton control, including clip and track manipulation, browser navigation, and session playback, but has minor gaps such as missing update or delete operations for clips or tracks. Agents can work around these omissions by combining existing tools, but the lack of direct modification tools may limit efficiency in some workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources