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., "@X32/M32 MCP Server Set channel 1 volume to -10 dB and unmute it"
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.
MCP server for controlling Behringer X32/M32 digital mixing consoles via OSC protocol.
Remote Mixing: Control your X32/M32 from anywhere on the network
Automated Setup: Quickly configure channels for rehearsals or shows
Batch Operations: Apply settings to multiple channels at once
Documentation: Query and document current mixer settings
Troubleshooting: Check mixer state without physical access
Live Adjustments: Make quick changes during performances via AI assistant
Related MCP server: Eos MCP
32 input channels with volume, gain, mute, solo, EQ, pan control
16 mix buses for aux sends and monitor mixes
8 FX racks with parameter control
Main/monitor output control
Direct OSC parameter access for advanced users
npm install -g x-m32-mcp-serverOr from source:
git clone https://github.com/GoBeromsu/X32-MCP.git
cd X32-MCP
npm install && npm run buildAdd to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"x32": {
"command": "npx",
"args": ["x-m32-mcp-server"]
}
}
}connection_connect with host="192.168.1.100" and port=10023Tool | Parameters |
Connection (4) | |
|
|
| - |
| - |
| - |
Channel (8) | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bus (4) | |
|
|
|
|
|
|
|
|
FX (3) | |
|
|
|
|
|
|
Main/Monitor (3) | |
|
|
|
|
|
|
Low-Level (2) | |
|
|
|
|
Unity Gain: 0 dB = 0.75 linear (neutral, no boost/cut)
Safe Start: Begin with channel at -20 dB and muted
Channel Colors: Use colors to organize (red=vocals, blue=drums, etc.)
Bus Usage: 1-4 monitors, 5-6 FX sends, 7-8 recording, 9-16 IEM/matrix
Network: X32 uses port 10023, connect to same network as computer
channel: 1-32
bus: 1-16
fx: 1-8
unit: "linear" (0.0-1.0) or "db" (-90 to +10)
muted/solo/bypass: true/false
pan: -100 to +100, "L50"/"C"/"R50", or 0.0-1.0
color: "red", "green", "blue", etc. or 0-15
band: 1-4 (EQ bands)
parameter: "f" (frequency), "g" (gain), "q" (Q factor)
Volume linear: 0.0-1.0 (unity = 0.75)
Volume dB: -90 to +10 (unity = 0 dB)
Gain: 0.0-1.0
FX parameter: 0.0-1.0
Channel name: max 12 characters
MIT
Get the complete state of a mix bus including fader level, on/off status, and other key parameters. Returns all values in both linear and human-readable formats.
Inputs: bus (required).
Mute or unmute a specific mix bus on the X32/M32 mixer. This controls the bus on/off state.
Inputs: bus (required), muted (required).
Set the send level from a channel to a mix bus. This controls how much of the channel signal is sent to the bus. Supports both linear values (0.0-1.0) and decibel values (-90 to +10 dB).
Inputs: bus (required), value (required), channel (required), unit.
Set the fader level (volume) for a specific mix bus on the X32/M32 mixer. Supports both linear values (0.0-1.0) and decibel values (-90 to +10 dB). Unity gain is 0 dB or 0.75 linear.
Inputs: bus (required), value (required), unit.
Mute or unmute a specific input channel on the X32/M32 mixer. This controls the channel on/off state.
Inputs: muted (required), channel (required).
Set the strip color for a specific input channel. Colors help visually organize channels on the mixer.
Inputs: color (required), channel (required).
Configure a specific EQ band on an input channel. The X32/M32 has 4 parametric EQ bands per channel.
Inputs: band (required), value (required), channel (required), parameter (required).
Set the preamp gain for a specific input channel on the X32/M32 mixer. This controls the input gain stage before the channel processing.
Inputs: gain (required), channel (required).
Set the name/label for a specific input channel. Maximum 12 characters for X32/M32.
Inputs: name (required), channel (required).
Set the stereo pan position for a channel. Accepts percentage (-100 to +100), LR notation (L50, C, R100), or linear values (0.0-1.0).
Inputs: pan (required), channel (required).
Set the fader level (volume) for a specific input channel on the X32/M32 mixer. Supports both linear values (0.0-1.0) and decibel values (-90 to +10 dB). Unity gain is 0 dB or 0.75 linear.
Inputs: value (required), channel (required), unit.
Solo or unsolo a specific input channel on the X32/M32 mixer. This routes the channel to the solo bus for isolated monitoring.
Inputs: solo (required), channel (required).
Establishes a connection to an X32 or M32 digital mixing console using the OSC (Open Sound Control) protocol. Use this tool when you need to control mixer functions remotely. The mixer must be powered on and connected to the same network.
Inputs: host (required), port.
Disconnects from the currently connected X32 or M32 digital mixing console. Use this tool to cleanly terminate the OSC connection when mixer control is no longer needed.
Inputs: no named parameters.
Retrieves detailed console information from connected X32 or M32 digital mixing console. Returns model name, firmware version, server details, and other system information useful for identifying mixer capabilities and troubleshooting.
Inputs: no named parameters.
Retrieves the current operational status of the connected X32 or M32 digital mixing console. Returns connection state, network information, and server details to monitor mixer availability and network configuration.
Inputs: no named parameters.
Bypass or enable a specific effects rack on the X32/M32 mixer. Bypassing an effect allows the audio to pass through unprocessed while retaining the effect settings.
Inputs: fx (required), bypass (required).
Get the current state of a specific effects rack on the X32/M32 mixer. Returns the effect type and parameter values.
Inputs: fx (required).
Set a parameter value for a specific effects rack on the X32/M32 mixer. The X32/M32 has 8 effects racks (1-8), each with multiple parameters (01-64). Parameter numbers and ranges vary by effect type.
Inputs: fx (required), value (required), parameter (required).
ADVANCED/LOW-LEVEL TOOL: Retrieves current parameter values from X32/M32 mixer using raw OSC address patterns. Consider using semantic tools (channel_*, bus_*, etc.) for common operations. Use this tool for parameters not covered by semantic tools or for debugging purposes.
Inputs: address (required).
Mute or unmute the main stereo output on the X32/M32 mixer. This controls the master output on/off state.
Inputs: muted (required).
Set the main stereo output fader level on the X32/M32 mixer. Supports both linear values (0.0-1.0) and decibel values (-90 to +10 dB). Unity gain is 0 dB or 0.75 linear.
Inputs: value (required), unit.
Set the monitor output fader level on the X32/M32 mixer. Supports both linear values (0.0-1.0) and decibel values (-90 to +10 dB). Unity gain is 0 dB or 0.75 linear.
Inputs: value (required), unit.
ADVANCED/LOW-LEVEL TOOL: Controls X32/M32 mixer parameters by setting specific values via raw OSC address patterns. Consider using semantic tools (channel_*, bus_*, etc.) for common operations. Use this tool for parameters not covered by semantic tools or for advanced automation.
Inputs: value (required), address (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 24 tools
Each tool targets a distinct combination of mixer resource (channel, bus, FX, main, monitor, connection) and action. Groups are clearly separated, and the low-level get/set_parameter tools are explicitly marked as advanced, so no ambiguity exists.
The majority of tools follow an object_verb pattern (e.g., channel_set_volume, bus_mute, fx_bypass), but the low-level tools get_parameter and set_parameter invert the pattern, and connection_connect is slightly redundant. These are minor deviations from an otherwise consistent convention.
With 24 tools, the set is on the heavier side of the ideal range, but the complexity of a digital mixer justifies the coverage of channels, buses, FX, main, monitor, and connection. No tools feel redundant.
The server provides comprehensive control over channels, buses, FX, main, and monitor, but lacks high-level state retrieval for several resources (e.g., channel_get_state, main_get_state). Agents must rely on the low-level get_parameter for these reads, which is a notable gap in the semantic surface.
Compose, mix, master and export in Logic Pro, REAPER or Ableton Live by talking to an AI engineer.
OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.
Manage 24/7 live streams, media, playback queues, schedules, and multistreaming from AI assistants.
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.