A
licenseNot graded
qualityB
maintenanceLocal MCP bridge for Bitwig Studio, enabling read-back-verified control of tracks, devices, transport, and plug-in parameters via any MCP client.
3
MIT
osc-bridge
Server Details
OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- roomi-fields/osc-bridge
- GitHub Stars
- 10
- Server Listing
- osc-bridge
- ChatGPT
- –
- Claude
- –
TDQS
A3.8/5.0
Scored across 29 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions, and the descriptions help separate similar areas such as find/get/load/share/update/withdraw preset. The preset tooling is crowded, several tools bundle multiple actions (comment_preset, preset_collection, follow_author), and relay_detect/listen/status can be confused under time pressure.
Naming Consistency4/5
Names are consistently snake_case and mostly verb_noun, making the set predictable. Minor deviations include preset_collection as a noun-only name and the relay_* tools using a resource prefix rather than a verb-first pattern.
Tool Count3/5
The server covers a genuinely broad domain—presets, device drivers, hardware relay, trust/reporting, account/profile—so the surface is not arbitrary. Still, 29 tools is heavy for an agent-facing server, and several multi-action tools could be consolidated or split to reduce selection burden.
Completeness4/5
The surface covers the main lifecycle: preset discovery, retrieval, loading, sharing, updating, withdrawing, commenting, starring, collections, device lookup/routes/docs, driver contribution/fixes, relay interaction, trust, reporting, claiming, and account linking/profile. Gaps are minor, such as audio preview upload being documented only as an external PUT endpoint and no account-unlink operation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Create, co-edit, analyze, publish, and export collaborative step-sequencer sessions through MCP.
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
MCP server for Producer/Riffusion AI music generation
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for the Behringer DeepMind 12 synthesizer. Gives AI agents real-time control over synth parameters via MIDI NRPN, plus edit-buffer snapshots via SysEx.28 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Ableton Live through a Max for Live device and optional Remote Script, covering tracks, clips, MIDI notes, mixer settings, transport, and plugin search and insertion.1MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to control SuperCollider audio synthesis via OSC, supporting melody, rhythm, and soundscape generation through MCP tools.1327MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.