Q-SYS MCP

NPM · QSYS-MCP · SCANNED AUG 3

Control QSC Q-SYS systems over QRC from AI agents or Claude.

Available components

+33 this week 79 79 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency97

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Cryptographically verified build provenance (signed, bound to reowens/qsys-tools). View diagnostics → Pass
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 23 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2601 tokens (~104/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
99% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · qsys-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add reowens-qsys-mcp -- npx -y qsys-mcp

# add to Codex CLI

codex mcp add reowens-qsys-mcp -- npx -y qsys-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reowens-qsys-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "qsys-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add reowens-qsys-mcp --command npx --arg -y --arg qsys-mcp

# ~/.hermes/config.yaml

mcp_servers:
  reowens-qsys-mcp:
    command: "npx"
    args: ["-y", "qsys-mcp"]

// mcp.json

{
  "mcpServers": {
    "reowens-qsys-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "qsys-mcp"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +58
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- The attested source repository moved: reowens/qsys-tools security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
1 Aug 26 +15
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
27 Jul 26 46

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:: reowens/qsys-tools
Certificate issuer:: https://token.actions.githubusercontent.com
Certificate SAN:: https://github.com/reowens/qsys-tools/.github/workflows/publish.yml@refs/tags/qsys-mcp-v0.6.0
Rekor log index:: 2136215530
Predicate type:: https://slsa.dev/provenance/v1
Subject digest:: sha512:775ae8c024b9a3801344745546d0edd6118fe0d133847a22b074593d2f4bf4a5c11813714d830f22aadb9dc872e10032c74dad92705b7aeca299e3af8
Discovery method:: attestation_endpoint

Dependencies 96 packages

96 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 25 exposed · ~2,601 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

qsys_change_group_add_component Add component controls to a change group ~76

Add a named component's controls to a change group so you can poll them for changes (ChangeGroup.AddComponentControl).

Input Output Examples

Name	Type	Req	Description
component	string	yes	Component name
controls	array	yes	Control names within the component to watch
id	string	yes	Change group id (any string; reused on poll)

No output schema declared.

No examples provided.

qsys_change_group_clear Clear a change group ~36

Remove all controls from a change group without destroying it (ChangeGroup.Clear).

Input Output Examples

Name	Type	Req	Description
id	string	yes	Change group id

No output schema declared.

No examples provided.

qsys_change_group_invalidate Invalidate a change group ~57

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.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Change group id

No output schema declared.

No examples provided.

qsys_change_group_remove Remove controls from a change group ~58

Remove Named Controls from a change group, leaving the group in place (ChangeGroup.Remove). Returns any unknown control names.

Input Output Examples

Name	Type	Req	Description
controls	array	yes	Named Control names to stop watching
id	string	yes	Change group id

No output schema declared.

No examples provided.

qsys_connect Connect to Q-SYS ~224

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.

Input Output Examples

Name	Type	Req	Description
allow_live_writes	boolean	—	Permit write tools against a LIVE (non-emulator) Core. Default false: writes are refused unless the target reports IsEmulator=true. Set true only when the user has explicitly approved changing a real…
host	string	—	Core IP/hostname, or 127.0.0.1 for a local Designer emulator
password	string	—	Password, if the design requires authentication
port	integer	—	QRC port (default 1710)
reconnect	boolean	—	Auto-reconnect on a dropped socket (Core restart, network blip), replaying change-group registrations so polling resumes. Default true.
user	string	—	Username, if the design requires authentication

No output schema declared.

No examples provided.

qsys_create_change_group Create or extend a change group ~66

Create a change group (or add Named Controls to an existing one) so you can poll for changes (ChangeGroup.AddControl).

Input Output Examples

Name	Type	Req	Description
controls	array	yes	Named Control names to watch
id	string	yes	Change group id (any string; reused on poll)

No output schema declared.

No examples provided.

qsys_destroy_change_group Destroy a change group ~36

Destroy a change group, freeing its server-side state (ChangeGroup.Destroy).

Input Output Examples

Name	Type	Req	Description
id	string	yes	Change group id

No output schema declared.

No examples provided.

qsys_disconnect Disconnect from Q-SYS ~31

Close the QRC connection to the Core/emulator. A later qsys_connect is required before other tools.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

qsys_get_component Get specific component control values ~43

Get specific control values within a named component (Component.Get).

Input Output Examples

Name	Type	Req	Description
controls	array	yes	Control names within the component
name	string	yes	Component name

No output schema declared.

No examples provided.

qsys_get_component_controls Get component controls ~93

List a named component's controls and current values (Component.GetControls). Use filter/names_only to trim large components.

Input Output Examples

Name	Type	Req	Description
filter	string	—	Case-insensitive substring; only controls whose name contains it are returned
name	string	yes	Component name (as returned by qsys_list_components)
names_only	boolean	—	Return only control names (drop values/positions) to save context

No output schema declared.

No examples provided.

qsys_get_control Get control values ~34

Get the current values of one or more Named Controls (Control.Get).

Input Output Examples

Name	Type	Req	Description
names	array	yes	Named Control names

No output schema declared.

No examples provided.

qsys_list_components List components ~160

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. Note: QRC only sees components whose Designer "Script Access" is set to External or All (None is the default) — a component missing here, or one that silently ignores writes, most likely needs its Code Name + Script Access set in Designer.

Input Output Examples

Name	Type	Req	Description
filter	string	—	Case-insensitive substring; only components whose name contains it are returned
names_only	boolean	—	Return only name + type per component (drop properties) to save context
type	string	—	Case-insensitive substring on component type (e.g. "gain", "mixer")

No output schema declared.

No examples provided.

qsys_load_snapshot Recall a snapshot ~85

Recall control settings from a saved snapshot bank/number, optionally ramped over seconds (Snapshot.Load). This MUTATES the running/emulated system.

Input Output Examples

Name	Type	Req	Description
bank	string	yes	Snapshot bank name, as named in Q-SYS Designer
number	integer	yes	Snapshot number within the bank (1-based)
ramp	number	—	Ramp time in seconds (optional)

No output schema declared.

No examples provided.

qsys_loop_player_start Start Loop Player playback ~254

Schedule one or more audio files to play on a Loop Player component (LoopPlayer.Start). This MUTATES the running/emulated system. There is no QRC method to browse Core files — pass a file path you already know. Read Loop Player state back via qsys_get_component.

Input Output Examples

Name	Type	Req	Description
files	array	yes	One file→output assignment per entry (a Files entry carries only name + output; the options below apply to the whole job)
log	boolean	—	Log start + errors to the Core event log (default false)
loop	boolean	—	Loop playback continuously (default false)
name	string	yes	Loop Player component name (its "Code Name")
refId	string	—	If set, the Core logs an async failure notification for this job (the notification is not surfaced by these tools yet)
seek	number	—	Offset into the file to start playback, in seconds (default 0)
startTime	number	—	-1 = now, -2 = queue after current, ≥0 = absolute time-of-day (s). Omitted → Core default (0). With Time source "None", 0 plays now and >0 has no effect.

No output schema declared.

No examples provided.

qsys_loop_player_stop_cancel Stop or cancel Loop Player playback ~160

Stop current playback on outputs (op "stop"), or cancel a pending/queued future-start job without disrupting current playback (op "cancel") — LoopPlayer.Stop / LoopPlayer.Cancel. Outputs is a list of integer output numbers (e.g. [1, 2]). This MUTATES the running/emulated system.

Input Output Examples

Name	Type	Req	Description
log	boolean	—	Log the stop/cancel to the Core event log (default false)
name	string	yes	Loop Player component name (its "Code Name")
op	string	yes	"stop" halts current playback; "cancel" aborts a queued future-start job
outputs	array	yes	Output track numbers as an integer list, e.g. [1, 2]

No output schema declared.

No examples provided.

qsys_mixer_set_crosspoint Set mixer crosspoint(s) ~259

Set gain/delay (number, ramped) or mute/solo (boolean) on the crosspoints of an input×output selection (Mixer.SetCrossPoint{Gain,Delay,Mute,Solo}). This MUTATES the running/emulated system. Read mixer state back via qsys_get_component.

Input Output Examples

Name	Type	Req	Description
inputs	string	yes	Input selector — QRC String Syntax: "*" (all), "1 2 3"/"1,2,3" (list), "1-6" (range), "!3" (negate), combinable ("1-8 !3")
name	string	yes	Mixer component name
op	string	yes	Which crosspoint property to set
outputs	string	yes	Output selector — QRC String Syntax: "*" (all), "1 2 3"/"1,2,3" (list), "1-6" (range), "!3" (negate), combinable ("1-8 !3")
ramp	number	—	Ramp time in seconds — gain/delay only, ignored otherwise
value	number\|boolean	yes	Number (dB/seconds) for gain/delay; boolean for mute/solo

No output schema declared.

No examples provided.

qsys_mixer_set_cue Set mixer cue(s) ~132

Set gain (number, ramped) or mute (boolean) on selected mixer cues (Mixer.SetCue{Gain,Mute}). This MUTATES the running/emulated system. Read mixer state back via qsys_get_component.

Input Output Examples

Name	Type	Req	Description
cues	string	yes	Cue selector (string specification of mixer cues)
name	string	yes	Mixer component name
op	string	yes	Which cue property to set
ramp	number	—	Ramp time in seconds — gain only, ignored otherwise
value	number\|boolean	yes	Number (dB) for gain; boolean for mute

No output schema declared.

No examples provided.

qsys_mixer_set_cue_input Route/monitor input(s) to cue(s) ~173

Enable an input on a cue, or set its AFL (after-fade listen) flag (boolean) (Mixer.SetInputCue{Enable,Afl}). This MUTATES the running/emulated system. Read mixer state back via qsys_get_component.

Input Output Examples

Name	Type	Req	Description
cues	string	yes	Cue selector (string specification of mixer cues)
inputs	string	yes	Input selector — QRC String Syntax: "*" (all), "1 2 3"/"1,2,3" (list), "1-6" (range), "!3" (negate), combinable ("1-8 !3")
name	string	yes	Mixer component name
op	string	yes	Set cue-input enable, or AFL monitoring
value	number\|boolean	yes	Boolean

No output schema declared.

No examples provided.

qsys_mixer_set_input Set mixer input(s) ~181

Set gain (number, ramped) or mute/solo (boolean) on selected mixer inputs (Mixer.SetInput{Gain,Mute,Solo}). This MUTATES the running/emulated system. Read mixer state back via qsys_get_component.

Input Output Examples

Name	Type	Req	Description
inputs	string	yes	Input selector — QRC String Syntax: "*" (all), "1 2 3"/"1,2,3" (list), "1-6" (range), "!3" (negate), combinable ("1-8 !3")
name	string	yes	Mixer component name
op	string	yes	Which input property to set
ramp	number	—	Ramp time in seconds — gain only, ignored otherwise
value	number\|boolean	yes	Number (dB) for gain; boolean for mute/solo

No output schema declared.

No examples provided.

qsys_mixer_set_output Set mixer output(s) ~175

Set gain (number, ramped) or mute (boolean) on selected mixer outputs (Mixer.SetOutput{Gain,Mute}). This MUTATES the running/emulated system. Read mixer state back via qsys_get_component.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Mixer component name
op	string	yes	Which output property to set
outputs	string	yes	Output selector — QRC String Syntax: "*" (all), "1 2 3"/"1,2,3" (list), "1-6" (range), "!3" (negate), combinable ("1-8 !3")
ramp	number	—	Ramp time in seconds — gain only, ignored otherwise
value	number\|boolean	yes	Number (dB) for gain; boolean for mute

No output schema declared.

No examples provided.

qsys_poll_change_group Poll a change group ~41

Poll a change group; returns the controls that changed since the last poll (ChangeGroup.Poll).

Input Output Examples

Name	Type	Req	Description
id	string	yes	Change group id

No output schema declared.

No examples provided.

qsys_save_snapshot Save a snapshot ~66

Capture the current control settings into a snapshot bank/number (Snapshot.Save). This OVERWRITES the stored snapshot.

Input Output Examples

Name	Type	Req	Description
bank	string	yes	Snapshot bank name, as named in Q-SYS Designer
number	integer	yes	Snapshot number within the bank (1-based)

No output schema declared.

No examples provided.

qsys_set_component Set component control values ~54

Set one or more control values within a named component, each optionally ramped (Component.Set). This MUTATES the running/emulated system.

Input Output Examples

Name	Type	Req	Description
controls	array	yes	—
name	string	yes	Component name

No output schema declared.

No examples provided.

qsys_set_control Set a control value ~79

Set a Named Control value, optionally ramped over a number of seconds (Control.Set). This MUTATES the running/emulated system.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Named Control name
ramp	number	—	Ramp time in seconds (optional)
value	number\|string\|boolean	yes	New value (number, string, or boolean)

No output schema declared.

No examples provided.

qsys_status Q-SYS engine status ~28

Get the Q-SYS engine status: platform, design name, run state, emulator flag.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug