Skip to main content
Glama
maramasaeva

messier-live

by maramasaeva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to messier-live

No user-submitted related servers found.

    Related Servers

    • Ableton MCP Extension

      t1merickson
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to Ableton Live, inspect the arrangement, compose and edit MIDI, manage tracks/scenes/clips, insert and tweak devices, and control the mixer.
      MIT

    • LiveBrain MCP

      Fasping
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control Ableton Live 12 for music production, including generating grooves, basslines, and percussion, and executing live set operations through MCP.
      3
      2
      MIT

    • Ableton MCP Extended

      kevinzhang03
      A
      license
      A
      quality
      D
      maintenance
      Enables programmatic control of Ableton Live using natural language to manage session transport, tracks, MIDI clips, and device parameters. It also integrates ElevenLabs for AI-generated audio and provides a high-performance framework for real-time performance tools.
      16
      MIT

    • ableton-control-deck

      remymazmanian
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP bridge that enables AI agents to read and control Ableton Live sessions with read-back verification, including tracks, clips, transport, devices, and third-party plug-in parameters.
      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 25 tools

    Disambiguation4/5

    Tools are mostly distinct: live_status is explicitly described as the cheap telemetry option versus get_session_info, and set_fx_macro, fx_sweep, and fx_pulse are differentiated as set/ramp/punch. Minor overlap exists between load_to_deck and prepare_deck, but descriptions clarify the intended use case.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun snake_case pattern like set_fx_macro, fire_deck, and set_device_parameter. There are minor deviations with noun-style names like live_status, deck_status, and crate_list, plus bare verbs like play, stop, and diagnose, but the overall convention remains readable.

    Tool Count3/5

    At 25 tools, this is on the heavy borderline for an MCP server. The broad scope—transport, deck management, FX automation, device parameter control, and crate library—largely justifies each tool, but the set feels slightly bloated and some tools could plausibly be consolidated.

    Completeness4/5

    The core DJ performance workflow is well covered: transport, deck load/fire/stop, volume and crossfade control, FX sweeps and pulses, device parameter escape hatches, and crate-based track suggestions. Minor gaps exist such as no open_project, no direct crossfader position control, and limited non-deck track manipulation, but these do not block the primary use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources