gma3-mcp
Related Servers
Alternatives to gma3-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn 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.10016Apache 2.0
- 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
- AlicenseBqualityBmaintenanceAn MCP server that lets Claude and other MCP clients read PreSonus Studio One .song files directly and drive a running Studio One through an in-app bridge device. It exposes tools for songs, tracks, takes, markers, transport, mixer channels, meters and roughly 1,000 Studio One commands.2728 npm10MIT
- 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.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Code to operate Logic Pro — transport, track selection/mute/solo/arm, mixer volume and pan, 8-band Channel EQ, and insert plugin slots — by emulating a Mackie Control surface over a CoreMIDI virtual port. Every command is verified against the LED, fader, and LCD feedback Logic sends back, so results report whether each action actually took effect.MIT
- FlicenseAqualityDmaintenanceAn MCP server that gives Claude Code (or any MCP client) full control of Reaper.53-
TDQS
Scored across 75 tools
Tools are extensively documented with explicit distinctions (e.g. gma3_get_object vs gma3_dump vs gma3_objects; gma3_lua vs structured readers; gma3_hardkey vs gma3_keyboard). A few overlaps remain—gma3_set_property vs gma3_configure_* vs gma3_command—but descriptions consistently steer the selection.
Strong, predictable gma3_<verb>_<noun> convention throughout (gma3_store_cue, gma3_configure_sequence, gma3_patch_add, gma3_build_phaser). Minor deviations exist (gma3_dump, gma3_status, gma3_lua) but they are readable and intentional.
75 tools is heavy even for the broad grandMA3 domain; the patch/executor/sequence/cue/timecode/macro/phaser sub-surfaces each add clusters of tools. It is more than an agent can comfortably hold, pushing toward 25+ territory.
Covers the domain remarkably thoroughly: show-data reads, playback, programmer, patch (add/set/remove), cues/parts/timing/triggers, executors, sequences, presets, phasers, recipes, macros, timecodes and input. CRUD and lifecycle gaps are rare and explicitly documented with limitations.