Ext Ops Panel
Open dashboard
Comparison

MAGNEMO vs io.github.firebase/firebase-mcp

MAGNEMO is an MCP server published by magnemo.ai. Marketplaces we read that list it: 1 (Official MCP Registry). 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-08. 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
MarketplaceMAGNEMOio.github.firebase/firebase-mcp
Official MCP Registry Listed
Version: 0.6.11
Downloads/month (PyPI): 733
Downloads/week (PyPI): 303
Forks (GitHub): 2
Stars (GitHub): 4
Not marked · First seen
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

MAGNEMO vs io.github.firebase/firebase-mcp
FactMAGNEMOio.github.firebase/firebase-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)4 (worse)46 418 (better)
Forks (GitHub) (differs)2 (worse)4 835 (better)
Last release (differs)2026-10-29Not published
Where it runs (differs)On your machine (magnemo-mcp)On your machine (firebase-tools)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 01, secrets among them: 0
Parts of the bundle (differs)Not a bundle16
Licence (differs)Not statedMIT
Repository (differs)github.com/magnemo-ai/magnemogithub.com/firebase/firebase-tools
Changes in the last 7 days (differs)01
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

MAGNEMO

In its own words, on Official MCP Registry:

Persistent Memory for AI Agents, in plain local files. No network calls of its own.

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

MAGNEMO As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MAGNEMO_VAULT=<YOUR_MAGNEMO_VAULT>" --transport stdio magnemo -- uvx magnemo-mcp

Requires: MAGNEMO_VAULT

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

Only MAGNEMO asks for

  • MAGNEMO_AGENT
  • MAGNEMO_VAULT

Only io.github.firebase/firebase-mcp asks for

  • IS_FIREBASE_MCP

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

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

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