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

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

    • GMA2 MCP

      chienchuanw
      A
      license
      B
      quality
      C
      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
      14
      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
      3
      Apache 2.0

    • hcl-mcp

      akontadakis
      F
      license
      B
      quality
      C
      maintenance
      Enables natural-language-driven human-centric lighting analysis, including CIE S 026 α-opic and circadian metrics, spectral sky reconstruction from EPW files, and Radiance daylight/electric/glare simulation.
      51
      -

    • MCP ETC Nomad

      eva-akselrad
      A
      license
      C
      quality
      B
      maintenance
      Enables LLM control of ETC Eos Family lighting consoles via OSC, allowing operation of cues, levels, subs, macros, and the full Eos command line.
      20
      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.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., list_projects vs. create_project vs. delete_project), but a few pairs like optimize_scene/update_scene and generate_act_cues/create_cue_sequence could cause confusion if descriptions are not explicit. Overall, the boundaries are mostly clear.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., list_projects, create_fixture_instance, optimize_cue_timing). No mixed conventions or vague verbs are present.

    Tool Count3/5

    With 24 tools, the set feels heavy for a single server, but it covers multiple subdomains (projects, fixtures, scenes, cues, script analysis) where each tool has a specific role. It is within the 16-25 heavy range, so not ideal but not extreme.

    Completeness4/5

    Core CRUD and analysis operations are well-covered for projects, fixtures, scenes, and cues. Minor gaps exist such as missing delete operations for fixtures and scenes, and no update_project, but these are not critical to the main workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources