Schema | ableton-mcp

ableton-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
get_session_overviewB	Tempo, time signature, and summary of every track.
get_track_detailB	Devices, clip slots, and routing for one track.
get_clip_notesB	MIDI notes in a clip: pitch, start (beats), duration, velocity.
get_transport_stateB	Transport state: playing, current beat, loop.
get_selectedA	What the user currently has selected in Live. Call this first when the user asks 'what is this?'.
create_midi_clipC	Create a MIDI clip and fill with notes. Use this when the user wants a musical idea written into the set.
modify_clip_notesC	Replace all notes in an existing MIDI clip.
set_tempoC	Set song tempo (BPM).
set_time_signatureC	Set song time signature.
create_trackC	Create a new MIDI or audio track at end of set.
fire_clipA	Start playing a clip. ASK THE USER FIRST before calling — surprise playback is disruptive.
stop_clipC	Stop a clip.
explain_shortcutB	Look up an Ableton Live keyboard shortcut by action name.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrinalghosh/ableton-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server