studio-one-mcp
Related Servers
Alternatives to studio-one-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceAn MCP server that lets Claude and other clients read Fender Studio Pro 8 song files and control the running app — transport, tracks, plug-ins, sends, mixer levels, markers, automation, macros and recording — without needing an IAC Driver. It also captures the app's audio output and analyses the mix for loudness, true peak, clipping, band energy, low-end mono, stereo width and correlation, optionally with a PNG and reference comparison.59MIT
- AlicenseNot gradedqualityCmaintenanceAn unofficial MCP server that lets an agent control Fender Studio Pro / PreSonus Studio One — transport playback, Mackie Control mixer moves, shortcut-driven track and session editing, plug-in listing and insert-macro generation, and DAW command discovery and dispatch from an exported key scheme. It also ships audio-to-MIDI workflows for drafting drums or a hummed melody from rehearsal recordings before arranging them in the DAW.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude or any MCP client to view and control a Cubase/Nuendo project in real time, including transport, tempo, locators, mixer, channel strip, inserts, plug-in parameters, and 1,454 commands. It also supports music generation and recording notes into tracks.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that turns PreSonus Studio One into an AI-controllable DAW, enabling production workflows like editing, MIDI manipulation, mixing, effects, and export through an LLM.12MIT
- FlicenseAqualityDmaintenanceAn MCP server that gives Claude Code (or any MCP client) full control of Reaper.531-
- FlicenseNot gradedqualityBmaintenanceEnables Claude and other MCP clients to control FL Studio over virtual MIDI, including transport, tempo, patterns, step sequencing, mixer and channel controls, and live note or chord playback, while reading some FL state back.-
TDQS
Scored across 27 tools
Most tools target clearly distinct resources (markers, channels, tracks, events, transport), and descriptions are detailed. However, the generic live_command overlaps with many specific wrappers (live_undo, live_transport, live_edit_events), and live_set_transport/live_set_loop/live_transport all manipulate transport state, creating some potential misselection.
All names are snake_case with predictable live_ and song_ domain prefixes, which makes grouping clear. Within live_, however, some tools are noun-only getters (live_song, live_channels, live_meters) while others follow verb_noun (live_add_marker, live_set_channel), so the convention is mostly but not perfectly uniform.
With 27 tools, the set is above the 15-tool sweet spot and crosses the 25-tool threshold that signals an overly heavy surface. Mergeable pairs like live_undo/live_redo, overlapping transport setters (live_transport, live_set_transport, live_set_loop), and a catch-all live_command inflate the count beyond what the domain strictly needs.
The surface covers live control (status, transport, markers, channels, tracks, events, takes, meters, save, undo/redo) plus offline song file inspection, giving solid lifecycle coverage. Gaps remain in track deletion/rename, plug-in parameter writing, and MIDI note editing, though live_command can bridge some of these.