Helix Stadium MCP
Ask your AI assistant what a Line 6 Helix Stadium .hsp preset does, or how two snapshots differ — and get a plain-English answer with real values (dB, Hz, ms), not raw parameter numbers.
Overview
Point your AI assistant at a .hsp preset and ask what it does, or how two snapshots differ. You get the whole signal chain back in plain English — friendly model names, on/off state, and every parameter in the units you'd read off the hardware (dB, Hz, ms, %), not raw numbers. Because it understands the whole patch, it also walks you through changes: ask how to brighten the lead or get more gain, and it points you to the exact block and parameter to move. Today's tool surface is read-only (you apply edits in your own editor); making those changes for you is on the roadmap.
Features
- Lossless .hsp codec - byte-exact round-trip of the preset container
- Plain-English explain - the full signal chain per path, with friendly model names, on/off state, per-snapshot and footswitch tags, and parameters in real units
- Snapshot diffing - exactly what changes between two snapshots (e.g. Rhythm vs Lead), in real units
- Model catalog browsing - list, describe, and search models read at runtime from your own install
- Validation - checks a preset's structure and, with the catalog, its model ids and controller sources
- Read-only and private - runs over stdio, opens no socket, makes no network calls, and has no arbitrary-code escape hatch
Requirements
- Line 6 Helix Stadium installed (Windows confirmed; macOS support in progress). The server reads the model catalog from your own install at runtime.
- Python 3.10+ (for the MCP server)
- An MCP-compatible AI client (e.g. Claude Desktop)
Installation
Step 1: Run the Server
uvx twelvetake-helix-stadium-mcp serve
# or: pipx run twelvetake-helix-stadium-mcp serveStep 2: Register With Your AI Client
Add the server to your MCP client's configuration (e.g. Claude Desktop):
{
"mcpServers": {
"helix-stadium": {
"command": "uvx",
"args": ["twelvetake-helix-stadium-mcp", "serve"]
}
}
}Step 3: Verify Detection
Check that your install is found:
helix-stadium-mcp doctorIf the catalog isn't auto-detected, set HELIX_STADIUM_RES to your install's res/ folder (the one containing P35ModelCatalog.json).
Available Tools (8)
| Group | Count | Tools |
|---|---|---|
| Preset read / explain | 3 | read_preset, explain_preset, diff_snapshots |
| Model catalog | 3 | list_models, describe_model, search_models |
| Install & validation | 2 | detect_install, validate_preset |
v1 is read-only. Editing, generation, and setlist tooling are on the roadmap.
Usage Examples
Read MyTone.hsp and explain the signal chainWhat changes between the Rhythm and Lead snapshots?Search the model catalog for tape delaysDescribe the amp model in block 2Validate this preset fileFAQ
Can it edit or create presets?
Not yet. The v1 tool surface is entirely read-only — it reads, explains, diffs, and validates. Editing, generation, and setlist tooling are on the roadmap.
Does it bundle any Line 6 content?
No. The model catalog is read at runtime from your own Helix Stadium install. No Line 6 content is bundled or redistributed.
Which platforms are supported?
Windows is confirmed. macOS support is in progress. If the catalog isn't auto-detected, point HELIX_STADIUM_RES at your install's res/ folder.
Does it make network calls?
No. It runs over stdio, opens no socket, and makes no network calls.
Is this affiliated with Line 6 or Yamaha?
No. It is an independent, unofficial tool, not affiliated with, authorized, sponsored, or endorsed by Line 6 or Yamaha Guitar Group. Line 6, Helix, and Helix Stadium are trademarks of their respective owners.
Need a custom MCP server?
We build MCP servers like this one — wiring AI assistants into DAWs, creative software, and internal tools. That is a service we offer. Tell us your workflow and we will scope it.
Get a custom MCP built