SSyncDev

Osc MCP Server

Declarative OSC bridge for music hardware and software — 849 synthesizer drivers (MIDI/SysEx) plus DAW & live-coding targets (Ableton, Bitwig

Local serverstdioGo

What is the Osc MCP Server?

Declarative OSC bridge for music hardware and software — 849 synthesizer drivers (MIDI/SysEx) plus DAW & live-coding targets (Ableton, Bitwig, Reaper, Sonic Pi

What it actually does

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).

  • CC / NRPN addresses are cryptic
  • SysEx byte formats are hand-rolled per device
  • Bidirectional state (what the device CURRENTLY knows) is hard to track

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

How to install the Osc MCP Server

{
  "mcpServers": {
    "osc-bridge": {
      "command": "npx",
      "args": ["-y", "@roomi-fields/osc-bridge"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • “Use Osc to N-to.”
  • “Use Osc to First.”
  • “Use Osc to Multi.”

Frequently asked questions

Declarative OSC bridge for music hardware and software — 849 synthesizer drivers (MIDI/SysEx) plus DAW & live-coding targets (Ableton, Bitwig, Reaper, Sonic Pi Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.