Ext Ops Panel
Open dashboard
Comparison

reaper-mcp-server vs io.github.firebase/firebase-mcp

reaper-mcp-server is an MCP server published by bonfire-systems. Marketplaces we read that list it: 1 (PyPI (MCP servers)). io.github.firebase/firebase-mcp is an MCP server published by firebase. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-official, Community GitHub marketplaces). 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

Where each is published
Marketplacereaper-mcp-serverio.github.firebase/firebase-mcp
PyPI (MCP servers) Listed
Version: 0.4.0
Downloads/month (PyPI): 6 243
Downloads/week (PyPI): 426
Forks (GitHub): 38
Stars (GitHub): 183
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 13 149 020
Downloads/week (npm): 4 514 786
Forks (GitHub): 1 281
Stars (GitHub): 4 488
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 835
Stars (GitHub): 46 418
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

reaper-mcp-server vs io.github.firebase/firebase-mcp
Factreaper-mcp-serverio.github.firebase/firebase-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)183 (worse)46 418 (better)
Forks (GitHub) (differs)38 (worse)4 835 (better)
Last release (differs)2026-10-26Not published
Where it runs (differs)On your machine (reaper-mcp-server)On your machine (firebase-tools)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)Not a bundle16
LicenceMITMIT
Repository (differs)github.com/bonfire-systems/reaper-mcpgithub.com/firebase/firebase-tools
Changes in the last 7 days (differs)01
First seen (differs)2026-10-132026-10-11

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-server

In its own words, on PyPI (MCP servers):

MCP server for controlling REAPER DAW with AI agents

io.github.firebase/firebase-mcp

In its own words, on Official MCP Registry:

Gives AI development tools Firebase-specific capabilities and expertise.

How to run each

reaper-mcp-server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.firebase/firebase-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio firebase-mcp -- npx -y mcp firebase-tools

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

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: reaper-mcp-server · What it can do: io.github.firebase/firebase-mcp · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built