io.github.firebase/firebase-mcp vs Impri
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). Impri is an MCP server published by sekera-radim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  io.github.firebase/firebase-mcp |  Impri |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Downloads/month (npm): 14 088 257 Downloads/week (npm): 3 454 538 Forks (GitHub): 1 267 Stars (GitHub): 4 475 Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (npm): 493 Downloads/week (npm): 384 Forks (GitHub): 1 Stars (GitHub): 6 Not marked · First seen |
| Claude Code: claude-plugins-official | Listed Version: not stated Forks (GitHub): 4 462 Stars (GitHub): 41 694 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 | io.github.firebase/firebase-mcp | Impri |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 41 694 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 4 462 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (firebase-tools) | Remote server (api.impri.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 15 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/firebase/firebase-tools | github.com/sekera-radim/impri |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 14 h ago |
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
io.github.firebase/firebase-mcp
Gives AI development tools Firebase-specific capabilities and expertise.
Impri
Impri MCP server — human-in-the-loop approval inbox for AI agents
How to run each
io.github.firebase/firebase-mcp As a local MCP server: npm package
claude mcp add --transport stdio firebase-mcp -- npx -y mcp firebase-toolsImpri As a remote MCP server
claude mcp add --transport http impri https://api.impri.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: IMPRI_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Impri 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
Only io.github.firebase/firebase-mcp asks for
IS_FIREBASE_MCP
Only Impri asks for
IMPRI_API_KEY (secret)IMPRI_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.firebase/firebase-mcp · What it can do: Impri · 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.