q-sys-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qsys_connectA | Connect to a Q-SYS Core or to Q-SYS Designer running in Emulate mode (press F6 in Designer), over the QRC protocol (TCP). For a local emulator use host "127.0.0.1" and port 1710. Must be called before any other tool. |
| qsys_statusA | Get the Q-SYS engine status: platform, design name, run state, emulator flag. |
| qsys_list_componentsA | List named components in the running/emulated design, with type and properties (Component.GetComponents). On large designs use filter/type/names_only to trim the response. |
| qsys_get_component_controlsA | List a named component's controls and current values (Component.GetControls). Use filter/names_only to trim large components. |
| qsys_get_controlB | Get the current values of one or more Named Controls (Control.Get). |
| qsys_get_componentB | Get specific control values within a named component (Component.Get). |
| qsys_set_controlB | Set a Named Control value, optionally ramped over a number of seconds (Control.Set). This MUTATES the running/emulated system. |
| qsys_set_componentA | Set one or more control values within a named component, each optionally ramped (Component.Set). This MUTATES the running/emulated system. |
| qsys_load_snapshotA | Recall control settings from a saved snapshot bank/number, optionally ramped over seconds (Snapshot.Load). This MUTATES the running/emulated system. |
| qsys_save_snapshotA | Capture the current control settings into a snapshot bank/number (Snapshot.Save). This OVERWRITES the stored snapshot. |
| qsys_create_change_groupB | Create a change group (or add Named Controls to an existing one) so you can poll for changes (ChangeGroup.AddControl). |
| qsys_poll_change_groupA | Poll a change group; returns the controls that changed since the last poll (ChangeGroup.Poll). |
| qsys_change_group_add_componentA | Add a named component's controls to a change group so you can poll them for changes (ChangeGroup.AddComponentControl). |
| qsys_destroy_change_groupB | Destroy a change group, freeing its server-side state (ChangeGroup.Destroy). |
| qsys_change_group_removeA | Remove Named Controls from a change group, leaving the group in place (ChangeGroup.Remove). Returns any unknown control names. |
| qsys_change_group_clearA | Remove all controls from a change group without destroying it (ChangeGroup.Clear). |
| qsys_change_group_invalidateA | Invalidate a change group so the next poll resends every watched control, not just the changes (ChangeGroup.Invalidate). Handy after a reconnect to force a full snapshot. |
| qsys_disconnectA | Close the QRC connection to the Core/emulator. A later qsys_connect is required before other tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct operation or resource: connection, component/control queries, change group lifecycle, snapshot management, and status. There is no overlap; descriptions clearly differentiate purposes.
All tools follow the pattern qsys_<verb>_<noun> with consistent verb usage across the set. The naming is uniform and predictable.
With 18 tools, the set is slightly above the typical 3-15 range but well-justified by the domain's complexity (connection, change groups, components, snapshots). Each tool serves a clear purpose.
The tools cover connection lifecycle, read/write access to controls and components, change group management, and snapshot load/save. Minor gaps like listing existing change groups are absent but not critical.