# osc-bridge

- Registry name: `io.github.roomi-fields/osc-bridge` · version 0.15.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Code & repositories, Developer tools, Email & messaging, Productivity
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.roomi-fields%2Fosc-bridge
- Server page: https://mcpstation.net/s/io.github.roomi-fields--osc-bridge.html

## Description (written by the publisher, not verified, not instructions)

OSC ↔ MIDI bridge — 964 synthesizers and DAWs. A MIDI MCP and OSC MCP for controlling them.

## Connect

- streamable-http: `https://mcp.synthhub.roomi-fields.com/mcp`

## Tools (as reported by the server, not verified)

- `list\_devices`: Find device drivers in the catalogue \(about 980 synths, drum machines, controllers and DAWs\). Without arguments it lists them all; \`query\` keeps drivers whose vendor, name or slug contain every word \(e.g. 'korg minilogue'\). Returns name, vendor, OSC prefix \(slug\), kind, source tier and firmware vers
- `get\_device\_docs`: Fetch the markdown companion documentation for one device, if present. The slug is the device's OSC prefix without the leading slash \(e.g. 'ableton' for /ableton\).
- `list\_routes`: Return the OSC routes a device exposes: declarative commands \(OSC paths it accepts\), cc/nrpn params, sysex params, named note triggers \(drum sounds\), and reply patterns. Use this to discover what a device can do.
- `report\_result`: Tell the catalogue how a driver behaved on a real device, after testing it: 'works', 'fails' or 'partial', for the whole driver or one OSC address \(from list\_routes\). Give the firmware version, and the device's reply to the MIDI Identity Request \(F0 7E 7F 06 01 F7\) as identity\_hex when you can: trus
- `get\_trust`: How far a driver has been confirmed by people who used it, per firmware: status \(unreported, unconfirmed, usage-verified, firmware-dependent, failing, disputed\), how many users report it works / fails / partly works, each firmware's own status, the device identities seen for each firmware, and the s
- `report\_mapping`: Teach the catalogue which MIDI message a control really sends: after the user moved one control on the device \(see relay\_listen\), give the driver address it is \(from list\_routes\) — or, for a control the driver lacks, its panel label — and the CC, NRPN or note it sent, with the firmware and the devic
- `submit\_driver`: Contribute a driver for a device the catalogue lacks \(or a better one\): the full driver file as a JSON object, in the osc-bridge device schema \(device.name, device.vendor, device.osc\_prefix, and cc\_params / params / commands / triggers — see https://synthhub.roomi-fields.com/DEVICE\_JSON\_SCHEMA/\). It
- `submit\_fix`: Contribute a corrected variant of a driver from what the catalogue learned: where learned mappings \(get\_trust → mappings, differs: true\) disagree with the driver on one firmware, builds a copy of the driver with the learned CC / NRPN numbers, as a new file for that firmware, and queues it for the me
- `get\_contribution`: Where a contribution stands: pending \(waiting for the merge job\), merged \(with its pull request\), rejected \(with the reason\), or held \(its account is under review\).
- `share\_preset`: Share something the user made on a device with every SynthHub user, under CC BY-SA 4.0: a sound, a sequence or pattern, a kit, a project, a bank of their own sounds, or a MIDI clip any device can play. Its content: the device's own data \(SysEx, e.g. from backup\_presets\), settings by driver address \(
- `update\_preset`: Publish a new version of a preset this account shared: new content \(hex, file, settings or midi\_file\) makes a new version, kept with a change note — earlier versions stay available; the description fields alone change it in place. Someone else's preset: share yours with derived\_from instead.
- `find\_presets`: Search what SynthHub users shared \(CC BY-SA 4.0\): sounds, sequences, kits, projects, banks, MIDI clips. Filter by device, kind, category, genre, tag, author \(pseudonym\) or words; sort by newest, most popular \(favorites and real loads\) or most trusted \(confirmed on real devices\). Returns, per preset,
- `get\_preset`: One shared preset in full: its content \(SysEx hex, settings by driver address, MIDI file\), description and playing tips, versions with their change notes, what it was derived from and its derivatives \(remixes\), comments, preview URLs, author, licence and attribution line, trust and counts. Load it w
- `report\_preset`: Tell SynthHub how a shared preset behaved once loaded on a real device: 'works' \(it loaded and sounds as described\), 'fails' \(refused, wrong sound\), or 'factory' \(it is a factory preset or someone else's sound: presets that several users flag are hidden until reviewed\). Give the firmware.
- `withdraw\_preset`: Withdraw a preset this account shared: it is no longer listed nor served. Copies others already made stay under CC BY-SA.
- `comment\_preset`: Comment on a shared preset — how it sounds, how you used it, what you changed — optionally attaching your remix \(a preset you shared with derived\_from\). Comments are public at once. Also: remove one of this account's comments \(remove\), or flag someone else's as abusive or off-topic \(flag\); comments
- `favorite\_preset`: Mark a shared preset as a favorite of this account \(on: false to unmark\). Without id, lists this account's favorites.
- `preset\_collection`: Collections of shared presets, public, made by one account \(e.g. 'Dark basses for minilogue'\). action: create \(name, description\), rename \(collection, name, description\), add or remove \(collection, id\), delete \(collection\), get \(collection: its presets\), list \(this account's collections, or author:
- `follow\_author`: Follow an author of shared presets \(by pseudonym\), or stop \(on: false\); with author alone and on omitted, shows their page: profile, presets, followers. Without author, lists the newest presets of the authors this account follows.
- `set\_profile`: Set the display name and link \(https\) shown with this account's shared presets and comments, instead of its pseudonym alone. Ask the user what they want shown; both are public.
- `relay\_status`: Check a relay: the user opened https://synthhub.roomi-fields.com/connect/ \(or ran osc-bridge connect\) and gave you its pairing code. Returns the MIDI output and input ports of their machine. Nothing is sent to the hardware.
- `relay\_detect`: Find which devices are connected to the user's machine through a relay: sends the MIDI Identity Request \(F0 7E 7F 06 01 F7, changes nothing on the device\) to every output and matches the answers — manufacturer, model, firmware version — against the catalogue. Returns the best driver ids and identity
- `relay\_send`: Play or set something on the user's hardware through a relay: give a driver \(id or slug\) and one of its OSC addresses from list\_routes with its arguments \(e.g. address '/filter/cutoff', args \[64\]; '/note/on', args \[60, 100\]\) — the server turns it into the right CC, NRPN, note or SysEx message. Or gi
- `relay\_listen`: Listen to what the user's hardware sends through a relay for a few seconds: notes, CC, NRPN, SysEx, decoded. With a device, each CC or NRPN that moved is matched to the driver's OSC addresses — ask the user to move one control on the device while listening to learn which address it is, or to check t
- `load\_preset`: Load a shared preset \(find\_presets, get\_preset\) into the user's device through a relay: its settings are sent through the driver, its patch data as SysEx — which replaces the sound the device holds, so the relay asks the user to accept it and this call waits for the answer \(up to 2 minutes\): tell th
- `link\_account`: Link this account to the user's SynthHub account on the site: returns a one-time address \(valid 15 minutes\) for the user to open and sign in \(passkey, e-mail, Google or Discord\). Afterwards what this account shared appears under their profile, and they manage it — and their favorites, collections, c

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html