A
licenseNot graded
qualityB
maintenanceAn 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.
5
MIT
studio-one-mcp
Related Servers
Alternatives to studio-one-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceAn MCP server that gives Claude Code (or any MCP client) full control of Reaper.53-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects Claude to FL Studio, enabling natural language control of transport, mixer, channel rack, and piano roll operations.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude to control Ableton Live in real-time via the AbletonOSC bridge. It allows users to manage playback, create tracks, write MIDI, and adjust mixer or device parameters using natural language commands.-
- AlicenseAqualityBmaintenanceMCP server that connects Ableton Live to Claude, enabling prompt-assisted music production with full mixer control including volume, panning, and sends.20MIT
- FlicenseAqualityBmaintenanceAn MCP server that gives Claude Code hands inside DaVinci Resolve Studio, enabling project management, status checks, snapshots, and arbitrary Python scripting via the Resolve API.51-
TDQS
B3.4/5.0
Scored across 27 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count2/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues