Skip to main content
Glama
yiw190

reaper-mcp

by yiw190
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

reaper-mcp

ci

MCP server for REAPER.

MCP client  --stdio JSON-RPC-->  python/server.py  --JSON mailbox-->  lua/bridge.lua (inside REAPER)

Eleven grouped tools. Multi-step edits go through batch; anything else through reaper_call / run_lua.

Setup

git clone https://github.com/yiw190/reaper-mcp.git
cd reaper-mcp
python3 python/install_bridge.py

Then in REAPER: Actions → Load ReaScript → reaper_mcp_bridge.lua → Run. Console: reaper-mcp bridge 0.1.0 ready.

MCP client config (Claude Code / Claude Desktop / Cursor):

{
  "mcpServers": {
    "reaper": {
      "command": "python3",
      "args": ["/absolute/path/to/reaper-mcp/python/server.py"]
    }
  }
}

Use native Windows Python, not WSL.

REAPER_MCP_IPC_DIR     mailbox override (must match on both sides)
REAPER_MCP_TIMEOUT     default 10s
REAPER_MCP_DEBUG=1     Lua request log

Mailbox is %APPDATA%/reaper-mcp/ipc (ASCII path both sides derive). Time is beats. Indices are 0-based.

Related MCP server: reaper-reapy-mcp

Tools

status transport track midi fx project render action reaper_call run_lua batch

Tests

python3 python/test_server.py

Fake bridge, no REAPER.

License

MIT

This server cannot be deployed

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

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • 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