Behringer WING MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Behringer WING MCPset fader on channel 1 to -6 dB"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Behringer WING MCP
Model Context Protocol (MCP) server for Behringer WING digital mixers.
The server exposes a small, practical toolset for controlling a WING, WING Compact, or WING Rack from an MCP client. It talks to the console over OSC/UDP and uses stateless request/response calls so it can coexist with other WING integrations on the same network.
Current status
This is an early open-source implementation. The typed tools cover common strip operations:
set fader level
adjust fader level relatively
mute or unmute a strip
set pan
set scribble-strip name
find/list strips by scribble-strip name
set bus send level from typed source/destination fields
read a small strip status snapshot
read or write a raw OSC address as an escape hatch
The code can be built and tested without a console. Actual OSC calls require a WING on the same network.
Related MCP server: Ableton Live MCP Server
Requirements
Node.js 20 or newer
A Behringer WING-family console reachable on the network
OSC enabled and unlocked on the console
The WING OSC service uses UDP port 2223 by default. The console also has a
TCP control surface on port 2222, but this MCP server uses OSC only.
Install from source
git clone https://github.com/ralfferreira/behringer-wing-mcp.git
cd behringer-wing-mcp
npm ci
npm run buildConfigure the console
On the console, open the remote/network settings and make sure:
OSC remote control is enabled
OSC remote lock is off
the console has an IP address reachable from the machine running the MCP server
Avoid exposing the console network to the public internet. The OSC control surface is intended for trusted local networks.
Configure an MCP client
Build the project first, then point your MCP client at dist/index.js.
Example:
{
"mcpServers": {
"wing": {
"command": "node",
"args": ["/absolute/path/to/behringer-wing-mcp/dist/index.js"],
"env": {
"WING_HOST": "192.168.1.50"
}
}
}
}Windows example path:
{
"mcpServers": {
"wing": {
"command": "node",
"args": ["C:/Users/USER/Documents/Code/behringer-wing-mcp/dist/index.js"],
"env": {
"WING_HOST": "192.168.1.50"
}
}
}
}Environment variables
Variable | Required | Default | Description |
| yes | - | Console IP address or hostname. |
| no |
| OSC UDP port. |
| no |
| Timeout for one OSC request/response. |
| no |
| Set to |
Tools
Tool | Description |
| Set a strip fader level in dB. |
| Change a strip fader relatively by a dB delta. |
| Mute or unmute a strip. |
| Set strip pan from |
| Set a strip scribble-strip name. |
| Read name, fader, mute, and pan for one strip. |
| Search scribble-strip names across strip kinds. |
| Read a compact live list of strip IDs and names, optionally with status. |
| Set a channel, aux, or bus send level to a bus destination. |
| Read any raw OSC address. |
| Write any raw OSC address, then read it back. |
Supported typed strip kinds:
Kind | Range | Notes |
|
| Main input channels. |
|
| Aux input channels. Together, |
|
| Buses. |
|
| Main buses. |
|
| Matrices. |
|
| DCAs in the remote-control model. |
Natural-language helper examples
These tools are meant to let MCP clients work from plain prompts without needing to know every OSC leaf.
adjust_fader kind="ch" index=12 delta_db=-3
find_strip_by_name query="pastor mic"
list_strips kinds=["ch","aux","bus"] include_status=false
set_bus_send source_kind="ch" source_index=1 bus=5 db=-12 enabled=truefind_strip_by_name returns ranked matches with kind, index, id, name,
and score. If multiple matches have the same top score, prefer calling write
tools with an explicit kind and index.
list_strips performs live request/response reads. By default it reads strip
names only for a compact map of IDs to labels; set include_status=true to also
read fader, mute, and pan values.
set_bus_send writes /<source>/<index>/send/<bus>/lvl and accepts source
kinds ch, aux, and bus. When enabled is provided, it also writes the
send on state. Like every write helper, it is blocked by WING_READ_ONLY=true.
Raw OSC examples
Use raw OSC tools for parameters not yet covered by typed tools:
osc_get address="/ch/1/fdr"
osc_set address="/ch/1/mute" value=1 force_type="i"
osc_set address="/ch/1/name" value="Lead Vox" force_type="s"Raw writes can affect a live mix immediately. Use WING_READ_ONLY=true when
you only want to inspect values.
Development
npm ci
npm test
npm run buildUseful scripts:
npm run buildcompiles TypeScript intodist/npm testbuilds and runs offline unit testsnpm run devstarts TypeScript watch modenpm startruns the built server
To try the server with the MCP Inspector:
WING_HOST=192.168.1.50 npx @modelcontextprotocol/inspector node dist/index.jsPowerShell:
$env:WING_HOST = "192.168.1.50"
npx @modelcontextprotocol/inspector node dist/index.jsProject layout
src/index.ts MCP server and tool definitions
src/osc.ts Minimal OSC encoder/decoder and UDP client
src/wing.ts WING address helpers and typed operations
src/*.test.ts Offline tests for OSC and address helpersReferences
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ralfferreira/behringer-wing-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server