Skip to main content
Glama
Sign In
Ableton Producer MCP

Ableton Producer MCP

by kovtun-oleksii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Ableton Producer MCP

No user-submitted related servers found.

    Related Servers

    • AbletonMCP

      juampicosta
      F
      license
      B
      quality
      D
      maintenance
      Control Ableton Live from Claude Code via the Model Context Protocol (MCP). Create/edit tracks, control plugins, fire clips, edit MIDI notes, capture audio — all through natural language.
      100
      -

    • Ableton MCP for Live Intro

      untitledxdamage
      A
      license
      C
      quality
      B
      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

    • AbletonMCP

      Milesy1
      A
      license
      C
      quality
      D
      maintenance
      Connects Claude AI to Ableton Live through the Model Context Protocol, enabling prompt-assisted music production with track creation, instrument loading, clip editing, and session control. Allows users to create complete musical arrangements by describing what they want in natural language.
      37
      3
      MIT

    • AbletonMCP

      fastmcp-me
      A
      license
      B
      quality
      D
      maintenance
      Connects Ableton Live to Claude AI via the Model Context Protocol, enabling prompt-assisted music production, track creation, and Live session manipulation.
      16
      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.3/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (clip notes, device params, transport, arrangement automation), and the session/arrangement automation trio is well delineated by the clip_view/scope parameters. The fuzzy spots are device loading (insert_device vs load_instrument_or_effect vs load_drum_kit), snapshot vs session/track info, and the preference-logging cluster (rate_last_action vs reject_last_action vs prefer_candidate) which agents could easily confuse.

    Naming Consistency4/5

    Nearly everything is consistent snake_case verb-first (get_*, set_*, create_*, clear_*, delete_*, load_*), with arrangement variants named predictably against session variants. Minor deviations are duplicate_to_arrangement (object trails awkwardly) and mixed-style oddities like prefer_candidate and get_remote_script_info, but nothing breaks the pattern.

    Tool Count2/5

    43 tools is well past the heavy threshold, and a meaningful chunk is not DAW control at all: five+ telemetry/preference instruments (submit_intent, rate_last_action, prefer_candidate, reject_last_action, record_audition, set_dataset_consent), a handshake tool, and a pure UI tool (switch_to_arrangement_view). The musical surface alone would be reasonable, but the research-instrumentation layer inflates the set.

    Completeness3/5

    Core workflows (tracks, clips, MIDI notes, devices, browser, automation, locators) are covered end-to-end with read/modify/write loops supported via clear_notes_from_clip. However there are notable gaps: no delete_track or track volume/pan/send setters outside automation, no scene/fire-scene management, no device removal, no clip loop/color/warp controls, and no undo — real dead ends for common mixing and arrangement tasks.

    Resources