A
licenseA
qualityD
maintenanceEnables control of Behringer X32/M32 digital mixing consoles via OSC protocol for remote mixing, automated setup, and live adjustments through an AI assistant.
24
41 npm
MIT
XR18 MCP Server
by gdeber
Related Servers
Alternatives to XR18 MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables 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.5211-
- 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
- AlicenseAqualityDmaintenanceMCP server for controlling Behringer X-Air digital mixers via OSC, with symbolic naming and dB-to-float conversion.191Apache 2.0
- AlicenseAqualityCmaintenanceEnables controlling Behringer WING digital mixers via OSC, supporting fader, mute, pan, and name operations on strips, with raw OSC access for unsupported parameters.116MIT
- AlicenseBqualityDmaintenanceEnables LLMs to control Ableton Live digital audio workstation through OSC (Open Sound Control) protocol. Provides comprehensive tools for managing tracks, routing, and DAW configuration through natural language commands.1394MIT
TDQS
B3.1/5.0
Scored across 25 tools
Disambiguation4/5
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 Consistency3/5
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.
Tool Count4/5
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.
Completeness4/5
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
ActivityMaintained
ResponsivenessNo issues