Skip to main content
Glama
bbernstein

LacyLights MCP Server

by bbernstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to LacyLights MCP Server

No user-submitted related servers found.

    Related Servers

    • light-mcp-server

      bawaaaaah
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-driven control of Art-Net/sACN DMX lighting, including scenes, effects, groups, safety rules, MIDI/OSC, and Ableton Live integration through a unified command layer.
      MIT

    • grandMA2 Universal MCP Server

      vandiy064-byte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control grandMA2 onPC or physical consoles through natural-language commands for live fixture control, cue and preset programming, macros, timecode automation, diagnostics, and live show administration.
      1
      MIT

    • 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.
      3
      AGPL 3.0

    • 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
      16
      Apache 2.0

    • MADRIX MCP

      drohi-r
      A
      license
      D
      quality
      D
      maintenance
      Enables AI-driven control of MADRIX LED lighting software, providing over 100 tools for storage, layer, cue list, timeline, audio, output, and color management via the MADRIX Remote HTTP interface.
      100
      5
      Apache 2.0
    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

    C2.9/5.0

    Scored across 102 tools

    Disambiguation3/5

    Many tools target distinct resources, but the set contains numerous near-duplicate pairs such as update_look vs update_look_partial, bulk_update_looks vs bulk_update_looks_partial, and get_look vs get_look_fixtures vs get_look_fixture_values. Long descriptions often help, but the sheer number of bulk_-prefixed variants and subtle semantic differences creates real misselection risk.

    Naming Consistency4/5

    Nearly all tool names use snake_case with a consistent verb_noun or verb_noun_prep_noun pattern, including the bulk_ prefix. A few names deviate from the pattern (undo, redo, next_cue, previous_cue, qlc_import_guidance), but the overall convention is predictable.

    Tool Count1/5

    102 tools is far beyond a reasonable scope for an MCP server and is bloated with redundant bulk operations and many near-duplicate single/bulk/partial variants. This extreme count creates severe cognitive load and makes tool selection unnecessarily difficult.

    Completeness3/5

    Core lighting entities (projects, fixtures, looks, cues, cue lists, look boards) have extensive CRUD, bulk, import/export, undo/redo, and playback coverage. However, there are notable gaps: group invitations cannot be accepted or declined, and descriptions reference get_fixture_usage and get_look_usage tools that are not present, leaving dead ends in access-control and usage analysis.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources