VCV Rack: OSC control from Claude, scripts and controllers¶
0 named commands to drive VCV Rack over OSC — from Claude (MCP), live-coding environments or a MIDI controller.
| Device | VCV Rack |
|---|---|
| Vendor | VCV |
| OSC prefix | /vcv |
| Source | 📡 From a third-party OSC API |
| Firmware | VCV Rack 2.5 |
| Revision | VCV Rack 2.5 + OSC plugin (passthrough) |
| Upstream | third-party-osc |
| Driver file | devices/vcv-rack/vcv-rack.third-party-osc.fw-2.5.json |
Not tested on the device yet
This driver comes from documentation or community data and has not been checked on real hardware. If you own one, a quick test and a pull request promoting it helps everyone — see CONTRIBUTING.
How do you control it?¶
Start the bridge with this driver; it forwards named OSC commands to the software:
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as vcv: ask “what can the VCV Rack do?” and it reads this map with list_routes. See the MCP guide.
Limitations¶
Passthrough mode — VCV Rack itself has no built-in OSC. Recommended: install the `vcv-osc` plugin (github.com/roomi-fields/vcv-osc), whose OSC Controller module controls the whole patch — params, cables, module add/remove, presets, full state dump, and change subscriptions — addressable by numeric id OR human name/brand. It defaults to listen 7770 / reply 7771, matching this JSON with zero config. The bridge forwards `/vcv/...` (with `/vcv` stripped) to UDP 7770 and re-prefixes replies from 7771. vcv-osc also serves an OSCQuery namespace on HTTP 7772 for controllers that auto-build a surface (TouchOSC, Open Stage Control) — that is a direct HTTP link, not through this bridge. CV-only community modules (FormsAndShapes, Stoermelder) also work for simple signal bridging; adjust the port to match.