Skip to main content
Glama
MaybeItsAdam

zeros-mcp

by MaybeItsAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to zeros-mcp

No user-submitted related servers found.

    Related Servers

    • GMA2 MCP

      chienchuanw
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that lets AI assistants control grandMA2 lighting consoles via Telnet, exposing 41 high-level tools for cue management, fixture control, preset management, executor control, macro editing, appearance assignment, bulk operations, console state queries, show file management, read-back verification, and music show workflows.
      100
      15
      Apache 2.0

    • Eos MCP

      Nairolf138
      A
      license
      Not graded
      quality
      A
      maintenance
      Transforms an ETC Eos lighting console into a service controllable by AI assistants and automation tools via MCP and OSC, enabling cue management, preset recall, and channel level control.
      2
      AGPL 3.0

    • ableton-mcp

      sketchymeow
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server to control Ableton Live via the Live API, offering curated tools for transport, tracks, clips, devices, automation, and more, plus a generic layer to access the entire Live Object Model.
      MIT

    • OSC MCP Server

      darkwings
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling Behringer X-Air digital mixers via OSC, with symbolic naming and dB-to-float conversion.
      19
      1
      Apache 2.0

    • voicemeeter-mcp

      aaronckj
      A
      license
      B
      quality
      B
      maintenance
      An MCP server for controlling Voicemeeter (Basic, Banana, or Potato) on Windows: strip and bus gains, mutes, output routing, live levels, macro buttons, presets, and audio-engine restarts.
      17
      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

    A4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: set_ commands target different parameters, get_ commands retrieve different information, and playback controls are separated by action (pause, release, view, level). The only potential overlap is between fire_cue and go_cue, but the descriptions clarify that one runs a specific cue while the other advances to the next cue.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern with useful prefixes (set_, get_, fire_). Minor deviations exist, such as go_cue versus fire_cue and pause_playback/release_playback/view_playback, but the overall naming is predictable and readable.

    Tool Count5/5

    With 12 tools, the server is well-scoped for controlling a lighting console. It covers cue firing, playback management, levels, blackout, macros, and diagnostics without unnecessary bloat.

    Completeness4/5

    The set covers the essential live-control operations (cues, playbacks, grand master, blackout, macros) plus useful diagnostics. The main gap is the inability to read console state—only command history is available—but this is a documented protocol limitation, so it's an acceptable minor gap.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources