Skip to main content
Glama
Sign In
eos-mcp-server

eos-mcp-server

by ReynoldsProductions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to eos-mcp-server

No user-submitted related servers found.

    Related Servers

    • zeros-mcp

      MaybeItsAdam
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for controlling Zero 88 lighting consoles running ZerOS over OSC, exposing playbacks, cues, the grand master, blackout, and user macros as MCP tools.
      12
      MIT

    • Eos MCP

      Nairolf138
      A
      license
      Not graded
      quality
      B
      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.
      4
      AGPL 3.0

    • 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

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

    • MCP3

      emrgim
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to control grandMA3 consoles through official OSC /cmd commands, with an admin UI for IP scanning, object/action permissions, chat integration, and MCP stdio access.
      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.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a distinct purpose: firing cues vs macros vs advancing playback, recording vs selecting cues, setting levels vs parameters vs faders vs nudging, and a raw command escape hatch. The descriptions explicitly clarify potential overlaps (e.g., eos_fire_cue vs eos_go).

    Naming Consistency5/5

    All tools follow a consistent eos_verb_noun pattern in snake_case, e.g., eos_fire_cue, eos_record_cue, eos_set_channel_level, eos_get_status. No mixed conventions or vague verbs.

    Tool Count5/5

    13 tools is well-scoped for a lighting console control server, covering the main workflows (playback, recording, channel/parameter control, faders, status) without excessive granularity or unnecessary omissions.

    Completeness4/5

    Core lifecycle is covered: cue playback (fire, go), recording (record, select), channel/parameter control (set, nudge), fader management, and a raw command escape hatch for anything else. Minor gaps like no explicit delete cue or show save/load exist, but they are workaroundable via raw commands.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources