Agents Index

osc-bridge

Online

OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.

Visit publisherConnectJSON

What it can do: 29 tools

  • list_devices read-onlyFind device drivers in the catalogue of 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'). Retur
  • get_device_docs read-onlyFetch 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 read-onlyReturn 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.
  • export_device read-onlyWrite one driver in a format other tools read: 'oscquery' gives its OSC namespace as OSCQuery JSON (every route with type tags, ranges and access, for OSC controllers and browsers); 'midnam' gives its MIDI names as a MID
  • report_resultTell 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
  • get_trust read-onlyHow 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, eac
  • report_mappingTeach 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
  • submit_driverContribute 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 / comm
  • submit_fixContribute 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 lear
  • get_contribution read-onlyWhere 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_presetShare 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 d
  • update_presetPublish 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
  • find_presets read-onlySearch 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 stars, most loaded i
  • get_preset read-onlyOne 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,
  • report_presetTell 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 t
  • withdraw_presetWithdraw a preset this account shared: it is no longer listed nor served. Copies others already made stay under CC BY-SA.
  • comment_presetComment 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 com
  • star_presetStar a shared preset for this account, as on GitHub (on: false takes the star back). Without id, lists the presets this account starred.
  • preset_collectionCollections 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 (collectio
  • follow_authorFollow 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 accoun
  • set_profileSet the public profile shown on this account's author page and with its shared presets and comments, instead of its pseudonym alone: display name, link (https), a few words, the presets put first, where they are, more li
  • relay_status read-onlyCheck 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, and devices: the driver the u
  • relay_detect read-onlyFind 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, fi
  • relay_sendPlay 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, 1
  • relay_listen read-onlyListen 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 c
  • take_soundTake the sound the user's synth is playing — or one of its stored programs — straight from the synth through a relay, with its name. The synth is found among those SynthHub's librarian can talk to (the KnobKraft Orm adap
  • load_presetLoad 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
  • link_accountLink 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 appea
  • claim_presetsClaim presets SynthHub imported from another site (their page says 'imported', with the author's name and page there) when the user is that author: give the id of one of them; the server answers with a code for the user

Connect it

Claude Code
claude mcp add --transport http osc-bridge https://mcp.synthhub.roomi-fields.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.synthhub.roomi-fields.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "osc-bridge": {
      "url": "https://mcp.synthhub.roomi-fields.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "osc-bridge": {
      "type": "http",
      "url": "https://mcp.synthhub.roomi-fields.com/mcp"
    }
  }
}

Questions

What does osc-bridge do?

OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP. It exposes 29 tools to AI assistants.

What tools does osc-bridge provide?

29 tools, including list_devices, get_device_docs, list_routes, export_device, report_result, get_trust, report_mapping, submit_driver, submit_fix, get_contribution, share_preset, update_preset….

How do I connect osc-bridge to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.synthhub.roomi-fields.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does osc-bridge require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is osc-bridge online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes osc-bridge?

@roomi-fields on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Analytics & BI