MCP ETC Nomad
Related Servers
Alternatives to MCP ETC Nomad
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceTransforms 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.3AGPL 3.0
- FlicenseAqualityDmaintenanceMCP server that enables control of an ETC Eos lighting console over OSC, supporting cues, channel levels, faders, and macros, with safety guards for destructive actions.132-
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to control QLab live over OSC, including querying workspaces, managing cues, and sending raw OSC or AppleScript commands.MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language control of OSC (OpenSoundControl) messages, allowing users to generate, interpret, validate, and debug OSC messages through an LLM interface for parametric control of multimedia devices.3MIT
TDQS
Scored across 20 tools
Several tools overlap heavily: eos_command, eos_new_command, and eos_event are easily confused, especially since eos_event is described as using 'same syntax as eos_command.' Also, cue_fire, cue_go, and key_press all relate to the GO action, while channel_set_level and at_set_level both set intensity, creating boundary ambiguity.
Naming is not chaotic and consistently uses snake_case, but conventions vary: object-first names like channel_set_level and cue_fire sit alongside verb-first names like get_console_state and wait_for_osc, with oddities like eos_command and eos_new_command that have no clear action verb. It is readable but not predictable.
20 tools is on the heavy/borderline side. The Eos Nomad control domain is fairly broad and most tools target distinct console resources, but several overlapping command/event/Go tools could be consolidated, making the count feel higher than necessary.
The set covers core console workflows well: channels, groups, cues, submasters, macros, command-line entry, key presses, and state read-back. The generic eos_command tool helps fill CLI-only gaps, though there are minor missing read-back operations such as querying submaster or channel levels directly.