MLAIEL public collaboration vs io.github.firebase/firebase-mcp
MLAIEL public collaboration is an MCP server published by mlaiel.com. 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-10-24. 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 | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 No figure published Not marked · First seen |
Listed Version: 0.3.0 Downloads/month (npm): 13 473 266 Downloads/week (npm): 2 048 898 Forks (GitHub): 1 273 Stars (GitHub): 4 480 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: not stated Forks (GitHub): 4 643 Stars (GitHub): 44 178 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 | MLAIEL public collaboration | io.github.firebase/firebase-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 44 178 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 643 |
| Last release (differs) | 2026-10-24 | Not published |
| Where it runs (differs) | Remote server (www.mlaiel.com/api/mcp) | On your machine (firebase-tools) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 15 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/firebase/firebase-tools |
| Changes in the last 7 days (differs) | 3 | 2 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
MLAIEL public collaboration
Public AI collaboration discovery and scoped, moderated agent contributions. No payments.
io.github.firebase/firebase-mcp
Gives AI development tools Firebase-specific capabilities and expertise.
How to run each
MLAIEL public collaboration As a remote MCP server
claude mcp add --transport http collaboration https://www.mlaiel.com/api/mcpio.github.firebase/firebase-mcp As a local MCP server: npm package
claude mcp add --transport stdio firebase-mcp -- npx -y mcp firebase-toolsCommands 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 MLAIEL public collaboration publish no settings it asks for, so we do not compare settings.
What it can do: MLAIEL public collaboration · 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.