uad-console-mcp
Related Servers
Alternatives to uad-console-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceControl Logic Pro locally on macOS through MCP: transport, tracks, mixer, plug-in parameters, audio analysis, bounce and delivery, with optional gesture and voice control. Uses OSC, CoreMIDI and macOS Accessibility. Actions report confirmed, uncertain or failed outcomes. Actual control requires a local Mac with Logic Pro. Hosted/Linux builds are schema inspection only; all operations are disabled.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP agents to inspect and precisely edit a running Ardour session — tracks, buses, groups, mixer, transport, regions, internal MIDI, plugins, routing and automation — through the DAW's Lua APIs with optional native OSC, plus offline audio analysis and comparison of master exports. Edits are exposed as 80 typed tools with persistent IDs, explicit units, preflight validation and structured change/error results.GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables local inspection of Apple MainStage state and patch/set information, plus MIDI control such as program changes, CC, and metronome toggle via MCP.MIT
- AlicenseNot gradedqualityAmaintenanceConnects 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
- AlicenseAqualityDmaintenanceEnables control of Behringer X32/M32 digital mixing consoles via OSC protocol for remote mixing, automated setup, and live adjustments through an AI assistant.2437 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Code to operate Logic Pro — transport, track selection/mute/solo/arm, mixer volume and pan, 8-band Channel EQ, and insert plugin slots — by emulating a Mackie Control surface over a CoreMIDI virtual port. Every command is verified against the LED, fader, and LCD feedback Logic sends back, so results report whether each action actually took effect.MIT
TDQS
Scored across 21 tools
Every tool targets a distinct resource and action, and the 'Not for' sections explicitly disambiguate overlapping areas (e.g., uad_peek_meters vs uad_watch_meters, uad_get_plugin_params vs uad_set_plugin_params). No two tools appear to do the same thing; even closely related tools like uad_load_plugin and uad_plugin_preset have clear separation (loading vs preset recall).
All tools share the uad_ prefix and most follow a verb_noun pattern (uad_list_channels, uad_set_preamp, uad_load_plugin). However, a few deviate: uad_raw_get is noun_verb instead of verb_noun, and uad_talkback, uad_safe_state, uad_plugin_preset, and uad_snapshot are single nouns or adjective_noun without an explicit verb. The deviations are minor and do not significantly hurt readability.
With 21 tools, the server sits at the upper edge of the well-scoped range but is justified by the complexity of controlling a professional audio console. Each tool covers a meaningful aspect (status, channels, preamps, sends, monitor, safety, clock, plugins, meters, snapshots), and there is no redundancy. It feels slightly heavy but not overwhelming for the domain.
The tool surface covers core console operations comprehensively: channel control, preamp, sends, monitor, talkback, safety, clock, sample rate, plugin management, parameter adjustment, and metering. Obvious gaps like headphone output level and console session management are explicitly acknowledged as limitations, and the snapshot system compensates for state management. Minor missing operations (e.g., explicit routing beyond sends) are workarounds.