Skip to main content
Glama
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
      C
      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
      B
      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.
      MIT

    • ableton-agent-mcp

      ju5tinz
      A
      license
      Not graded
      quality
      B
      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 183 tools

    Disambiguation3/5

    Many tools are clearly distinct (e.g., list_tracks vs set_tempo), but there are numerous near-duplicate pairs like plan_midi_velocity_curve vs apply_midi_velocity_curve, or capture_track_state_snapshot vs save_track_state_snapshot, that could confuse an agent. The detailed descriptions help, but the sheer volume of 183 tools makes misselection likely without careful reading.

    Naming Consistency3/5

    Names are mostly snake_case with a verb-first pattern, but the convention is mixed: some actions are split into plan_* and apply_* pairs, while others use a single verb like set_* that covers both planning and applying. Exceptions like panic, undo, redo, and transport_play break the noun/verb pattern slightly. It is readable but not fully consistent.

    Tool Count1/5

    With 183 tools, the server is extremely over-scoped. Even for a complex DAW like Ableton Live, this many tools creates unreasonable context bloat and choice overload for an agent. The rubric explicitly marks 50+ as an extreme mismatch, and this is nearly four times that.

    Completeness5/5

    The tool surface covers an exceptionally broad range of Ableton Live functionality: tracks, devices, clips, automation, browser/presets, MIDI transformation, audio warp, transport, scenes, snapshots, routing, and specialized device contexts. There are no obvious dead ends; nearly every action has both planning and execution paths, and analysis/inspection tools are paired with mutating operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources