Firebase MCP Server
Firebase MCP Server is an MCP server published by Google, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Google. Last verified 2026-08-20.
Does Firebase MCP Server support the current MCP specification (2026-07-28)?
Not yet confirmed. Firebase MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Firebase MCP Server a first-party (official) MCP server?
Yes. Firebase MCP Server is the first-party MCP server published by Google (last verified 2026-08-20).
How do I connect to Firebase MCP Server?
Firebase MCP Server is available via the package npm:firebase-tools, the official MCP Registry under io.github.firebase/firebase-mcp, the source repository at https://github.com/firebase/firebase-tools. Authentication: none. Transports: stdio.
Does Firebase MCP Server support MCP revision 2025-11-25?
Yes. Firebase MCP Server supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Firebase MCP Server support MCP revision 2026-07-28?
No. Firebase MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Firebase MCP Server's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
The Firebase MCP server is not a standalone package: it ships inside the
Firebase CLI monorepo (firebase/firebase-tools, source under
src/mcp/) and runs locally as npx -y firebase-tools@latest mcp. Its
tools span Firebase products, grouped by feature: Firestore, Auth,
Storage, Crashlytics, Functions, App Hosting, Realtime Database, Remote
Config, Messaging, and Data Connect, with --only flags to narrow the
set. The docs page presents its tool list as partial and points at the
server's own capability listing for the full set.
There is no hosted endpoint and no MCP-level authentication. The docs state that tool calls use "the same user credentials that authorize the Firebase CLI in the environment where it's running", a logged-in Google account or Application Default Credentials.
Authority is verifiable from the vendor's own surfaces: the canonical
documentation lives on firebase.google.com and links the
firebase-tools src/mcp source directly, and the firebase GitHub
organization lists firebase.google.com as its site. Note the name
collision: several unrelated third-party repositories also call
themselves "firebase-mcp"; the official record is the one under the
io.github.firebase registry namespace.
No surface names a supported MCP specification revision. The
firebase-tools changelog references SEP-2243 header forwarding
(Mcp-Param-*), which names a spec enhancement proposal rather than a
revision, and the CLI's @modelcontextprotocol/sdk ^1.24.0 dependency is
not evidence of revision support. spec_status is therefore unknown.
The registry record also lags the CLI it describes: it pins
firebase-tools 14.27.0 from December 2025, while the npm latest is
15.26.0 (2026-08-05).
Which MCP spec revisions does Firebase MCP Server support?
Firebase MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Firebase MCP Server?
Ranked #4 in The MCP 500 with Adoption Index 80.31 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 2,186,911 | API · |
| GitHub stars | 4,467 | API · |
| GitHub forks | 1,251 | API · |
| Last push | 2026-09-15T14:37:10Z | API · |
| Repository archived | no | API · |
Repository and package signals for Firebase MCP Server
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 995
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Package (npm) as of
- Latest version
15.28.1- Last published
- First published
- Releases
- 550
- License (package)
- MIT
- Maintainers
- 4
- Direct dependencies
- 70
- Unpacked size
- 5.6 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record io.github.firebase/firebase-mcp version 0.3.0 (published 2025-12-04) - npm package firebase-tools pinned at 14.27.0 with a positional "mcp" argument, stdio transport, repository firebase/firebase-tools subfolder src/mcp - accessed
- Firebase documentation "Firebase MCP server" - run via npx -y firebase-tools@latest mcp; "When the Firebase MCP server makes tool calls, it uses the same user credentials that authorize the Firebase CLI in the environment where it's running"; tool list grouped by Firebase product and described by the page itself as partial; links the firebase-tools src/mcp source - accessed
- firebase-tools src/mcp/server.json - in-repo registry manifest matching the registry record field for field (name io.github.firebase/ firebase-mcp, version 0.3.0, npm firebase-tools 14.27.0, stdio) - accessed
- firebase/firebase-tools releases - latest stable v15.26.0 published 2026-08-05, whose notes mention a fix to the "Firebase MCP server firebase_login" tool; the npm registry lists 15.26.0 as latest, roughly one major version ahead of the registry record's pinned 14.27.0 - accessed
- Staleness re-verification via the GitHub API - repository firebase/firebase-tools active (pushed 2026-08-15, not archived), latest release v15.27.0 (2026-08-13); entity facts unchanged - accessed
- npm registry metadata for firebase-tools at published version 15.28.1, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed