Skip to content

SynthHub

Every synthesizer, drum machine and DAW in one catalogue, playable by name — by you and by your AI agent. SynthHub knows the MIDI implementation of 963 devices: their CC, NRPN and SysEx parameters and their drum sounds, each under a readable OSC address. Ask Claude or any MCP agent to set the filter of your minilogue or play a kick on your TR-8S; SynthHub finds the right message. Its engine is osc-bridge, an open-source (AGPL-3.0) OSC ↔ MIDI/SysEx bridge and MIDI MCP / OSC MCP server.

Browse the 963 devices Connect your synth

Three ways in

  • Hosted MCP server — nothing to install. Add https://mcp.osc-bridge.roomi-fields.com/mcp as a remote MCP server (a custom connector in Claude). Your agent searches the catalogue, reads any device's map, and tells you how far other users confirmed a driver on the real device. → API for agents
  • Your synth, from the browser. Plug it in, open Connect your synth in Chrome or Edge, and give the code to your agent: it detects the device, plays it and sets its parameters by name. A message that could overwrite the device's memory waits for your OK.
  • osc-bridge on your machine. npx -y @roomi-fields/osc-bridge mcp, or a single binary for Linux, macOS and Windows: drive hardware from SuperCollider, Sonic Pi, TouchDesigner or a web page over OSC, back up presets, run several devices together. It keeps its catalogue up to date from SynthHub, and you choose what it shares. → Install osc-bridge

What can you do with it?

How far can you trust a driver?

Each driver states its source. ✅ means tested on the device; 📘 comes from the manufacturer's documentation; 📡 from a software's OSC API; 🎛️ from an Electra One community preset; 📦 from MIDI Guide community data (CC BY-SA 4.0). On top of that, SynthHub counts what users report from their own unit, firmware by firmware: a driver that several people confirmed on the same firmware is marked as verified by use, and one that fails on a firmware is flagged for it. Agents can also submit a missing driver or a fix; once it passes the checks, it joins the catalogue.

How does it work?

Each device is one JSON file: its CC and NRPN numbers, SysEx frame templates and drum sounds, each under a readable OSC address. osc-bridge loads the file, listens for OSC on 127.0.0.1:7777, sends MIDI to the device, and turns what the device sends back (knobs, pads, SysEx replies) into OSC for your clients. SynthHub serves the same catalogue to agents over MCP and carries their messages to your hardware through the relay.

osc-bridge detect                      # what is plugged in, and which driver fits
osc-bridge run --device devices/arturia/minilab3.json --out-port 4 --in-port 0
osc-bridge osc-send /minilab3/display/text "Hello" "World"

Coming next: shared presets, virtual twins of the catalogue's devices, and plugins that bring the relay into DAWs and VCV Rack.