
osc-bridge
If you work with hardware synths or DAWs, this bridges 849 MIDI/SysEx devices and major music software (Ableton, Bitwig, Reaper, Sonic Pi, SuperCollider) through a unified OSC interface. Each device gets a JSON descriptor mapping cryptic CC numbers and SysEx frames to named OSC addresses. The MCP server exposes five tools: discover MIDI ports, list supported devices, fetch a device's OSC API spec, send OSC messages, and read integration docs. Useful for generative composition workflows where Claude orchestrates multiple synths, reconfigures controller layouts on the fly, or scripts parameter automation across your studio without hardcoding MIDI implementations.
- GitHub stars
- 10
- tools
- 9
- transport
- STDIO, HTTP
- last updated
- Oct 31, 2026
Tools
9 toolsPublic tool metadata for what this MCP can expose to an agent.
list_devicesLists the available devices.
Lists the available devices.
No parameter schema in public metadata yet.
get_device_docsRetrieves documentation for a device.
Retrieves documentation for a device.
No parameter schema in public metadata yet.
list_routesLists the OSC routes for a device.
Lists the OSC routes for a device.
No parameter schema in public metadata yet.
export_device
No parameter schema in public metadata yet.
sendSends OSC messages to synths and DAWs.
Sends OSC messages to synths and DAWs.
No parameter schema in public metadata yet.
get_status
No parameter schema in public metadata yet.
detect_hardware
No parameter schema in public metadata yet.
backup_presets
No parameter schema in public metadata yet.
restore_presets
No parameter schema in public metadata yet.
Sponsors
Readme
osc-bridge
Declarative OSC bridge for music hardware and software — and an MCP server to drive it from an LLM.
Details
- Repository
- github.com/roomi-fields/osc-bridge
- Website
- synthhub.roomi-fields.com
- Category
- Media & Entertainment
- Package
@roomi-fields/osc-bridge- Transport
- STDIO, HTTP
- Registry
- MCP registry, active