Plugged.in Proxy vs reaper-mcp-server
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). reaper-mcp-server is an MCP server published by bonfire-systems. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |  Plugged.in Proxy |  reaper-mcp-server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 29 Pulls (Docker Hub): 36 659 Stars (Docker Hub): 3 Stars (GitHub): 139 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Not listed | Listed Version: 0.4.0 Downloads/month (PyPI): 6 243 Downloads/week (PyPI): 426 Forks (GitHub): 38 Stars (GitHub): 183 Not marked · First seen |
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 | Plugged.in Proxy | reaper-mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 139 (worse) | 183 (better) |
| Pulls (Docker Hub) (differs) | 36 659 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 29 (worse) | 38 (better) |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | On your machine (reaper-mcp-server) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/bonfire-systems/reaper-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
reaper-mcp-server
MCP server for controlling REAPER DAW with AI agents
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
reaper-mcp-server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of reaper-mcp-server publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of reaper-mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: Plugged.in Proxy · What it can do: reaper-mcp-server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.