Skip to main content
Glama
yiw190

reaper-mcp

by yiw190
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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

    • 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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Tools are mostly distinct, but reaper_call and run_lua both offer arbitrary scripting access, and action overlaps with reaper_call for command execution. Descriptions help, but an agent could misselect between these scripting tools.

    Naming Consistency5/5

    All tool names follow a consistent style: lowercase, single words or underscore-separated compounds (reaper_call, run_lua). No mixed conventions or unpredictable verbs.

    Tool Count5/5

    14 tools is well-scoped for a DAW control server, covering core operations (status, transport, track, midi, fx, send, render) and advanced scripting without overwhelming.

    Completeness5/5

    The set provides comprehensive coverage of project lifecycle and editing, with scripting tools (reaper_call, run_lua, batch) filling any gaps. Missing specific audio editing but scriptable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources