Declarative OSC bridge for music hardware and software — 849 synthesizer drivers (MIDI/SysEx) plus DAW & live-coding targets (Ableton, Bitwig
Declarative OSC bridge for music hardware and software — 849 synthesizer drivers (MIDI/SysEx) plus DAW & live-coding targets (Ableton, Bitwig, Reaper, Sonic Pi, SuperCollider). Ships an MCP server: a MIDI MCP and OSC MCP for controlling. The osc mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.
849 hardware synthesizers over MIDI / SysEx, plus DAWs and live-coding environments over OSC (Ableton, Bitwig, Reaper, Sonic Pi, SuperCollider, Pure Data, TouchDesigner, VCV Rack). Every device gets a clean, named OSC surface described by one JSON file. Drive it from a live-coding client, a DAW, a script, the CLI — or from Claude via the built-in MCP server (a MIDI MCP and OSC MCP).
Everything the assistant can do here goes through one of these:
N-to — N orchestration.** One process can drive several synths at once (osc-bridge orchestrate --config bridge.toml), each reachable under its own OSCFirst — class reconfigurable controllers (Electra One MK2).** Upload a generated preset as one OSC call; the bridge parses the JSON, reconfigures the deviceMulti — block SysEx emission** (ob.emit_sysex) — the upload script emitsStatus — CountSend — ReceiveTarget — ModeInstallation goes through your MCP client rather than a global install: point it at @roomi-fields/osc-bridge on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Osc's toolset — N-to, First, Multi and 3 more — is a fair guide to whether it matches your workflow. It is maintained by roomi-fields; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| N-to | N orchestration.** One process can drive several synths at once (osc-bridge orchestrate --config bridge.toml), each reachable under its own OSC prefix — so two MatrixBrutes live side-by-side as /matrixbrute-1 and /matrix |
| First | class reconfigurable controllers (Electra One MK2).** Upload a generated preset as one OSC call; the bridge parses the JSON, reconfigures the device over SysEx, and *dynamically* rewires its own CC↔OSC routing so each kn |
| Multi | block SysEx emission** (ob.emit_sysex) — the upload script emits |
| Status | Count |
| Send | Receive |
| Target | Mode |
{
"mcpServers": {
"osc-bridge": {
"command": "npx",
"args": ["-y", "@roomi-fields/osc-bridge"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.