Skip to main content
Glama
ku1x

ableton-mcp

by ku1x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ableton-mcp

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
      -

    • AbletonMCP

      wstierhout
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI assistants to control Ableton Live, providing 104 tools for music production including track, clip, device, and mixer control.
      156
      440 PyPI
      25
      MIT

    • LiveBrain MCP

      Fasping
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control Ableton Live 12 for music production, including generating grooves, basslines, and percussion, and executing live set operations through MCP.
      3
      2
      MIT

    • LivePilot

      Toblaron
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI clients to Ableton Live 12, enabling deep control and editing of live sets, sound search, listening/evaluation, and version exploration through MCP tools.
      561 npm
      Business Source 1.1

    • ableton-control-deck

      remymazmanian
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP bridge that enables AI agents to read and control Ableton Live sessions with read-back verification, including tracks, clips, transport, devices, and third-party plug-in parameters.
      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.2/5.0

    Scored across 37 tools

    Disambiguation3/5

    Most DAW tools have clear targets, but several clusters are close: get_session_info vs get_session_snapshot, create_clip vs create_audio_clip, load_instrument_or_effect vs load_drum_kit, and the preference/trajectory tools (reject_last_action, rate_last_action, prefer_candidate, record_audition) overlap in purpose. Descriptions clarify the differences, but an agent could easily misselect without reading them carefully.

    Naming Consistency4/5

    Tool names overwhelmingly follow a clear verb_noun snake_case pattern: get_*, create_*, set_*, start_*, stop_*, fire_*, delete_*, load_*. Minor deviations exist, like create_clip lacking 'midi' while create_audio_clip explicitly says audio, and a few telemetry tools (prefer_candidate, record_audition, submit_intent) using varied verbs, but the overall pattern is coherent.

    Tool Count2/5

    At 37 tools, this is a large surface. A sizable subset consists of telemetry, consent, snapshot, intent, and preference-logging tools that are not core Ableton operations, making the set feel bloated and harder to navigate than necessary.

    Completeness3/5

    The core workflow is fairly well covered: clips can be created, populated, cleared, read, named, fired, stopped, deleted, and duplicated to arrangement; devices and browser browsing are covered. However, notable gaps remain, including no delete track, no mixer/solo/mute/volume/pan control beyond device parameters, no arrangement clip deletion/moving, and no locator deletion or listing, so some likely workflows end in dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources