Skip to main content
Glama
elleural

AbletonMCP

by elleural
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AbletonMCP

No user-submitted related servers found.

    Related Servers

    • Ableton MCP for Live Intro

      untitledxdamage
      A
      license
      C
      quality
      A
      maintenance
      Enables Claude or any AI agent to operate Live 12 Intro end to end: creating tracks and scenes, writing and quantizing MIDI clips, loading audio onto the Arrangement timeline, setting device parameters in real units, drawing clip automation, mixing with real sidechain, and rendering or analyzing audio so the agent can check its own work. It exposes 57 tools over MCP or a local JSON socket, working within the stock Intro edition's 16-track, 16-scene limits.
      57
      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
      B
      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.
      622 npm
      Business Source 1.1

    • 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

    • ableton-mcp-lofifren

      LofiFren
      A
      license
      B
      quality
      B
      maintenance
      Connects Ableton Live to AI through MCP, enabling prompt-assisted music production with extended tools and a 33-personality style system for generating parts in various artist styles.
      62
      5
      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.5/5.0

    Scored across 78 tools

    Disambiguation3/5

    The set is massive (78 tools), and while most tools target distinct resources/actions, there are overlapping areas such as set_device vs set_device_parameters, get_device vs get_devices, and catch-all tools (clip_action, device_action, lom_*) that duplicate or extend narrower tools. Descriptions are detailed but an agent could still misselect among the many options.

    Naming Consistency4/5

    Names are overwhelmingly snake_case and follow verb_noun or noun_action patterns (create_track, get_clip, set_mixer), with clear grouping prefixes (get_, set_, create_, delete_, duplicate_, move_). Minor deviations like new_set, transport, select, bounce, music_theory, and lom_* prefixes are readable but not perfectly uniform.

    Tool Count1/5

    78 tools is extreme for any server; even a complex DAW control surface can be consolidated. This far exceeds the 50+ threshold for severe mismatch, likely overwhelming an agent and reducing usability.

    Completeness5/5

    The surface covers set management, tracks, clips, notes, devices, mixer, routing, browser, automation, arrangement, bounce, release, and audio analysis, plus a LOM fallback for anything missing. This is effectively complete for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources