Skip to content

Build a tool for your synth with AI

Ask your AI app for an editor, a randomiser or a script for your synth. On its own it guesses the CC numbers and SysEx messages, often wrongly. With SynthHub added to it, it reads them here: every control, message and drum sound of 977 synths, drum machines, controllers and DAWs, with where each one comes from and how far it has been checked on the real device.

1. Connect your AI app

Nothing to install, no sign-up. Pick your app below; your personal address keeps the same account from one session to the next.

Your personal address needs JavaScript; meanwhile add https://mcp.synthhub.roomi-fields.com/mcp to your app as a remote MCP server.

Your app has no place for an MCP server? Give it the address of the device's file instead: https://synthhub.roomi-fields.com/api/v1/devices/<vendor>/<driver>.json (each device page links to it). The catalogue finds the device.

2. Ask for your tool

Name the device and what you want. A few to start from:

  • "Build me a web page with a slider for every control of my KORG minilogue, sending MIDI from the browser."
  • "Write a Python script that sends random but musical filter and envelope settings to my Novation Bass Station II every bar."
  • "My M-VAVE FM-1 runs the ChoralRoot firmware: what can I control over MIDI, and which controls does it add?"
  • "Make a MIDNAM file of my Elektron Model:Samples for my DAW."
  • "Which controls of my Moog Subsequent 37 are 14-bit, and how do I send them?"

The app looks the device up, reads its controls and messages, and builds from them. Each control comes with its source; one checked on the device by other users says so.

With your synth plugged in

Open Connect your synth in Chrome or Edge and give the pairing code to your app. It can then find what is plugged in, play and set it, listen to what you move on it, and take the sound it is playing, asking you before anything that could overwrite the synth's memory. Try:

  • "Find what's connected and play a C minor chord on it."
  • "I'll move the cutoff knob: check that the catalogue has it right."
  • "Take the sound my synth is playing and save it."

3. Give back

What you and your app find makes the catalogue better for everyone:

  • It works, or it doesn't: your app reports it for your firmware, and three users agreeing make it trusted on that firmware.
  • A control is missing or wrong: your app checks what the control really sends and contributes the correction, credited to its account.
  • A sound you made: share it with its name, credited to you, from your app or from the device's page.

What your app can rely on

  • Every device's file says where its data comes from: the maker's documentation, a community source, or a test on the device; and for which firmware.
  • Addresses that read alike from one device to the next (/filter/cutoff, /program/recall), turned into the right CC, NRPN, note or SysEx for each.
  • The data is free to reuse with its credit. The details, every request and every tool: API for agents.