REAPER MCP vs BeatSeek
REAPER MCP is an MCP server published by twelvetake.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). BeatSeek is an MCP server published by levz0r. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  REAPER MCP | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.11.0 Downloads/month (PyPI): 2 685 Downloads/week (PyPI): 2 609 Forks (GitHub): 19 Stars (GitHub): 104 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.11.0 Downloads/month (PyPI): 2 685 Downloads/week (PyPI): 2 609 Forks (GitHub): 19 Stars (GitHub): 104 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | REAPER MCP | BeatSeek |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 104 | No figure on GitHub |
| Forks (GitHub) (differs) | 19 | No figure on GitHub |
| Last release (differs) | 2026-11-10 | Not published |
| Where it runs (differs) | On your machine (twelvetake-reaper-mcp) | Remote server (beatseek.io/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/twelvetake-studios/reaper-mcp | Not stated |
| Changes in the last 7 days (differs) | 5 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-07 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
REAPER MCP
Enables AI assistants to control REAPER for mixing, mastering, MIDI and music production.
BeatSeek
SoundCloud search for DJs and AI agents, with BPM and key measured from the audio.
How to run each
REAPER MCP As a local MCP server: PyPI package
claude mcp add --transport stdio reaper-mcp -- uvx twelvetake-reaper-mcpBeatSeek As a remote MCP server
claude mcp add --transport http beatseek https://beatseek.io/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only BeatSeek has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: REAPER MCP · What it can do: BeatSeek · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.