Skip to main content
Glama
OSC MCP Server

OSC MCP Server

by darkwings

OSC MCP Server

MCP Server for controlling a Behringer X-Air XR18 digital mixer via Open Sound Control (OSC) protocol.

Features

  • 18 input channels with fader, mute, EQ (4 bands), and bus sends

  • 6 buses (monitor/aux) with fader and mute

  • Main LR output control

  • 4 FX slots with send level and mute

  • Symbolic naming — refer to channels and buses by name (e.g. "Kick", "Drummer") instead of numbers

  • dB-to-float conversion — work in dB, the server handles the XR18's non-linear fader scale

  • Persistent connection — the server remembers the last mixer IP across sessions

  • Raw OSC escape hatch for any unsupported command

Related MCP server: X32/M32 MCP Server

Prerequisites

  • Python >= 3.11

  • uv package manager

  • A Behringer XR18 (or other X-Air mixer) on your local network

Installation

git clone https://github.com/darkwings/OSC_MCP.git
cd OSC_MCP
uv sync

Running the Server

# Run via stdio (used by MCP clients)
uv run osc-mcp

# Or use the MCP inspector for interactive testing
uv run mcp dev src/osc_mcp/server.py

Adding to an MCP Client

Claude Desktop

The easiest way is to use the built-in install command:

uv run mcp install src/osc_mcp/server.py --name "OSC Mixer"

Alternatively, open Claude Desktop and go to Settings > Developer > Edit Config, then add:

{
  "mcpServers": {
    "osc-mcp": {
      "command": "uv",
      "args": ["run", "--directory", "/absolute/path/to/OSC_MCP", "osc-mcp"]
    }
  }
}

Restart Claude Desktop after saving.

Claude Code

claude mcp add osc-mcp -- uv run --directory /absolute/path/to/OSC_MCP osc-mcp

Or manually add to .mcp.json or ~/.claude/mcp.json:

{
  "mcpServers": {
    "osc-mcp": {
      "command": "uv",
      "args": ["run", "--directory", "/absolute/path/to/OSC_MCP", "osc-mcp"]
    }
  }
}

Cursor

Go to Settings > MCP Servers > Add Server and use:

  • Type: stdio

  • Command: uv run --directory /absolute/path/to/OSC_MCP osc-mcp

Generic MCP Client

Any MCP-compatible client can connect using the stdio transport:

uv run --directory /absolute/path/to/OSC_MCP osc-mcp

Replace /absolute/path/to/OSC_MCP with the actual path where you cloned the repository.

Usage

Once the server is running in your MCP client:

  1. Connect: connect_mixer("192.168.1.1") — the IP is saved for future sessions

  2. Name your channels: assign_channel_name(1, "Kick"), assign_bus_name(2, "Drummer")

  3. Control: set_channel_fader("Kick", -5), set_channel_send_to_bus("Kick", "Drummer", -10)

On subsequent sessions, the server automatically reconnects to the last known mixer IP. If the mixer is unreachable (e.g. different network), the agent is prompted to ask for the new IP.

Available Tools

Tool

Description

connect_mixer

Connect to mixer at IP:port

assign_channel_name

Name a channel (1-18)

assign_bus_name

Name a bus (1-6)

list_names

Show all name assignments

set_channel_fader

Set channel level in dB

set_channel_mute

Mute/unmute a channel

get_channel_fader

Query current channel level

set_bus_fader

Set bus level in dB

set_bus_mute

Mute/unmute a bus

set_channel_send_to_bus

Set channel→bus send level

get_channel_send_to_bus

Query channel→bus send level

set_main_fader

Set main LR level

set_main_mute

Mute/unmute main LR

set_channel_eq

Set EQ band parameters

set_channel_eq_on

Enable/disable channel EQ

set_fx_send_fader

Set FX send level

set_fx_send_mute

Mute/unmute FX send

get_mixer_info

Query mixer info

send_raw_osc

Send any raw OSC message

Running Tests

uv run pytest

License

Apache License 2.0

Available Tools

19 tools
assign_bus_nameA

Give a bus (1-6) a symbolic name, e.g. bus 2 = 'Drummer'.

Inputs: bus (required), name (required). Returns: result

assign_channel_nameB

Give a channel (1-18) a symbolic name, e.g. channel 1 = 'Kick'.

Inputs: name (required), channel (required). Returns: result

connect_mixerB

Connect to the XR18 mixer at the given IP and port (default 10024).

Inputs: ip (required), port. Returns: result

get_channel_faderC

Query the current fader level of an input channel.

Inputs: channel (required). Returns: result

get_channel_send_to_busB

Query the current send level from a channel to a bus.

Inputs: bus (required), channel (required). Returns: result

get_mixer_infoB

Query mixer info via /xinfo.

Inputs: no named parameters. Returns: result

list_namesA

Show all current channel and bus name assignments.

Inputs: no named parameters. Returns: object

send_raw_oscC

Send a raw OSC message. Escape hatch for any OSC command.

Inputs: address (required), args. Returns: result

set_bus_faderB

Set a bus master fader level in dB. Bus can be a number (1-6) or name.

Inputs: bus (required), level_db (required). Returns: result

set_bus_muteA

Mute or unmute a bus. Bus can be a number (1-6) or name.

Inputs: bus (required), muted (required). Returns: result

set_channel_eqB

Set EQ parameters for a channel band (1-4).

Inputs: q (required), band (required), channel (required), gain_db (required), +1 more. Returns: result

set_channel_eq_onB

Enable or disable EQ on a channel.

Inputs: channel (required), enabled (required). Returns: result

set_channel_faderB

Set an input channel's fader level in dB. Channel can be a number (1-18) or name.

Inputs: channel (required), level_db (required). Returns: result

set_channel_muteA

Mute or unmute an input channel. Channel can be a number (1-18) or name.

Inputs: muted (required), channel (required). Returns: result

set_channel_send_to_busC

Set how much of a channel goes to a specific bus/monitor in dB.

Inputs: bus (required), channel (required), level_db (required). Returns: result

set_fx_send_faderB

Set an FX send fader level in dB (slot 1-4).

Inputs: fx_slot (required), level_db (required). Returns: result

set_fx_send_muteA

Mute or unmute an FX send (slot 1-4).

Inputs: muted (required), fx_slot (required). Returns: result

set_main_faderB

Set the main LR output fader level in dB.

Inputs: level_db (required). Returns: result

set_main_muteB

Mute or unmute the main LR output.

Inputs: muted (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct operation (e.g., fader, mute, EQ, send) on a specific resource (channel, bus, main, FX). Even similar tools like set_channel_fader and set_channel_mute are clearly differentiated by their purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., assign_channel_name, set_channel_fader, get_channel_send_to_bus). There is no mixing of conventions or ambiguous verbs.

    Tool Count5/5

    With 19 tools covering channel, bus, main, FX, naming, info, and a raw OSC escape, the count is well-scoped for a mixer control server. It includes all essential operations without being bloated.

    Completeness4/5

    The tool set covers core mixer operations (fader, mute, EQ, sends, main). Missing features like compressor or gate are offset by the send_raw_osc escape hatch, preventing dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers