DeadCat: Reaper

io.github.systemblueioPublished by GitHub account systemblueiov0.1.5Updated Oct 24, 2026

Operate a REAPER session in plain language, with writes verified against REAPER feedback.

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

Lets an assistant control a REAPER digital audio workstation session in plain language, with writes verified against REAPER feedback.

What you can do
This server connects an assistant to a running REAPER session so it can carry out digital audio workstation operations from natural-language instructions. According to the registry description, it operates the session in plain language and verifies write actions against feedback returned by REAPER. The manifest does not list individual tools, so the exact command set is not documented here.
When to use it
Worth adding when you work in REAPER and want an assistant to drive session actions for you rather than clicking through the interface yourself. It is a desktop-only local server, so it suits a workstation setup rather than a headless or web environment.
Requirements
Runs as a local process on the user's machine over stdio, distributed as an mcpb package. Desktop only; no web executable. No authentication, environment variables, or headers are declared, but a REAPER installation must be present and running for the server to operate a session.
Before you install
The server performs write operations in a REAPER session, which can change or overwrite project content; the description says writes are verified against REAPER feedback, but you should still keep backups of important projects. No credentials, payments, or third-party data sharing are declared.

Installation

In SourceWeft

  1. Open DeadCat: Reaper in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.