Skip to main content
Glama
jpoindexter

ableton-mcp

by jpoindexter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ableton-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • AbletonMCP

      ahujasid
      A
      license
      B
      quality
      C
      maintenance
      Connects Ableton Live to Claude AI through the Model Context Protocol, enabling AI-assisted music production by allowing Claude to directly interact with and control Ableton Live sessions.
      16
      5,631 PyPI
      3,082
      MIT

    • AbletonMCP

      FreeRiverHouse
      A
      license
      B
      quality
      D
      maintenance
      Connects Ableton Live to Claude AI via the Model Context Protocol for prompt-assisted music production and session manipulation. It enables users to create tracks, load instruments, and manage MIDI clips using natural language commands.
      16
      1
      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

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

    Scored across 128 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there are clear overlaps: load_instrument_or_effect and load_item_to_track both load instruments/effects onto a track via URI, and browse_path and get_browser_items_at_path both navigate the browser by path. These duplicates create ambiguity for agents.

    Naming Consistency4/5

    The vast majority follow a consistent verb_noun pattern (get_*, set_*, create_*, delete_*, etc.) in snake_case. Minor outliers like 'undo', 'redo', and 'health_check' deviate slightly but don't break the overall pattern.

    Tool Count1/5

    128 tools is far beyond even the 50+ extreme threshold. While Ableton has a rich feature set, this granularity (e.g., separate humanize_timing and humanize_velocity, separate get_clip_gain and set_clip_gain) makes the server unwieldy and difficult for agents to navigate effectively.

    Completeness4/5

    The tool surface is remarkably comprehensive, covering track, clip, scene, device, routing, browser, transport, automation, warp, and groove functionality. Minor gaps like session save/export or locator movement exist, but they are not critical to core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources