Ext Ops Panel
Open dashboard
Comparison

io.github.firebase/firebase-mcp vs Skybridge Everything App

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). Skybridge Everything App is an MCP server published by everything.skybridge.tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplaceio.github.firebase/firebase-mcpSkybridge Everything App
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.0.2
No figure published
Not marked · First seen
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 390
Stars (GitHub): 40 325
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

io.github.firebase/firebase-mcp vs Skybridge Everything App
Factio.github.firebase/firebase-mcpSkybridge Everything App
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)40 325No figure on GitHub
Forks (GitHub) (differs)4 390No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (firebase-tools)Remote server (everything.skybridge.tech)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/firebase/firebase-toolsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 19 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

In its own words, on Official MCP Registry:

Gives AI development tools Firebase-specific capabilities and expertise.

Skybridge Everything App

In its own words, on Official MCP Registry:

Example and testing ChatGPT and MCP App showcasing all the features of the Skybridge framework

How to run each

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

Skybridge Everything App As a remote MCP server

Claude Code
claude mcp add --transport http everything https://everything.skybridge.tech

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Skybridge Everything App 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

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

What it can do: io.github.firebase/firebase-mcp · What it can do: Skybridge Everything App · 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. 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