Image, video and audio · MCP server
Reaper MCP (xDarkzx): MCP server, setup and security
Reaper MCP (xDarkzx) is an open-source MCP server published on GitHub that lets an AI agent control REAPER edit MIDI mix tracks and execute ReaScript scripts. Its repository has 107 stars and its last commit is from October 23, 2026 and it is licensed under Apache-2.0.
What Reaper MCP (xDarkzx) does
According to its repository: “Music production in REAPER: transport, tracks, MIDI editing, mixing and FX, tempo maps, markers and regions, and ReaScript execution.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Reaper MCP (xDarkzx) is listed under Image, video and audio, a category of 67 servers in the directory, where it ranks #26 by stars.
Topics declared by the repository: reaper, claude, daw, python, audio-editing, ai-tools.
Installing and connecting Reaper MCP (xDarkzx)
No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Python. Listed systems: macOS, Windows, Linux.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Reaper MCP (xDarkzx). That does not replace reading the code.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on April 16, 2026, the xDarkzx/Reaper-MCP repository has 107 stars and 13 forks, with 0 open issues. It has more stars than 68% of the servers in the directory. It received changes this month.
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Reaper MCP (xDarkzx) is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Permissive licence (Apache-2.0)
Limitations
- Install from source
Alternatives
- OpenScreen4.9K ★
- Remove AI Watermarks6.1K ★
- FunASR20.8K ★
- Oh My Cassette117 ★
- FableCut746 ★
- WeftCut261 ★
Learn more
Frequently asked questions
How do I install Reaper MCP (xDarkzx)?
No package is declared in the MCP registry: clone the xDarkzx/Reaper-MCP repository, follow its README, then declare the start command in your client's MCP configuration.
Is Reaper MCP (xDarkzx) free?
The code is published under the Apache-2.0 licence and can be used free of charge.
Is Reaper MCP (xDarkzx) safe?
No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.
Is it an official server?
Nothing says so: it is a project published by xDarkzx on GitHub. Check who maintains it before giving it access.
What are the alternatives to Reaper MCP (xDarkzx)?
In the same category: OpenScreen, Remove AI Watermarks, FunASR, and Oh My Cassette. OpenScreen and Remove AI Watermarks score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score