Everpod vs io.github.firebase/firebase-mcp
Everpod is an MCP server published by everpod.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-10-18. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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 |
| Claude Code: claude-plugins-official | Not listed | Listed Version: not stated Forks (GitHub): 4 462 Stars (GitHub): 41 694 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 | Everpod | io.github.firebase/firebase-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 41 694 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 4 462 (better) |
| Last release (differs) | 2026-10-13 | Not published |
| Where it runs (differs) | Remote server (everpod.ai/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) | github.com/everpod-ai/mcp | github.com/firebase/firebase-tools |
| Changes in the last 7 days | 2 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 28 h ago | 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
Everpod
Your own AI agent on an always-on cloud computer: Claude Code, Codex and more, or managed OpenClaw.
io.github.firebase/firebase-mcp
Gives AI development tools Firebase-specific capabilities and expertise.
How to run each
Everpod As a remote MCP server
claude mcp add --transport http everpod https://everpod.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
io.github.firebase/firebase-mcp As a local MCP server: npm package
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.
Only Everpod 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
The marketplaces of Everpod publish no settings it asks for, so we do not compare settings.
What it can do: Everpod · 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.