Connect your synth
Plug your synth into this computer, by USB or through a MIDI interface, and open this page in Chrome, Edge, Opera or Firefox. Nothing to install. Here you can find which device it is, then let your AI app play it.
Which devices are plugged in?
Press the button: SynthHub lists the devices plugged into this computer. One it does not recognise for sure, you identify in a few gestures (turn its knobs, answer a question), or name: it then starts its page for everyone.
Let your AI app play them
First find your devices above: your AI app then knows which one it plays. No synth at hand?
Recognised: . Your AI app (Claude or any app taking MCP servers) reaches them through this page: press the button, give it the code, and it can play them and set their sound by name ("set the filter cutoff to 64", "play middle C"). Keep the page open while it plays.
Not connected. Works in Chrome, Edge, Opera and Firefox; not in Safari.
Your code: ····-····
- In your AI assistant, add a remote MCP server (in Claude: Settings → Connectors → Add custom connector) with this address, once:
- Tell the agent:
- Keep this tab open while you play. Closing it ends the session.
The first agent to use a code is the only one that can drive your devices; a new code ends the session and pairs again.
What your AI app does
- The agent asks the server; the server sends MIDI messages to this page, which plays them on your device. Every message appears in the list above as it passes.
relay_detectasks each device who it is (the standard MIDI Identity Request, which changes nothing on it) and finds its driver and firmware.relay_sendsets a parameter or plays a note by its name in the driver.relay_listenhears what your device sends: turn a knob and the agent sees which parameter it is.take_soundtakes the sound your synth is playing, with its name, so the agent can share it once you say you made it. The page asks you before each step it cannot check by itself: finding the synth, if it does not answer the standard question, then asking it for its sound.
Trying it without a synth
Tick Add a virtual test synth: the page then offers a simulated device,
Test Synth, alongside your real ones. It
answers relay_detect like a real synth, and sends back everything it
receives, so relay_send followed by relay_listen shows the round trip.
Ask your agent: "Detect my devices, set the Test Synth's cutoff to 90 and
check what it sends back." The same synth is available on the command line
with osc-bridge connect --test-synth.
Tick Add the virtual FM-1 to hear it: the page loads the virtual FM-1, an emulated M-VAVE FM-1, and lists it as FM-1 (virtual) alongside your real devices once it has started: press Start in its frame. Your agent loads a sound from the catalogue into it and plays notes, exactly as on a real synth, and the page asks you before anything that would overwrite its memory. Unticking the box removes it.
Privacy
The server gives this browser an account — a random id, kept in this browser so you stay the same user next time; no sign-up, no personal data.
Sharing is on by default: the identity (model, firmware) of the devices your agent detects is recorded to improve the catalogue for everyone. Untick Share the identity of my devices to record none, or tick private next to one device to keep only that one out; this browser remembers which devices you made private. Your MIDI messages themselves are never recorded.
For security, the server keeps the address each request comes from for 30 days (our legitimate interest in protecting the service from abuse), then erases it. Details: API for agents.
Limits
- Safari and iOS do not give web pages access to MIDI devices; use Chrome or
Edge, or
osc-bridge connecton your computer. - Messages that can overwrite your device — every SysEx message except the Identity Request: patch dumps, stores, settings — are never sent without you. The page shows what the agent wants to send, and nothing goes out until you press Accept. Refuse sends nothing.
- Timing follows the network: fine for setting sounds and playing test notes, not for tightly timed sequences.