{"id":"bonfire-audio-reaper-mcp","name":"reaper-mcp","af_score":56.2,"security_score":20.8,"reliability_score":20.0,"what_it_does":"reaper-mcp-server is a local Model Context Protocol (MCP) server that exposes REAPER DAW functionality (project management, track/MIDI/Fx/audio operations, mixing/mastering, rendering, and audio analysis) to AI agents, using python-reapy with REAPER’s distant API enabled.","best_when":"You have REAPER installed locally, can enable REAPER’s distant API, and want an agent to drive REAPER via MCP tools rather than manual DAW scripting.","avoid_when":"You cannot enable REAPER’s distant API or you need network-exposed access with strong auth/TLS; the interface appears intended for local use rather than remote sharing.","last_evaluated":"2026-03-30T15:24:27.175137+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["Many tool actions modify DAW state (create/delete/insert FX/items). Agents should confirm intent and avoid repeated calls without checking current project state.","REAPER’s distant API must be enabled (and likely only works when REAPER is open/running).","Audio rendering/recording can be time-consuming and may require sequencing and waiting for completion.","Parameter naming/types are not shown in the README; tool schemas may be necessary to ensure correct arguments."],"error_quality":0.0}