Skip to main content
Glama
IMNMV

AbletonMCP

by IMNMV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to AbletonMCP

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
      1,771 PyPI
      3,082
      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

      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

    • ableton-mcp

      jpoindexter
      A
      license
      B
      quality
      F
      maintenance
      Connects Ableton Live to Claude AI through the Model Context Protocol, enabling AI-assisted music production and Live session manipulation via over 200 tools.
      100
      53
      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 16 tools

    Disambiguation5/5

    Each tool has a distinct purpose: clip operations (create, add notes, fire, stop, name), track operations (create, get info, rename), browser browsing, instrument loading, tempo, and playback control. There is no ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, e.g., 'add_notes_to_clip', 'create_midi_track', 'get_session_info'. No mixing of conventions.

    Tool Count5/5

    With 16 tools, the server covers core Ableton operations comprehensively without being excessive. Each tool serves a clear and necessary role in session management.

    Completeness3/5

    The tool set covers creation and basic manipulation but lacks delete operations for tracks and clips, and does not include mixer controls (volume, pan, mute) or scene management. Notable gaps exist but core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources