XR18 MCP Server
Click on "Deploy 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., "@XR18 MCP Server Raise guitar in monitor 1 by 2 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.
XR18 MCP Server
An MCP server that controls a Behringer XR18 over its OSC UDP interface. The
client implementation is xr18; mixer commands are sent to UDP port 10024.
The command registry is based on doc/paramenters.txt, the supplied X AIR OSC
protocol PDF, and the Behringer World X-Air OSC reference. Generic raw tools
provide complete access to documented paths, including firmware-specific paths
that do not have a dedicated semantic MCP tool.
Requirements
Python 3.12 or newer
An XR18 reachable over the network
Related MCP server: X32/M32 MCP Server
Install and run
uv sync
XR18_HOST=192.168.1.100 uv run xr18-mcpConfiguration environment variables:
XR18_HOST(required): mixer IP address or hostnameXR18_PORT(optional): OSC UDP port; defaults to10024XR18_TIMEOUT(optional): request timeout in seconds; defaults to2
MCP configuration
Use stdio in an MCP client configuration. Replace the directory with this project's absolute path.
{
"mcpServers": {
"xr18": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/xr18", "xr18-mcp"],
"env": {
"XR18_HOST": "192.168.1.100"
}
}
}
}Tools
Mixer-assistant tools, which speak dB rather than raw protocol values:
xr18_list_channels,xr18_resolve_channel(regular channels, AUX, FX returns, monitor buses, FX sends, LR, and DCAs)xr18_get_send_db,xr18_set_send_db,xr18_adjust_send_dbxr18_get_fader_db,xr18_set_fader_db,xr18_adjust_fader_db
Send 1–6 are the monitor buses and send 7–10 are FX sends 1–4. Source names can resolve regular channels, the AUX return, FX returns, monitor buses, FX send masters, LR, and DCAs. Destination arguments accept numeric buses, canonical identifiers such as bus/5 and fxsend/2, or configured destination names. fxsend/2 maps to channel send slot 08.
Low-level and administrative tools:
xr18_info,xr18_status,xr18_enable_remotexr18_get,xr18_set,xr18_triggerxr18_list_commands,xr18_describe_commandxr18_read_metersfor batches0through9; returned values are dBxr18_channel_set_fader,xr18_channel_set_mutexr18_headamp_set_phantomxr18_snapshot_load,xr18_snapshot_save,xr18_snapshot_delete, andxr18_snapshot_set_scope
Use xr18_describe_command before writing an unfamiliar raw OSC path. Native
XR18 float values are normalized between 0.0 and 1.0; integers and strings
follow the parameter documentation.
Examples of raw paths:
/ch/01/mix/fader
/ch/01/gate/on
/ch/01/eq/1/g
/bus/1/mix/on
/routing/p16/01/src
/fx/1/typeMixer assistant agent (llama.cpp)
agents/mixer_assistant is a Google ADK agent that turns plain-language
requests into mixer changes, running against a local llama.cpp server. It
understands English and Italian.
"raise 1 dB of guitar in monitor 5"
"lower the kick 2 dB in wedge 3"
"set lead vocal fader to -6 dB"
"alza di 1 dB la chitarra nel monitor 5"
"mute channel 8"1. Start llama.cpp
Tool calling requires the --jinja flag. Without it the model returns prose and
no mixer command is ever issued.
llama-server --jinja -fa on -hf bartowski/Qwen2.5-7B-Instruct-GGUF:Q4_K_M --port 8080Use a model with a native tool-calling template. Qwen 2.5, Llama 3.1/3.3,
Hermes 2/3, Mistral Nemo, and Functionary are supported natively. Avoid
aggressive KV cache quantization such as -ctk q4_0, which measurably degrades
tool-calling accuracy.
2. Run the agent
cp agents/.env.example agents/.env # then edit XR18_HOST
cd agents
uv run adk run mixer_assistant # terminal chat
uv run adk web # browser chatConfiguration:
XR18_HOST,XR18_PORT,XR18_TIMEOUTfor the mixerLLAMA_API_BASEdefaults tohttp://localhost:8080/v1LLAMA_MODELdefaults toqwen2.5-7b-instruct
Source resolution examples
The assistant distinguishes a source strip from a destination send:
"raise 1 dB of guitar in monitor 5" -> source guitar, send 5
"raise 1 dB of aux in monitor 2" -> source AUX return, send 2
"raise reverb in monitor 3" -> source named FX return, send 3
"raise monitor 5 fader" -> source monitor bus 5 fader
"lower delay send 2 fader" -> source FX send master 2 faderBare aux, aux in, and aux input resolve to /rtn/aux. Configured strip
names are read from the mixer and take precedence over generic labels. Ambiguous
names are rejected rather than guessed.
Design notes
All gain mathematics is done in Python, never by the model. The model may only pass a delta such as
1.0toxr18_adjust_send_db. Relative changes are a single atomic read-modify-write inside the MCP server.The tool surface is filtered to 9 tools. Local 7B models select tools far less reliably when shown all 24, so raw OSC and console administration are hidden from the agent.
Instrument names resolve from the mixer's scribble strips first, then from
agents/mixer_assistant/aliases.json. Ambiguous names raise an error and the agent asks which channel is meant rather than guessing.The agent cannot enable phantom power, initialize the console, delete snapshots, or change network settings.
OSC write behavior
XR18 parameter writes are fire-and-forget by default because XR18 firmware does
not reliably echo set messages. Query operations still wait for a mixer reply.
The absolute MCP setter tools support verify=true to issue a separate readback
query after writing:
xr18_set_send_db(source="ch/03", bus="bus/5", db=-4, verify=true)
xr18_set_fader_db(source="ch/03", db=-6, verify=true)Relative adjustments read the current value, send the new value without waiting, and return the expected resulting dB value.
Safety
The server requires confirm=true for console initialization, applying network
settings, snapshot deletion, and phantom power changes. Network updates can
disconnect the MCP server from the mixer. The XR18 ignores /-action/setclock.
/xremote subscriptions expire after ten seconds, so call
xr18_enable_remote periodically while listening for parameter changes.
Test
uv run pytestCanonical resolver identifiers can be passed directly to later tools: ch/10, rtn/aux, rtn/1, bus/5, fxsend/2, lr, and dca/1.
Available Tools
25 toolsxr18_adjust_fader_dbA
Change a channel's main mix fader by a relative amount in dB.
Use a positive delta_db to raise and a negative delta_db to lower.
Inputs: source (required), delta_db (required). Returns: object
xr18_adjust_send_dbA
Change a source send level by a relative dB amount.
bus accepts a number, bus/5, fxsend/2, monitor/wedge name, or configured destination name. Positive delta_db raises the level.
Inputs: bus (required), source (required), delta_db (required). Returns: object
xr18_channel_set_faderB
Set a source fader with the native normalized 0.0-1.0 value.
Inputs: source (required), normalized_value (required).
xr18_channel_set_muteB
Mute or unmute a channel, AUX, FX, bus, LR, or DCA source.
Inputs: muted (required), source (required).
xr18_describe_commandC
Validate a concrete OSC path and return its registry metadata.
Inputs: path (required). Returns: object
xr18_enable_remoteA
Enable XR18 remote updates for ten seconds; call periodically to keep them active.
Inputs: no named parameters. Returns: Generic wrapper for non-object return types.
xr18_getB
Get a mixer parameter using its exact, native OSC value.
Inputs: path (required).
xr18_get_fader_dbB
Read a channel's main mix fader level in dB.
Inputs: source (required). Returns: object
xr18_get_send_dbA
Read a source send level in dB.
bus accepts 1-6, a canonical identifier such as bus/5 or fxsend/2, or a configured monitor/FX send name such as Vocal Monitor.
Inputs: bus (required), source (required). Returns: object
xr18_headamp_set_phantomB
Set physical preamp phantom power. This requires confirm=true.
Inputs: enabled (required), headamp (required), confirm.
xr18_infoC
Return the mixer identity and firmware information.
Inputs: extended. Returns: Generic wrapper for non-object return types.
xr18_list_channelsA
List every named source strip and its current fader level in dB.
Includes regular channels, AUX, FX returns, monitor buses, FX send masters, LR, and DCAs.
Inputs: no named parameters. Returns: Generic wrapper for non-object return types.
xr18_list_commandsA
List documented command templates. Use a prefix such as '/ch' or '/routing'.
Inputs: prefix. Returns: Generic wrapper for non-object return types.
xr18_read_metersA
Read meter batch 0-9 in dB. Batch 0 requires zero-based channel 0-31.
Inputs: batch_id (required), channel. Returns: Generic wrapper for non-object return types.
xr18_resolve_channelB
Resolve a regular channel, AUX, FX, bus, LR, or DCA by name.
The legacy tool name is retained for compatibility; its result now contains the unified source identifier used by the other assistant tools.
Inputs: name (required). Returns: object
xr18_setA
Set a registered mixer parameter using its native OSC value.
Float controls use the XR18's normalized 0.0-1.0 protocol range. Use xr18_describe_command before setting unfamiliar controls.
Inputs: path (required), value (required).
xr18_set_fader_dbC
Set a channel's main mix fader to an absolute dB value.
Inputs: db (required), source (required), verify. Returns: object
xr18_set_send_dbC
Set a source send level to an absolute dB value.
Inputs: db (required), bus (required), source (required), verify. Returns: object
xr18_snapshot_deleteA
Delete snapshot slot 1-64. This requires confirm=true.
Inputs: slot (required), confirm.
xr18_snapshot_loadA
Recall snapshot slot 1-64.
Inputs: slot (required).
xr18_snapshot_saveB
Save the current mixer state to snapshot slot 1-64.
Inputs: slot (required).
xr18_snapshot_set_nameC
Set an indexed snapshot name.
Inputs: name (required), slot (required).
xr18_snapshot_set_scopeB
Set a snapshot recall-scope index from 0 through 59.
Inputs: slot (required), scope (required).
xr18_statusA
Return XR18 status, IP address, and server name.
Inputs: no named parameters. Returns: Generic wrapper for non-object return types.
xr18_triggerC
Trigger an action. Console initialization and network updates require confirm=true.
Inputs: path (required), value, confirm. Returns: Generic wrapper for non-object return types.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 25 tools
Most tools are clearly distinct by purpose (e.g., snapshots, meters, sends, faders), but there is overlap in how fader levels can be manipulated (xr18_set, xr18_channel_set_fader, xr18_set_fader_db), which could lead to misselection. Descriptions are detailed enough to reduce ambiguity.
Naming is mixed: some tools follow xr18_<action> (get, set, trigger), others xr18_<object>_<action> (snapshot_load, channel_set_fader), and still others xr18_<action>_<object> (get_fader_db, set_send_db). This inconsistency, while readable, could confuse an agent expecting a uniform pattern.
25 tools is on the high end of the acceptable range, but justified for a complex mixer server covering channels, sends, snapshots, meters, and status. The count is not excessive given the domain scope.
The tool set covers core mixing operations (faders, mutes, sends), snapshots (load/save/delete/scope/name), channel listing/resolution, meters, and status. Generic get/set allow access to any parameter, filling potential gaps. Missing dedicated EQ or effect tools are mitigated by the generic interface.
Maintenance
Related MCP Connectors
OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Agent-native XRPL infrastructure: 19 paid MCP tools, x402 USDC on Base, non-custodial XRPL actions.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables control of digital mixers (Behringer X32, Midas M32) through natural language commands in Claude Desktop, supporting fader control, muting, EQ, dynamics, effects, scenes, routing, and more via OSC protocol.5217MIT
- AlicenseAqualityDmaintenanceEnables control of Behringer X32/M32 digital mixing consoles via OSC protocol for remote mixing, automated setup, and live adjustments through an AI assistant.2424 npmMIT
- AlicenseNot gradedqualityBmaintenanceConnects AI coding agents to PreSonus StudioLive III mixers over the local network, exposing live mixer context such as channel names, mute/solo/fader state, Fat Channel compressor/EQ models, and meter activity as MCP resources and tools for reading and reasoning about live sound engineering.1MIT
- AlicenseAqualityCmaintenanceEnables controlling Behringer WING digital mixers via OSC, supporting fader, mute, pan, and name operations on strips, with raw OSC access for unsupported parameters.118MIT