Q-SYS MCP

Name: Q-SYS MCP
Author: reowens

by reowensversion 0.6.1i★ –iRuns on your computer

Registry nameio.github.reowens/qsys-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "qsys": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "qsys-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account reowens, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18353 servers in this category
Published to the registry more recently than 81% of the other 18353 servers in this category
Basic checks equal to or better than 100% of the other 18353 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Q-SYS MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.6.1) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Date Math

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Date Math

by JowenDelaPena

Date/time math for agents: business days, holidays, time zones, cron, RRULE. 25 free calls/day.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

qsys-tools

Open-source tooling for QSC Q-SYS audio/video systems — control a Core from

your shell, your code, or an AI agent, and run Q-SYS Designer on your Mac or Ubuntu desktop.

Every Q-SYS Core — and Q-SYS Designer in Emulate mode — serves QSC's published QRC protocol (JSON-RPC 2.0 over TCP, port 1710). It's the same external-control interface Crestron/AMX integrations use. These tools speak it natively: zero QSC code, no SDK, no hardware required for development.

Package	What it is
`qsys-cli`	CLI (command: `qsys`) — status, component inventory, get/set controls with ramps, live watch, snapshots
`qsys-qrc`	TypeScript QRC client — wire framing, change groups, keepalive, transparent auto-reconnect, typed protocol surface
`qsys-mcp`	MCP server (`io.github.reowens/qsys-mcp` in the MCP Registry) — 25 tools that let an AI agent inspect and drive a live Q-SYS system
`qsys-mac`	npm bootstrapper (command: `qsys-mac`) — downloads/verifies the signed Q-SYS Mac Installer DMG and delegates to its helper
`qsys-mac-installer`	Q-SYS Designer for macOS — signed/notarized BYO-installer wrapper app + DMG source
`qsys-linux`	Q-SYS Designer for Ubuntu 26.04 x86-64 — per-user Wine/.NET 10 setup and desktop launcher (command: `qsys-linux`)

Quick start — shell

export QSYS_HOST=192.168.1.10     # your Core, or 127.0.0.1 for Designer Emulate

npx qsys-cli status # engine/design status npx qsys-cli ls # list components npx qsys-cli get MainGain # read a named control npx qsys-cli set MainGain -6 --ramp 2 npx qsys-cli watch MainGain # stream changes until Ctrl-C npx qsys-cli snapshot load Bank 1 --ramp 1

$ qsys status Design Example-Design (code a1B2c3D4e5F6) Platform Emulator (emulator) State Active

$ qsys set-component Main_Mixer input.1.gain -6 --ramp 2 NAME VALUE STRING POSITION input.1.gain -6 -6.00dB 0.585

Install the command globally with npm i -g qsys-cli (the binary is plain qsys). Every command takes --json for scripting; watch emits JSON lines.

Quick start — AI agent (MCP)

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

or in any MCP client config:

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

Then ask the agent to connect to your Core (or the Designer emulator) and it can read meters, flip mutes, ramp gains, watch controls for changes, and recall snapshots — with auto-reconnect across Core restarts. Details in packages/qsys-mcp.

Registry-aware MCP clients can discover it as io.github.reowens/qsys-mcp.

Quick start — your own code

npm install qsys-qrc

import { QrcClient } from 'qsys-qrc';

const qrc = new QrcClient({ host: '192.168.1.10' }); await qrc.connect();

const status = await qrc.statusGet(); // typed helpers… await qrc.setControl('MainGain', -6, 2); // value -6, 2 s ramp const [gain] = await qrc.getControl(['MainGain']);

await qrc.send('Component.GetComponents'); // …or raw QRC methods

qrc.close();

Change groups (poll-based watch), component access, snapshots, and logon are all covered by typed helpers — see packages/qsys-qrc.

Q-SYS Designer on your Mac

For most users, use the signed DMG installer app. Run it once to create Q-SYS Designer.app, then either trash the installer app or keep it around as a small manager for Launch, Reinstall, and Remove. The installed Designer app and its Application Support data remain independent of the installer app.

Direct DMG path:

open https://github.com/reowens/qsys-tools/releases/tag/qsys-mac-installer-v0.1.9

Or use the npm bootstrapper:

npx qsys-mac install "/path/to/Q-SYS Designer Installer 10.5.1.exe"

It downloads and verifies the signed Q-SYS Mac Installer DMG, mounts it, and runs the bundled helper. The npm package does not contain Q-SYS Designer or the app payload. You provide your own free Designer installer download (BYO — nothing of QSC's is redistributed).

For read-only support diagnostics, run:

npx qsys-mac doctor

Current macOS prerequisite: Rosetta 2. The signed DMG bundles Wine, .NET, 7z, icon tooling, msiinfo, and native helper binaries; normal setup does not need Homebrew or host Python.

Prefer a GUI installer app? Homebrew can install it:

brew tap reowens/qsys

brew trust reowens/qsys brew install --cask qsys-mac-installer open -a "Q-SYS Mac Installer"

brew trust is required by current Homebrew for third-party cask taps.

The signed installer source lives in packages/qsys-mac-installer. It provisions Wine + .NET into Application Support and gives you a real Dock/Finder/menu-bar citizen. The current signed DMG is qsys-mac-installer 0.1.9.

Bonus: Designer's Emulate mode serves QRC on 127.0.0.1:1710, so all of the tools above work hardware-free against it — that's how this repo's tooling is validated.

Q-SYS Designer on Linux

The initial Linux recipe runs Designer 10.5.1 on Ubuntu 26.04 x86-64 through Wine Staging 11.20 and Windows .NET 10. Supply your own vendor ZIP/EXE:

npx qsys-linux install "/path/to/Q-SYS_Designer_Installer_10.5.1.zip"

npx qsys-linux doctor npx qsys-linux launch

Installation needs an accessible X11/XWayland desktop and 12 GiB free during setup. It runs per-user without sudo and adds a Q-SYS Designer desktop launcher. See requirements and validation.

The source checkout also has a vendor-free Docker test harness, described under Container smoke tests. You build its image locally; no image is published.

No hardware?

Point any of the tools at Q-SYS Designer running in Emulate mode (--host 127.0.0.1). Two protocol facts worth knowing: QRC has no method to *enumerate* named controls or snapshot banks (you need their names from the design), and Component.GetComponents returns only components with script access enabled.

Development

This is a pnpm workspace (Node 22.13+; pnpm comes from the packageManager field via corepack).

git clone https://github.com/reowens/qsys-tools.git

cd qsys-tools corepack enable # provisions the pinned pnpm pnpm install pnpm -r build # builds packages in dependency order (qsys-qrc first) pnpm run typecheck pnpm test

The e2e suites (QRC integration, the MCP-over-mock end-to-end, and the transparent-reconnect/AutoPoll-replay regression) run against qsys-mock-core — an in-repo, design-driven Q-SYS Core mock — so pnpm test exercises the full protocol with no hardware. Deeper conformance testing (validated-against-Designer rendering and ramps/meters) uses a separate, fuller emulator.

qsys-mac-installer builds separately with Xcode — see packages/qsys-mac-installer (scripts/package.sh for the sign/notarize pipeline).

Maintainer release steps are documented in RELEASE.md.

When working from this source checkout, use the workspace script instead of npx qsys-mac so the local workspace package isn't confused with the published one:

pnpm run qsys-mac -- status

pnpm run qsys-mac -- install "/path/to/Q-SYS Designer Installer 10.4.0.exe"

Licensing

The original qsys-tools source code is MIT licensed, including the QRC packages, the qsys-mac npm bootstrapper, the qsys-linux recipe, and the qsys-mac-installer wrapper app.

The signed macOS installer DMG is a multi-license binary distribution because it bundles redistributable third-party components such as Wine, .NET, p7zip, icoutils, msiinfo, and their runtime libraries. Those components remain under their own licenses and notices; see packages/qsys-mac-installer/THIRD-PARTY-NOTICES.md.

Each package carries its own LICENSE file.

Disclaimer

This is an independent open-source project, not affiliated with, endorsed by, or sponsored by QSC, LLC. "Q-SYS" and "Q-SYS Designer" are trademarks of QSC, LLC, used nominatively. These tools speak the publicly documented QRC protocol and contain no QSC code.

Q-SYS MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Date Math

README from the maker

qsys-tools

Quick start — shell

Quick start — AI agent (MCP)

Quick start — your own code

Q-SYS Designer on your Mac

Q-SYS Designer on Linux

No hardware?

Development

Licensing

Disclaimer