Skip to main content
Glama
ntworm

Ableton MCP Server

by ntworm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Ableton MCP Server

No user-submitted related servers found.

    Related Servers

    • Ableton Live MCP Server

      whybothercoding
      A
      license
      A
      quality
      A
      maintenance
      Enables an MCP client to inspect and modify a running digital audio workstation session through a local Python remote-script TCP bridge, exposing tools for session and track structure, clip slots and MIDI notes, devices and browser items, and mixer/transport control. Read and bulk-write operations cover tempo, naming, clip creation and note editing, muting/soloing/arming, playback and scene launching, and device parameter loading and adjustment.
      32
      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
      10 npm
      MIT

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

    Disambiguation2/5

    Several read/snapshot tools overlap heavily (get_session_overview, get_session_info, get_track_state, take_snapshot, get_composition_structure) and clip/device queries plus analysis/generation tools have nearby scopes. Descriptions help, but at 97 tools an agent will frequently struggle to pick the right one.

    Naming Consistency3/5

    Names are mostly snake_case, but the set mixes patterns: get_, list_, live_find_, diagnose_, music_generate_, groove_, set_, create_, and a stray diff_snapshots_tool. Readable, yet not a single predictable verb_noun convention.

    Tool Count1/5

    97 tools is far beyond a well-scoped MCP surface (typical 3-15). Many are niche diagnostics, capability-refusal stubs, or overlapping read helpers, making the server heavy and hard to navigate.

    Completeness3/5

    Coverage is broad across session/transport, tracks, clips, devices, browser, automation, audio analysis, generation, and extension workflows. However, obvious lifecycle gaps remain: no scene create/delete/rename, no track deletion, and no direct clip-stop operation.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources