Reaper Daemon
Related Servers
Alternatives to Reaper Daemon
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceThis MCP server enables AI assistants to control a live REAPER DAW instance, including transport, tracks, FX, MIDI, media, markers, rendering, and project state, with an escape hatch for arbitrary ReaScript commands.40MIT
- AlicenseCqualityAmaintenanceA comprehensive MCP server that enables AI assistants to control REAPER DAW for mixing, mastering, MIDI composition, and full music production workflows with 130 tools.1872,076 PyPI104MIT
- AlicenseBqualityCmaintenanceEnables MCP-capable AI agents to control REAPER through typed tools and a Lua escape hatch for project creation, track management, recording and editing, MIDI writing, mixing, rendering, and batch operations.501MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets language models interact with the Reaper DAW1MIT
- FlicenseAqualityDmaintenanceMCP server for controlling REAPER digital audio workstation from natural language. It enables AI agents to create tracks, import audio, adjust mix parameters, and manage sessions through typed operations and a REAPER bridge.22-
- AlicenseNot gradedqualityCmaintenanceThis MCP server lets an AI assistant inspect and safely modify a whole Live set—tracks, groups, returns, master, routing, automation, clips, devices, dBFS meters, snapshots, and undo—while leaving listening to the producer.MIT
TDQS
Scored across 49 tools
The descriptions are unusually explicit and cross-reference each other (e.g. insert_midi_events vs insert_midi_file vs insert_groove vs insert_riff), which rescues a lot. But with 49 tools there are still real boundary clusters: five audio-measurement tools (capture_track_audio, analyze_track, compare_tracks, verify_change, tune_param), four drum/MIDI-generation paths (riff_grid, profile_track, insert_groove, drum_workshop, transcribe_drums/insert_drum_transcription), and three automation writers (write_automation, apply_automation_transaction, batch) that an agent must reason carefully to pick between.
Everything is snake_case, so casing is consistent, but the verb convention is not: many tools are verb_noun (get_status, set_fx_param, insert_groove, capture_track_audio) while others are bare domain nouns that dispatch on an action argument (track, transport, markers, fx, batch, instruments, song_plan). Readable, but an agent cannot infer from a name alone whether the operation is a noun-with-action or a fixed verb.
49 tools is well past the 25-tool threshold and the surface includes long-tail capabilities (verify_change, tune_param, complete_postmortem_onboarding, insert_performance_audition, drum_workshop) that most sessions will never touch. Each is individually defensible for a full DAW bridge, but the set as a whole is heavy enough that selection accuracy and prompt budget suffer.
Coverage of the DAW domain is broad: transport/tempo map, tracks and routing, FX chain and parameters, automation, MIDI generation across several engines, markers/regions, save/templates, actions/scripts, and measured audio analysis. Gaps are real but mostly second-order — there is no media-item listing/inspection or item editing (split, trim, move, fades), no master-volume/mix write tool, and no undo/redo management, all of which some workflows will hit as dead ends.