devices/behringer/kick.vendor.fw-2719418.json, updated 2026-10-31Edit on GitHubJSONCSVMIDNAMOSCQueryBehringer KICK running 0700-AAM firmware source at 2719418
The Behringer KICK MIDI implementation: 2 CC, each named, for Claude (MCP), SuperCollider or any OSC app.
- sourcemaker's documentation
- firmware2719418
- licenceAGPL-3.0
- Maker
- Behringer
- Firmware
- 0700-AAM firmware source at 2719418
- Source
- maker's documentation
- Licence
- AGPL-3.0
Communities
Share and load its sounds
Plug the Behringer KICK into your computer, open shared presets in Chrome, Edge or Opera and press Connect my synth: SynthHub finds it, takes the sound it plays and names it. Sounds others shared for it load from their page the same way.
https://github.com/MusicTribeOpenSource/0700-AAM · AGPL-3.0
MIDI controls
2 controls, from the source at 0700-AAM firmware source at 2719418
Channel messages
| Control | CC | Range | Name to send |
|---|---|---|---|
| Modulation | 1 | 0–127 | /kick/modulation |
| All notes off | 123 | trigger | /kick/all_notes_off |
Use it
Find the MIDI ports, then start the bridge with this driver:
osc-bridge detect # prints the ready-to-run line for what is plugged in
osc-bridge run --device behringer/kick.vendor.fw-2719418 --out-port <N> --in-port <M>
Then send OSC to 127.0.0.1:7777, for example:
osc-bridge osc-send /kick/modulation 63
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as kick: ask “what can the Behringer KICK do?” and it reads this map with list_routes. See the MCP guide.
Limitations
Minimal driver, read from the AGPL-3.0 firmware source at commit 2719418 (no published firmware version; no manual: the product is announced without one). Received only: notes with velocity, CC1 and CC123. No SysEx and no NRPN. The received MIDI clock is ignored (Kick/modules/engine/audio_engine/engine/mt_audio_manager.cpp:73-76). No Start/Stop handling was found in this commit (absence measured by searching the repository). The clock the KICK sends was not read. No OSC and no RTP-MIDI. The network port has no known service (SSH only). The pads are tied to no instrument and no fixed pitch: the trigger note follows pad + 16 x bank (see the notes of the note routes). The default MIDI channel is unknown. USB MIDI is not proven. Untested on hardware.
Frequently asked questions
How many parameters of the Behringer KICK can be controlled over MIDI?
SynthHub's map of the Behringer KICK lists 2 MIDI CC parameters, each with its number, range and a readable name; the full chart is on this page.
Can an AI agent like Claude control the Behringer KICK?
Yes: SynthHub's hosted MCP server knows the Behringer KICK's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.