REAPER
REAPER MCP Server provides a bridge between AI agents and the REAPER digital audio workstation, enabling comprehensive control for music production tasks. It offers two communication methods: a ReaScript-based implementation using python-reapy and an OSC-based implementation for more reliable communication. The server includes tools for project management, track operations, MIDI composition, audio recording, VST plugin control, mixing, mastering, and rendering. Built with a modular architecture, it handles both simple commands like creating tracks and complex operations like applying mastering chains or creating drum patterns, making it ideal for AI-assisted music production without navigating REAPER's interface directly.
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-02.
Scan details: Circle-IR · 2026-09-02 · 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/bonfire-audio/reaper-mcp
- Author type
- human
- Last scanned
- 2026-09-02
- Updated
- 2026-09-02
Use via MCP
Resolve REAPER 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.