A
licenseNot graded
qualityC
maintenanceTransforms 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
by chienchuanw
Related Servers
Alternatives to GMA2 MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceHigh-performance MCP server that enables AI assistants to control TouchDesigner live via WebSocket, providing 37 tools for nodes, parameters, scripting, and more.5MIT
- FlicenseBqualityDmaintenanceMCP server for controlling Ableton Live, enabling AI assistants to interact with Live sessions through tools for track/clip/scene management, playback control, and device parameter adjustments.48-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes the complete DaVinci Resolve scripting API, enabling AI assistants to control DaVinci Resolve programmatically with over 440 tools for project management, timeline editing, color grading, rendering, and more.7MIT
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server that enables AI assistants to control music playback, manage users and access, configure providers, and administer a Music Assistant setup through natural language commands.MIT
- AlicenseCqualityAmaintenanceA comprehensive MCP server that enables AI assistants to control REAPER DAW for mixing, mastering, MIDI composition, and full music production workflows with 130 tools.17654MIT
TDQS
B3/5.0
Scored across 101 tools
Disambiguation3/5
Most tools target distinct object/action pairs with detailed descriptions, but there are several overlapping boundaries: label_object vs label_macro_tool vs label_sequence_cue, set_effect_speed vs set_effect_seconds, goto_cue_tool vs execute_sequence(goto), and multiple store/update cue variants. An agent would often need to read full descriptions to avoid picking the wrong tool.
Naming Consistency2/5
A loose verb_noun pattern exists, but it is inconsistently applied: some tools have a random _tool suffix (save_show_tool, delete_macro_tool, sync_effects_tool), some use non-verb forms (temp_executor, next_fixture, appearance_cue_across_sequences), and similar operations use different verbs (list_groups vs list_shows_tool, read_cue_info vs get_cue_annotation). The naming feels ad hoc rather than systematic.
Tool Count1/5
101 tools is far beyond any reasonable scope for a focused MCP server. Even for a broad grandMA2 console integration, this count is excessive and creates high selection and maintenance overhead.
Completeness4/5
The tool surface covers core workflows comprehensively: cues, presets, macros, effects, executors, variables, timecode, MIDI, show files, and palette building. Notable gaps exist around patch/fixture creation (only delete_fixture is provided) and generic sequence lifecycle, but send_raw_command provides a workaround for these edge cases.
Maintenance
ActivityStale
ResponsivenessSlow