Firebase MCP Server

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).