A
licenseC
qualityA
maintenanceA comprehensive MCP server that enables AI assistants to control REAPER DAW for mixing, mastering, MIDI composition, and full music production workflows with 130 tools.
180
2,711 PyPI
86
MIT
reaper-mcp
by vecnode
Related Servers
Alternatives to reaper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets language models interact with the Reaper DAW1MIT
- FlicenseAqualityBmaintenanceMCP 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-
- 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.50MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to control REAPER DAW via the Model Context Protocol, including track, FX, MIDI, and audio operations.4729 PyPI87MIT
- AlicenseBqualityAmaintenanceA Model Context Protocol server that enables AI agents to create fully mixed and mastered tracks in REAPER DAW, supporting project management, MIDI composition, audio recording, and mixing automation.58161MIT
TDQS
B3.3/5.0
Scored across 40 tools
Disambiguation5/5
Each tool targets a distinct action on a specific resource (e.g., transport_play vs transport_pause, fx_add vs fx_list). Even the two info tools (reaper_info, reaper_status) serve different diagnostic purposes. No ambiguity or overlap exists.
Naming Consistency5/5
All tools follow a consistent verb_noun or domain_verb_noun pattern with underscores (e.g., track_add, fx_set_param, transport_stop). The only outlier is install_bridge, but it still follows the verb_noun convention. No mixing of styles.
Tool Count2/5
With 40 tools, this server is well beyond the typical 3-15 range for a well-scoped server. While REAPER is a complex DAW, the granularity could be reduced (e.g., combining transport tools into a single tool with actions). The high count makes it heavy for an MCP server.
Completeness3/5
Core operations for tracks, FX, transport, and items are covered, but notable gaps exist (e.g., deleting markers/regions, editing MIDI notes beyond adding, managing sends/receives). The run_reascript tool partially mitigates this by allowing arbitrary code, but the dedicated tool surface is incomplete.
Maintenance
ActivityInactive
ResponsivenessNo issues