Reaper
This Reaper MCP server, developed for integration with Claude Desktop, provides a bridge between AI assistants and Reaper digital audio workstation projects. Built with Python and leveraging the MCP protocol, it offers tools for finding and parsing Reaper project files. The implementation focuses on extracting structured data from complex audio projects, making it accessible for AI models to analyze track layouts, plugin chains, automation, and other project elements. It's particularly useful for tasks like audio production assistance, project organization, or integrating music production workflows into AI-driven systems, enabling assistants to interact with Reaper projects without requiring deep knowledge of the underlying file format.
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-28.
Scan details: Circle-IR · 2026-09-28 · 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/dschuler36/reaper-mcp-server
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
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.