Skip to main content
Glama
Sign In
verove-jordan

ableton12-mcp

by verove-jordan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ableton12-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
      -

    • 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

    • ableton-live-mcp

      jterratsdev
      A
      license
      B
      quality
      B
      maintenance
      Local MCP server for inspecting and controlling Ableton Live through a local HTTP bridge. Enables LLMs to perform production workflows like MIDI import, track editing, mixing, mastering, and export.
      59
      21 npm
      MIT

    • Ableton MCP – Technoa edition

      macymm86
      A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server lets an AI assistant inspect and safely modify a whole Live set—tracks, groups, returns, master, routing, automation, clips, devices, dBFS meters, snapshots, and undo—while leaving listening to the producer.
      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.4/5.0

    Scored across 62 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, but there is some intentional overlap between get_device_parameters/get_macros and set_device_parameter/set_macro, and record_and_analyze is a composite of record_audio and analyze_audio. These are documented clearly enough to avoid confusion in practice.

    Naming Consistency5/5

    Tool names overwhelmingly follow a verb_noun snake_case pattern (e.g., create_midi_track, set_device_parameter, delete_scene). Minor exceptions like health, new_live_set, and save_set_as are still readable and do not disrupt the overall predictability.

    Tool Count2/5

    At 62 tools, the server is far beyond the 25+ threshold that indicates an over-heavy toolset. While Ableton is a complex domain, the count feels overwhelming and many tools could be consolidated (e.g., record_and_analyze already merges two).

    Completeness4/5

    The toolset covers the full creative workflow: session/track/clip management, device control, scenes, transport, audio capture, analysis, and comparison. The main gap is that export is not fully automated—open_export_dialog requires manual confirmation—but the capture-to-arrangement path fills most of the pipeline.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources