Ext Ops Panel
Open dashboard
Comparison

firebase-development vs io.github.firebase/firebase-mcp

firebase-development is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.firebase/firebase-mcp is an MCP server published by firebase. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-official). As of our marketplace pass on 2026-10-15. 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
Marketplacefirebase-developmentio.github.firebase/firebase-mcp
Claude Code: claude-plugins-community Listed
Version: dbb92f1
Forks (GitHub): 8
Stars (GitHub): 97
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 14 088 257
Downloads/week (npm): 3 454 538
Forks (GitHub): 1 267
Stars (GitHub): 4 472
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 268
Stars (GitHub): 37 981
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

firebase-development vs io.github.firebase/firebase-mcp
Factfirebase-developmentio.github.firebase/firebase-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)97 (worse)37 981 (better)
Forks (GitHub) (differs)8 (worse)4 268 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (firebase-tools)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published1
LicenceNot statedNot stated
Repository (differs)github.com/2389-research/claude-pluginsgithub.com/firebase/firebase-tools
Changes in the last 7 days (differs)10
First seen2026-10-112026-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

firebase-development

In its own words, on Claude Code: claude-plugins-community:

Firebase project workflows including setup, features, debugging, and validation

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

firebase-development As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install firebase-development@claude-community

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

Neither one's marketplaces publish the settings it asks for.

What it can do: firebase-development · What it can do: io.github.firebase/firebase-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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. 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