osc

This MCP server provides a comprehensive OSC-based interface for controlling Behringer and Midas digital mixers. It exposes a suite of 50+ tools that allow you to perform channel, bus, aux, matrix, effects, routing, scene management, and custom OSC command operations directly from Claude Desktop or any MCP-compatible client. The server communicates with the mixer over UDP using OSC (default port 10023) and keeps a bi-directional connection to fetch status and reflect changes in real time. To use it, configure the OSC connection details in Claude Desktop with the node-based MCP server entry, then issue natural-language commands or select specific tools to adjust levels, muting, EQ, dynamics, routing, scenes, and more. The available tools include precise controls such as osc_set_fader, osc_get_pan, osc_set_eq, osc_set_main_fader, osc_send_to_bus, osc_scene_recall, and osc_custom_command, among others, enabling both routine operations and advanced, custom OSC interactions with your mixer.

Prerequisites:

• Node.js 18 or higher
• A Behringer X32, Midas M32, or compatible mixer on the same network
• Claude Desktop app (for Claude-based control)

Setup steps:

1. Clone or download the repository and navigate to the project directory:

cd /path/to/osc-mcp

2. Install dependencies:

npm install

3. Build the project (produces dist/index.js):

npm run build

4. Run the server directly during development (example):

npm run dev

5. If you are integrating with Claude Desktop, configure Claude to point to your built index.js (see Claude configuration example in the README).

Tips and considerations:

• By default, the server communicates with the mixer using UDP on port 10023. Ensure your firewall allows UDP traffic to the mixer’s IP on that port.
• Environment variables OSC_HOST and OSC_PORT configure the target mixer address and port. Adjust them to your network setup if your mixer uses a different IP or port.
• The Claude Desktop section demonstrates how to embed the MCP server within Claude’s config, including providing OSC host/port values. Replace the example IP with your mixer’s actual address.
• The MCP exposes a broad toolset (channel, EQ, dynamics, bus/aux/matrix, scenes, status, and custom commands). Use osc_custom_command for raw OSC messages when needed, but prefer the higher-level tools for reliability.
• If you see latency or connection issues, verify network stability and that the mixer is reachable via UDP. The server uses a keep-alive approach (/xremote every ~9 seconds) to maintain the connection.