Skip to main content
Glama
yiw190

reaper-mcp

by yiw190
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to reaper-mcp

No user-submitted related servers found.

    Related Servers

    • reaper-mcp

      vecnode
      A
      license
      B
      quality
      D
      maintenance
      This 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.
      40
      MIT

    • REAPER MCP

      juliaexterkoetter
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local control of REAPER projects from MCP clients like Codex, including track, item, transport, FX, marker, automation, and render operations through a native Windows extension and authenticated bridge.
      1
      MIT

    • reaper-mcp-bridge

      Echo722
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      50
      1
      MIT

    • ReaMCP

      danielkinahan
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables users to control and edit REAPER projects through a Python-based interface and a Lua bridge. It supports managing tracks, controlling transport, manipulating MIDI and audio items, and adjusting FX parameters within the digital audio workstation.
      57
      GPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation3/5

    Resource tools (track, item, midi, fx, envelope, send, project, transport, render) are mostly distinct, but four generic escape hatches—action, reaper_call, run_lua, and batch—all execute arbitrary commands and could easily be misselected. The descriptions offer guidance on when to use each, but the boundaries between 'run a Main_OnCommand', 'call a ReaScript function', 'run a Lua snippet', and 'batch these together' remain fuzzy.

    Naming Consistency4/5

    All names are lowercase snake_case and predominantly resource-oriented nouns, which makes the set readable and predictable. Minor deviations: a few generic names (action, status, batch) and a couple of verb forms (render, run_lua) break the pure noun convention.

    Tool Count4/5

    14 tools is within a reasonable scope for a DAW control server covering tracks, items, MIDI, FX, envelopes, sends, rendering, and project settings. The count is slightly inflated by redundant abstraction layers (action/reaper_call/run_lua/batch) that could arguably be consolidated.

    Completeness4/5

    Coverage is broad: arrangement state, transport, MIDI, FX, items, envelopes, sends, routing buses, project tempo/markers, rendering, and raw escape hatches. Minor gaps remain—no explicit undo/redo control, limited take management beyond active_take, and marker/region lifecycle is only partially exposed (creation via project, deletion unclear).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources