Skip to main content
Glama
Sign In
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ableton-mcp

No user-submitted related servers found.

    Related Servers

    • FORGE

      croresnos
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables exposing any REST or GraphQL API as MCP tools from a single JSON spec, with writes requiring explicit confirmation before being sent.
      MIT

    • Ableton Live MCP

      ulm0
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to programmatically control an Ableton Live 12 session, including tracks, clips, MIDI notes, devices, parameters, mixer, scenes, warping, and rendering, over streamable HTTP.
      1
      MIT

    • Ableton Producer MCP

      kovtun-oleksii
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      MIT

    • Live Bridge

      aoe1928
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Ableton Live through a Max for Live device and optional Remote Script, covering tracks, clips, MIDI notes, mixer settings, transport, and plugin search and insertion.
      1
      MIT

    • ableton-agent-mcp

      ju5tinz
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that exposes Ableton Live control (session state, transport, tracks, devices, clips, MIDI note editing) as tools for LLM agents, enabling natural language manipulation of a Live session.
      1
      MIT
    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

    B3.1/5.0

    Scored across 328 tools

    Disambiguation2/5

    With 328 tools, many near-duplicate or overlapping operations exist, such as get_midi_clip_notes vs get_midi_clip_notes_extended, multiple get_*_context readers, and large plan/apply/context triplets for the same domain. Descriptions are unusually detailed and often distinguish safe read-only vs guarded write behavior, but the sheer number of similarly named context, plan, apply, and status tools makes tool selection error-prone.

    Naming Consistency4/5

    The tool set overwhelmingly uses consistent snake_case with predictable verb_noun patterns like get_*, set_*, list_*, create_*, plan_*, apply_*, and delete_*. There are minor deviations such as panic, undo, redo, transport_play, and transport_stop, but the convention remains readable throughout.

    Tool Count1/5

    328 tools is an extreme mismatch for practical agent use and far exceeds any reasonable scoped tool surface. Even for a complex DAW, this many narrowly separated tools creates enormous selection overhead and makes the set unwieldy despite each tool potentially earning its place in some workflow.

    Completeness4/5

    The surface covers an enormous range of Ableton Live operations: tracks, clips, devices, racks, mixer, transport, browser, presets, recording, automation, export, and snapshots. Some gaps remain, such as native groove deletion and hidden plug-in state, but these are largely explicit API limitations with documented workarounds.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources