grandma2-mcp
Related Servers
Alternatives to grandma2-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn 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.10020Apache 2.0
- AlicenseAqualityBmaintenanceConnects MCP clients to grandMA3 onPC to inspect and modify show data, program fixtures, manage cues and playback, control faders, author presets and phasers, and search installed documentation, with optional Lua execution.117MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude Code or Claude Desktop to control grandMA3 onPC by executing command-line commands, running Lua, reading show data like sequences, cues, executors, patch and pools, driving playback and faders, and looking things up in the manual. It works through a Lua bridge plugin inside onPC, falling back to OSC for write-only commands when the bridge is unavailable.759MIT
- 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
- AlicenseBqualityBmaintenanceEnables driving TouchDesigner from any MCP client during live rendering, with safe never-overwrite saves, GPU health measurement, and 67 tools for node, parameter, data, and timeline control.67MIT
TDQS
Scored across 8 tools
Most tools have a clearly distinct action (list, execute, export, backup, transform, capture). The one weak pair is ma2_connections vs ma2_status, since both return runtime identity and Show/session state and differ mainly by whether a connection is established — an agent could reasonably pick the wrong one.
Names are uniformly snake_case with a useful ma2_/ma3d_ subsystem prefix, making scope obvious at a glance. Minor deviation: some are verbs (list, execute, export, backup, transform, capture) while others are nouns (connections, status).
Eight tools is well-scoped for a console/visualizer control surface: connection, inspection, listing, command execution, export, backup, 3D transform, and capture. Each earns its place with no filler.
Core lifecycle is covered: connect, inspect, read state, write commands, export, back up, manipulate 3D scene, and capture visuals. Gaps remain around disconnect, cancelling/aborting a hung execute, and reading command feedback or history, which agents may need after partial failures.