MCP Voice/Text-Controlled Q-SYS Demo
AI-powered system that enables voice and text control for Q-SYS audio systems using OpenAI Agents SDK and Model Context Protocol.
README
MCP Voice/Text-Controlled Q-SYS Demo
✅ PHASE 1 COMPLETE - AI-powered voice and text control for Q-SYS audio systems using the official @q-sys/qrwc SDK and Model Context Protocol.
🎉 BREAKTHROUGH: Q-SYS Connection SUCCESS!
We've successfully connected to a live Q-SYS Core with 42 components and 3,074+ controls!
🏆 Phase 1 Achievements
- ✅ Official @q-sys/qrwc SDK Integration - Using Q-SYS's official WebSocket library
- ✅ Live Q-SYS Core Connection - Connected to professional AV system at 192.168.50.150:443
- ✅ 42 Components Discovered - Full access to audio, video, and control systems
- ✅ 3,074+ Controls Available - Real-time control and monitoring of all Q-SYS components
- ✅ WSS Protocol Working - Secure WebSocket connection established
- ✅ Real-time Events - Live update events from Q-SYS components verified
- ✅ Professional Error Handling - Robust connection management and logging
🎛️ Connected Q-SYS System Overview
Your Q-SYS system includes:
- Audio: 15 components (mixers, gain controls, mics, soundbar)
- Video: 8 components (displays, video switching, cameras, HDMI routing)
- Conference: 5 components (Zoom Room, Microsoft Teams integration)
- Control: 9 components (touchpanels, UCI controllers, encoders)
- Building: 9 components (HVAC, status monitoring, date/time)
🚀 Quick Start
Test the Q-SYS Connection
# Test basic connection
npm run test:connection
# Test component interaction
node tests/integration/qsys/test-component-control.mjs
# Run main application
npm run dev
Setup Your Q-SYS Core
-
Follow the setup guides:
QRWC_SETUP_GUIDE.md- Complete Q-SYS Core configurationQSYS_SETUP.md- Quick setup instructions
-
Configure your Core IP:
- Edit
qsys-core.config.jsonwith your Q-SYS Core's IP address - The application will automatically load your configuration
- Edit
Development
# Install dependencies
npm install
# Run development server (connects to Q-SYS)
npm run dev
# Run tests
npm test
# Run linting
npm run lint
# Type checking
npm run type-check
🔧 Configuration
Q-SYS Core Configuration
Edit qsys-core.config.json:
{
"qsysCore": {
"host": "YOUR_CORE_IP_ADDRESS",
"port": 443,
"username": "",
"password": "",
"connectionSettings": {
"timeout": 10000,
"reconnectInterval": 5000,
"enableAutoReconnect": true
}
}
}
Configuration Setup (No Duplication!)
We use separate files for different configuration:
# Q-SYS Core settings (IP, port, credentials):
# → Edit qsys-core.config.json
# OpenAI API key and environment settings:
# → Edit .env file
# Setup both files:
./setup-env.sh
| File | Purpose |
|---|---|
qsys-core.config.json |
Q-SYS Core connection settings |
.env |
OpenAI API key, environment variables |
See OPENAI_SETUP.md for complete setup instructions.
📊 Project Status
✅ Phase 1: Q-SYS Remote WebSocket Control (QRWC) - COMPLETE
- ✅ 1.1: Project Setup & Infrastructure
- ✅ 1.2: Official @q-sys/qrwc SDK Integration
- ✅ 1.3: WebSocket Connection (WSS on port 443)
- ✅ 1.4: Component Discovery & Access (42 components found)
- ✅ 1.5: Real-time Event Handling
- ✅ 1.6: Error Handling & Reconnection Logic
- ✅ 1.7: Configuration System (JSON + Environment)
- ✅ 1.8: Testing & Verification
🔄 Phase 2: MCP Server Implementation - READY
- ⏳ MCP tools for Q-SYS component control
- ⏳ Real-time component monitoring
- ⏳ Voice command processing integration
🔄 Phase 3: AI Integration - READY
- ⏳ OpenAI integration for voice processing
- ⏳ Natural language Q-SYS control
- ⏳ Conversational AV system management
🛠️ Technology Stack
Core Technologies
- TypeScript 5.8.4 - Strict typing and modern JavaScript
- @q-sys/qrwc 0.4.1-beta - Official Q-SYS Remote WebSocket Control SDK
- WebSocket (WSS) - Secure WebSocket connection to Q-SYS Core
- Winston - Structured logging with metadata
- Jest - Testing framework with async support
Q-SYS Integration
- Official Q-SYS SDK - Using @q-sys/qrwc for WebSocket communication
- Real-time Events - Component state updates and control changes
- Professional Audio/Video Control - Full access to Q-SYS design components
- SSL/HTTPS Support - Secure connections with self-signed certificate support
📁 Project Structure
src/
├── qrwc/ # Q-SYS Remote WebSocket Control
│ └── officialClient.ts # Official @q-sys/qrwc SDK wrapper (350 lines)
├── shared/ # Shared utilities and types
│ ├── types/ # TypeScript definitions
│ └── utils/ # Logging, error handling, configuration
├── index.ts # Main application entry point
tests/ # Test suites
├── unit/ # Unit tests for components
└── integration/ # Integration tests
docs/ # Additional documentation
scripts/ # Build and utility scripts
# Configuration & Testing
qsys-core.config.json # Q-SYS Core connection configuration
tests/integration/qsys/test-connection.mjs # Basic connection test script
tests/integration/qsys/test-component-control.mjs # Component interaction test script
🧪 Testing & Verification
Connection Tests
# Test Q-SYS Core connection
npm run test:connection
# Expected: ✅ 42 components discovered
# Test component control
node tests/integration/qsys/test-component-control.mjs
# Expected: ✅ Real-time component interaction working
Application Tests
# Run all tests
npm test
# Run with coverage
npm run test:coverage
# Type checking
npm run type-check
📖 Documentation
Setup & Configuration
- QRWC Setup Guide - Complete Q-SYS Core configuration
- Q-SYS Setup - Quick setup instructions
- OpenAI Setup - OpenAI API key configuration for Phase 3
- Run Instructions - Development setup
Technical Documentation
- Implementation Plan - Complete technical implementation
- Project Checklist - Phase completion tracking
- QRC Overview - Q-SYS Remote Control overview
- Component Control - Component interaction guide
Project Management
- PRD Document - Product requirements
- Cursor Rules - Development guidelines
🎯 Key Discovery: WSS Protocol
Critical Technical Breakthrough: Q-SYS Cores require Secure WebSocket (WSS) connections, not standard WebSocket (WS).
// ❌ This doesn't work:
const socket = new WebSocket('ws://core-ip:443/qrc-public-api/v0');
// ✅ This works:
const socket = new WebSocket('wss://core-ip:443/qrc-public-api/v0', {
rejectUnauthorized: false // For self-signed certificates
});
🏆 Live System Results
Connected to professional Q-SYS installation:
📦 Components found: 42
🎛️ Total controls: 3,074+
Categories discovered:
├── Audio: 15 components (mixers, mics, gain controls)
├── Video: 8 components (displays, switchers, cameras)
├── Conference: 5 components (Zoom Room, Teams integration)
├── Control: 9 components (touchpanels, encoders)
└── System: 9 components (HVAC, monitoring, time sync)
📄 License
MIT License - see LICENSE file for details.
🎉 Phase 1 Complete! The Q-SYS QRWC integration is fully functional and ready for MCP Server development in Phase 2.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。