firebase-auth vs io.github.bea-technology/roxyon
firebase-auth is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
firebase-auth is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. io.github.bea-technology/roxyon is an MCP server published by bea-technology. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.bea-technology/roxyon | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.0 Downloads/month (npm): 437 Downloads/week (npm): 59 Forks (GitHub): 0 Stars (GitHub): 0 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 | firebase-authno longer listed · | io.github.bea-technology/roxyon |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (mcp.roxyon.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/bea-technology/roxyon-devtools |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 35 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of firebase-auth
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Firebase project workflows including setup, features, debugging, and validation
-
Enterprise-grade auth, easy to implement. Add login, SSO, MFA, and access control to any app with framework-aware guidance.
-
Firebase project workflows including setup, features, debugging, and validation
-
firebase-mcp io.github.firebase/firebase-mcp
Gives AI development tools Firebase-specific capabilities and expertise.
-
Add authentication and user management with Clerk. Skills for setup, framework patterns, organizations, billing, webhooks, and testing, plus the Clerk MCP server.
-
WorkOS integration skills for AuthKit, SSO, Directory Sync, RBAC, Vault, Audit Logs, migrations, and API references.
What each says it does
firebase-auth
Generate Firebase Authentication integration
io.github.bea-technology/roxyon
Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.
How to run each
firebase-auth
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.bea-technology/roxyon As a remote MCP server
claude mcp add --transport http roxyon https://mcp.roxyon.com/mcpRequires: ROXYON_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.bea-technology/roxyon 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 firebase-auth publish no settings it asks for, so we do not compare settings.
What it can do: firebase-auth · What it can do: io.github.bea-technology/roxyon · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.