Skip to main content
Glama
gschian0

av-conductor

by gschian0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to av-conductor

No user-submitted related servers found.

    Related Servers

    • Ableton MCP

      keigotak
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language control over Ableton Live for generating musical patterns, melodies, and full song arrangements. It also provides tools for sample searching and mixing assistance through an OSC-based connection with Claude Desktop.
      1
      MIT

    • WING Rack MCP

      dwrightii
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to discover and connect to Behringer digital mixers over OSC, read and write parameters, dump subtrees to show files, and push edited files back to the desk.
      MIT

    • LiveMCP

      dsgarage
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to control Ableton Live directly through a Max for Live device, letting users read set state, search samples, place clips, build Drum Racks, adjust device parameters, and generate .als project files from sample packs without launching Live.
      10 npm
      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
    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

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: save/recall cues, raw OSC escape, full rebroadcast, state query, scene update, and time-based ramping. No two tools overlap in function or would cause misselection.

    Naming Consistency4/5

    Names are consistently snake_case and mostly follow a verb_noun pattern (save_cue, recall_cue, send_osc, get_state, set_scene, resend_all). The lone 'ramp' breaks the pattern slightly, but the overall convention is clear.

    Tool Count5/5

    Seven tools are well-scoped for an AV conductor, covering scene management, cue handling, OSC messaging, and ramping without bloat. Each tool earns its place.

    Completeness3/5

    Core lifecycle is present (create/read/update for scenes and cues), but notable gaps exist: no tool to delete or overwrite cues explicitly, and no way to cancel or stop an active ramp. These are common AV operations that agents cannot perform directly.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources