REAPER DAW
This MCP server provides AI assistants with complete control over REAPER DAW through a comprehensive bridge architecture that translates MCP calls into ReaScript API commands via a Lua bridge script running inside REAPER. Built using Python with file-based communication for reliability, the implementation offers 62+ API methods covering track management, MIDI operations, FX processing, automation, project settings, and transport controls, enabling programmatic music production workflows. The server supports both socket and file-based communication modes with extensive test coverage, serving AI music composition applications, automated mixing and mastering workflows, and developers building intelligent DAW automation tools that require deep integration with REAPER's professional audio capabilities.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.
Scan details: Circle-IR · 2026-09-19 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- media
- Source
- PulseMCP
- Repository
- github.com/shiehn/total-reaper-mcp
- Author type
- human
- Last scanned
- 2026-09-19
- Updated
- 2026-09-19
Use via MCP
Resolve REAPER DAW from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.