F
licenseA
qualityC
maintenanceEnables AI assistants to control a live REAPER DAW session on macOS in real time, including track creation, MIDI writing, FX management, and transport control.
20
-
ReaperMCP
by xDarkzx
Related Servers
Alternatives to ReaperMCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceEnables AI assistants to control REAPER DAW via the Model Context Protocol, including track, FX, MIDI, and audio operations.4784MIT
- 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.17768MIT
- FlicenseBqualityDmaintenanceEnables AI-powered music composition and control for REAPER DAW through OSC and ReaScript integration. Supports transport control, MIDI generation, track management, and music theory operations like scales, chords, and rhythm patterns.17-
- FlicenseNot gradedqualityDmaintenanceEnables AI-powered music production by integrating with REAPER DAW via MCP protocol, allowing users to control project settings, MIDI editing, and VST plugins through natural language.10-
- AlicenseNot gradedqualityDmaintenanceReal-time AI-assisted music production, advanced composition, mixing, and VST coordination for FL Studio via bidirectional MIDI & WebSockets, exposing over 100 tools for comprehensive DAW control.9MIT
TDQS
B3.4/5.0
Scored across 174 tools
Disambiguation4/5
Most tools have clearly distinct purposes (track_*, item_*, midi_*, fx_*, send_*, etc.), but there are some overlapping patterns like track_set_volume vs configure_tracks and item_set_* vs items_apply, though descriptions note the batch preferences. A few niche chop tools (arrange_chops_to_chord_tones vs chop_pipeline) have explicit warnings about their distinct uses, so ambiguity is limited.
Naming Consistency3/5
The majority follow a consistent verb_noun pattern (track_set_*, item_set_*, send_set_*), but there are notable deviations like setup_fx_chain, configure_tracks, items_apply, add_markers_batch, create_drum_pattern, and compose_arrangement. This mixed style makes the tool naming less predictable, especially with both singular and batch variants coexisting.
Tool Count2/5
174 tools is far beyond the typical well-scoped range and falls into the extreme mismatch category. Even for a full DAW control server, this is an enormous surface that would overwhelm an agent with context and decision overload. The count is not appropriate for a coherent toolset.
Completeness5/5
The tool set covers nearly every aspect of DAW operation: transport, tracks, items, takes, MIDI, FX, sends, envelopes, markers, tempo, project management, scripts, audio scanning, and several mix/master pipelines. There are no obvious dead ends, and the presence of batch tools, undo/redo, and backup mechanisms makes the domain coverage exceptionally complete.
Maintenance
ActivityActive
ResponsivenessResponsive