Log inSubmit server
Firebase MCP logo

Firebase MCP

by gannonh

Connects MCP clients to Firebase Auth, Firestore, and Storage for database, file, and user operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Firebase MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "gannonh-firebase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@gannonh/firebase-mcp"
      ],
      "env": {
        "SERVICE_ACCOUNT_KEY_PATH": "YOUR_VALUE_HERE",
        "FIREBASE_STORAGE_BUCKET": "YOUR_VALUE_HERE",
        "MCP_TRANSPORT": "YOUR_VALUE_HERE",
        "MCP_HTTP_PORT": "YOUR_VALUE_HERE",
        "MCP_HTTP_HOST": "YOUR_VALUE_HERE",
        "MCP_HTTP_PATH": "YOUR_VALUE_HERE",
        "DEBUG_LOG_FILE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @gannonh/firebase-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 24d ago.

Overview

gannonh/firebase-mcp MCP server connects AI assistants to Firebase Authentication, Firestore, and Storage through MCP tools. It supports document CRUD, collection listing and queries, file listing and uploads, file metadata retrieval, and user lookup. The server runs over stdio by default and can also expose an HTTP endpoint with session management. Use it when an MCP client needs to inspect or modify data in a Firebase project using service-account credentials.

Use cases

  • Manage Firestore documents from an AI client
  • Query documents across Firestore subcollections
  • Upload files to Firebase Storage
  • Inspect Firebase Storage metadata and URLs
  • Look up Firebase Authentication users

Key features

  • Firestore document CRUD operations
  • Root collection and collection-group queries
  • Firebase Storage file listing and uploads
  • Authentication user lookup by ID or email
  • stdio and HTTP transports
  • Configurable debug logging

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

21/21 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @gannonh/firebase-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars247Stargazers on the source repository.
npm downloads5.5kPackage downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Firebase MCP works

What gannonh/firebase-mcp does

gannonh/firebase-mcp MCP server exposes selected Firebase operations to MCP-compatible AI clients. It connects to Firestore for document and collection operations, Firebase Storage for file management, and Firebase Authentication for retrieving users by ID or email.

The Firestore interface covers adding, listing, reading, updating, and deleting documents. It can also list root collections and query documents across subcollections with a shared collection ID. Storage tools list files, return file metadata and URLs, and upload content either directly or from a URL. Authentication provides a user lookup operation.

The project belongs in the Cloud Platforms category for workflows where an agent needs controlled access to an existing Firebase project rather than a separate database or file service.

How it works

The server uses a Firebase service-account JSON key for initialization. MCP clients communicate with it through stdio by default. An HTTP transport is also available, allowing the server to run as a standalone service at a configurable endpoint. HTTP mode supports multiple clients by assigning each connection a session ID.

Clients can start the published package with npx, or run a locally built JavaScript entry point. After registration, an agent can call the exposed tools using their required parameters, such as a Firestore collection and document ID or a Storage file path.

Setup and configuration

A Firebase project and a Node.js environment are required. Create a service-account key in Firebase Console under Project Settings and Service Accounts, then store the JSON file securely. Set SERVICE_ACCOUNT_KEY_PATH to its absolute path.

FIREBASE_STORAGE_BUCKET can specify the Storage bucket; when omitted, the server uses the project ID with the appspot.com suffix. For transport configuration, MCP_TRANSPORT accepts stdio or http and defaults to stdio. HTTP mode also supports MCP_HTTP_PORT, MCP_HTTP_HOST, and MCP_HTTP_PATH, which default to port 3000, localhost, and /mcp respectively.

For diagnostics, set DEBUG_LOG_FILE to true to write to ~/.firebase-mcp/debug.log, or set it to a custom file path. The package can be launched with npx -y @gannonh/firebase-mcp, or installed from source with npm and built using the documented build command.

Tools and capabilities

The gannonh/firebase-mcp MCP server provides these tool groups:

  • Firestore: add, list, get, update, and delete documents; list root collections; query collection groups.
  • Storage: list files in an optional directory, retrieve file information and a URL, upload content, and upload a file from a URL.
  • Authentication: retrieve a user using an ID or email address.

Firestore queries may require a composite index. Firebase returns a link for creating the index when one is needed. The firestore_list_collections operation may also produce a Zod validation message in client logs even though the collection query returns its data successfully; the README identifies this as an MCP SDK validation issue.

Limitations and notes

The server requires valid service-account credentials and appropriate Firebase permissions. Storage operations depend on the configured bucket existing; an incorrect bucket name causes initialization or storage errors. HTTP mode requires clients to connect to the configured MCP URL, while stdio mode is the default for local client configurations.

The documented authentication capability is limited to retrieving a user by identifier. Firestore operations may also depend on indexes configured in the Firebase project.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Firebase MCP

gannonh/firebase-mcp is an MCP server that connects AI clients to Firebase Authentication, Firestore, and Storage. Its main tools manage Firestore documents and collections, list and upload Storage files, retrieve file metadata, and look up Authentication users by ID or email. It uses a Firebase service-account key for access.

Install it by adding an MCP configuration that runs `npx -y @gannonh/firebase-mcp`, then set `SERVICE_ACCOUNT_KEY_PATH` to an absolute service-account JSON path. A local installation can instead run the built `dist/index.js` file.

It supports Firestore, Firebase Storage, and Firebase Authentication. Firestore tools manage documents and collections, Storage tools list and upload files or retrieve metadata, and the Authentication tool retrieves a user by ID or email.

Yes, gannonh/firebase-mcp works with Cursor. Add its configuration to `[project root]/.cursor/mcp.json`, including the launch command and Firebase environment variables such as `SERVICE_ACCOUNT_KEY_PATH`.

Set `MCP_TRANSPORT=http` and optionally configure `MCP_HTTP_PORT`, `MCP_HTTP_HOST`, and `MCP_HTTP_PATH`, then start the package. The default endpoint is `http://localhost:3000/mcp`, and HTTP mode supports sessions for multiple clients.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFirebase MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gannonh-firebase-mcp?style=directory)](https://allmcps.com/mcp/gannonh-firebase-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/gannonh-firebase-mcp"><img src="https://allmcps.com/api/badge/gannonh-firebase-mcp?style=directory" alt="Firebase MCP on AllMCPs" /></a>