Skip to main content
Glama
chienchuanw

GMA2 MCP

by chienchuanw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GMA2 MCP

No user-submitted related servers found.

    Related Servers

    • grandMA2 Universal MCP Server

      vandiy064-byte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      MIT

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

    • grandma2-mcp

      RaSteaks
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of grandMA2 onPC and MA3D over Telnet through MCP tools for querying shows, fixtures, and playback objects, executing commands, adjusting fixture/camera transforms, exporting XML, backing up shows, and capturing MA3D screenshots.
      AGPL 3.0

    • gma3-mcp

      bdstark
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      75
      3
      MIT

    • ableton-mcp

      amamparo
      F
      license
      B
      quality
      D
      maintenance
      MCP 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
      -
    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/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

    ActivityInactive
    ResponsivenessUnresponsive

    Resources