Skip to main content
Glama
wstierhout

AbletonMCP

by wstierhout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AbletonMCP

No user-submitted related servers found.

    Related Servers

    • ableton-mcp

      amamparo
      F
      license
      B
      quality
      D
      maintenance
      MCP server for controlling Ableton Live, enabling AI assistants to interact with Live sessions through tools for track/clip/scene management, playback control, and device parameter adjustments.
      48
      -

    • ableton-mcp

      ku1x
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to control Ableton Live through MCP, allowing MIDI writing, audio import, device parameter adjustment, clip arrangement, and playback control over a localhost-only connection.
      37
      MIT

    • hellyee

      guvense
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that enables natural language control of Ableton Live for music production, including track, clip, device, automation, and mixing operations.
      7
      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

    A3.7/5.0

    Scored across 156 tools

    Disambiguation3/5

    Most tools target clearly distinct resources (track vs clip vs device vs return), and the descriptions are exemplary at cross-referencing alternatives. However, several overlapping clusters remain - four drum-pattern writers (generate_drum_pattern, generate_groove, generate_euclidean_drums, write_drum_grid), three chord generators, and two bass generators - where an agent must read carefully to avoid misselection.

    Naming Consistency4/5

    Naming is overwhelmingly systematic: snake_case, verb-first, with predictable family prefixes (get_, set_, create_, delete_, generate_, als_, adg_) across nearly all 156 tools. Minor deviations include noun-style commands (batch_commands, clip_operation, session_diff) and the jump_by vs jump_to_* split.

    Tool Count2/5

    156 tools far exceeds the well-scoped range, and despite Ableton Live's genuinely broad domain, there is significant redundancy (4 drum writers, 3 chord writers, 4 key detectors, 3 parameter-setter variants). This volume imposes heavy context costs and makes every tool selection a high-cardinality decision.

    Completeness4/5

    The surface is remarkably complete: tracks, clips, devices, transport, browser, automation, MIDI generation, live analysis, and offline .als/.adg inspection are all covered with full lifecycles. Minor gaps exist - no final render/export to disk, no arrangement clip move/trim/split, and automation can only be written/cleared, not read back - but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources