Skip to main content
Glama
alaarab

LiveMCP

by alaarab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to LiveMCP

No user-submitted related servers found.

    Related Servers

    • ableton-mcp

      sketchymeow
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server to control Ableton Live via the Live API, offering curated tools for transport, tracks, clips, devices, automation, and more, plus a generic layer to access the entire Live Object Model.
      MIT

    • 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
      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

    • 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
      20 npm
      MIT

    • Enhanced AbletonBridge

      mhzsajan
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI/LLM tools to Ableton Live through 440+ MCP tools spanning tracks, clips, devices, mixer, MIDI mapping, plugin management, video integration, setlists, performance monitoring, and audio analysis. Enables natural-language music production and real-time live show control, including scene firing, preset recall, and emergency stop.
      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 220 tools

    Disambiguation3/5

    Many tools have clear, distinct purposes, but there is notable overlap between pairs like add_notes_to_clip/add_notes_extended, get_notes_from_clip/get_notes_extended, set_track_volume vs set_track_properties, and the various device parameter getters. These overlapping tool pairs create potential misselection, though descriptions do help clarify which to prefer.

    Naming Consistency4/5

    The vast majority of tools follow a consistent snake_case verb_noun pattern (get_track_info, set_track_volume, create_scene). Minor deviations like 'duplicate_to_arrangement', 'trigger_back_to_arrangement', and 'toggle_browse' are few and still readable, so the pattern is largely predictable.

    Tool Count1/5

    With 220 tools, the server far exceeds any reasonable scope for a single MCP instance. Even for a DAW control server, this is an extreme number that will overwhelm agents and make tool selection expensive and error-prone.

    Completeness4/5

    The tool surface covers an extremely wide range of Ableton Live functionality: transport, tracks, scenes, clips, devices, parameters, browser loading, Max patcher manipulation, and docs. Minor gaps exist (e.g., no arrangement clip envelope editing, no project save/export), but the core workflows are well covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources