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
OSC MCP Server
Related Servers
Alternatives to OSC MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language control over Ableton Live for generating musical patterns, melodies, and full song arrangements. It also provides tools for sample searching and mixing assistance through an OSC-based connection with Claude Desktop.1MIT
- 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.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
- FlicenseNot gradedqualityCmaintenanceEnables natural language control of Ableton Live through Claude, including session management, track and clip creation, device parameter adjustment, and browser browsing.1-
TDQS
B3.2/5.0
Scored across 52 tools
Disambiguation4/5
Most tools have distinct purposes targeting specific mixer components (e.g., channels, buses, effects) with clear action distinctions (get vs. set). However, some overlap exists, like multiple EQ-related tools (osc_set_eq, osc_set_eq_frequency, osc_set_eq_q) that could be confusing without careful reading of descriptions, and the compressor/gate tools follow similar patterns that might cause minor confusion.
Naming Consistency5/5
All tools follow a highly consistent naming pattern: 'osc_' prefix, then a verb (e.g., get, set, mute, send), and a noun phrase describing the target (e.g., channel_name, aux_fader, emulator_status). This verb_noun structure is maintained throughout all 52 tools, making them predictable and easy to parse.
Tool Count2/5
With 52 tools, the count is excessive for an MCP server, likely overwhelming for agents and leading to decision paralysis. While the domain (OSC mixer control) is complex, this many tools suggests over-fragmentation (e.g., separate tools for each EQ parameter) rather than a well-scoped set, making it borderline heavy and inefficient for typical use.
Completeness5/5
The tool set provides comprehensive coverage for controlling an X32 mixer via OSC, including full CRUD-like operations (get/set for levels, names, statuses), scene management, emulator control, and detailed effect/processor adjustments (EQ, compressor, gate). No obvious gaps are present; agents can perform all expected mixer interactions without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues