{"id":"bonfire-audio-reaper-mcp","name":"reaper-mcp","homepage":null,"repo_url":"https://github.com/bonfire-audio/reaper-mcp","category":"ai-ml","subcategories":[],"tags":["mcp","reaper","daw-automation","audio","midi","mixing","mastering","python"],"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.","use_cases":["Automate REAPER project creation and editing from an AI agent","Generate MIDI items and drum patterns and place them into REAPER projects","Programmatically apply FX/mixing/mastering chains and render stems","Run audio analysis (loudness, dynamics, spectrum, stereo field, transients, clipping) on REAPER material"],"not_for":["Use as a hosted multi-tenant service (it appears designed for local REAPER control)","Security-sensitive automation where strong authentication/auditing is required across machines","Cloud deployment without a local REAPER instance accessible"],"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.","alternatives":["REAPER ReaScript (Lua/Python) directly","Other MCP servers/automation layers for DAWs (if available)","Direct python-reapy scripting without MCP","Custom MCP server that wraps REAPER ReaScript or ReaControlNet-style integrations"],"af_score":56.2,"security_score":20.8,"reliability_score":20.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:24:27.175137+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication mechanism is described for the MCP server. Access likely depends on local execution and the security posture of the REAPER distant API environment."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"MIT-licensed open source; pricing not applicable based on provided materials."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":56.2,"security_score":20.8,"reliability_score":20.0,"mcp_server_quality":78.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":10.0,"scope_granularity":0.0,"dependency_hygiene":55.0,"secret_handling":50.0,"security_notes":"Likely local-only interaction, but there is no documented auth/TLS layer for the MCP server itself. Enabling REAPER’s distant API increases the attack surface of the local machine/process; ensure only trusted local users/processes can reach the server. Dependencies include audio/analysis libraries (numpy/librosa/pyloudnorm/soundfile) which are common but still warrant vulnerability monitoring.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":20.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":"No idempotency guarantees are stated; many operations (create/import/render) are likely non-idempotent without caller safeguards.","pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}