osc-bridgelisted

# osc-bridge ## Overview osc-bridge gives every synthesizer and music app a clean, named OSC surface: send `/grandmother/filter/cutoff 64` and the bridge translates it to the right MIDI CC, NRPN, or SysEx frame for that device. 849 hardware drivers plus 8 software targets (DAWs and live-coding environments). This skill drives it through the `osc-bridge` MCP server. ## Critical: two things must be true before anything makes sound **1. The MCP server needs the device catalogue, and npm does not ship it.** The published package contains only the binary; the 849 driver JSONs live in the git repo. `--devices-dir` defaults to the relative path `devices`, so a default install indexes **0 devices** and every device tool fails with `no device with slug '…'`. Clone the repo and point at it: ```json { "mcpServers": { "osc-bridge": { "command": "npx", "args": ["-y", "@roomi-fields/osc-bridge", "mcp", "--devices-dir", "/absolute/path/to/osc-bridge/devices"] } } } ``` Check the server's stderr for `indexed 849 device file(s)`. If it says `indexed 0`, the path is wrong — nothing else will work. **2. The MCP `send` tool talks to the *bridge*, not to the synth.** The MCP server opens no MIDI port. A separate bridge process must be running and listening, or messages vanish into a UDP void: ```bash # hardware — --out-port is required osc-bridge run --device devices/moog/grandmother.json \ --out-port 4 --bind 127.0.0.1:7777 --osc-client 127.0.0.1: