Log inSubmit server
Firebase MCP logo

Firebase MCP

Exposes Firebase project management, deployment, emulation, database, Hosting, App Distribution, and Auth workflows through MCP.

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.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for firebase-mcp, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

firebase-mcp brings Firebase CLI workflows to AI assistants through the official Firebase MCP Server. It supports project management, deployment, local emulators, Hosting development, database interaction, App Distribution, and Firebase Auth data transfer. The server runs from the Firebase Tools package and uses a project directory for project-specific operations. Reach for it when an agent needs to inspect, test, manage, or deploy Firebase resources from an MCP-compatible client.

Use cases

  • Deploy Firebase project code and assets
  • Run Firebase emulators for local tests
  • Manage Firebase projects and registered apps
  • Start a local Firebase Hosting server
  • Import or export Firebase Authentication accounts

Key features

  • Firebase project and app management
  • Project deployment workflows
  • Local Hosting and emulator control
  • Firebase database interaction
  • Authentication account import and export
  • App Distribution tester and test-case management

Security & health

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

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 40d

Adoption & maintenance

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

GitHub stars4.5kStargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Firebase MCP works

What firebase-mcp does

firebase-mcp exposes Firebase development and administration workflows to AI assistants through the Firebase MCP Server included in the Firebase CLI repository. Its scope follows the Firebase CLI: managing projects and apps, deploying project code and assets, running local development services and emulators, working with Firebase data, handling App Distribution testers and test cases, and importing or exporting Firebase Authentication users.

Project-specific actions can use the active Firebase project associated with the current directory or receive a project ID through the CLI's project-selection mechanism. The repository also includes the broader Firebase command-line interface, so the MCP server is part of a toolset that can be used from the terminal as well as through an MCP client.

How it works

The server is distributed with the firebase-tools npm package and is started with the Firebase CLI's mcp command. The installation link supplied by the project uses npx to run firebase-tools and passes the current directory as the working directory:

Terminal
npx -y firebase-tools mcp --dir .

The working directory matters for operations that depend on local Firebase configuration. Deployment and local Hosting workflows use firebase.json and the project files in that directory. Firebase CLI authentication and project selection provide the account and project context for operations that require access to Firebase resources.

Setup and configuration

Install Node.js and npm before using the npm-based command. The Firebase CLI can also be installed globally with:

Terminal
npm install -g firebase-tools

After installation, authenticate with Firebase using firebase login, then select or configure the project as needed. A project can be initialized in the current directory with firebase init, which creates a firebase.json file. For non-interactive or remote environments, the CLI supports firebase login:ci; firebase login --no-localhost provides a browser-free authentication flow for machines accessed over SSH.

Start the MCP process from the project directory, or point it at one with --dir. Project-specific CLI operations can also use -P <project_id> to select a Firebase project explicitly.

Tools and capabilities

The Firebase CLI functionality represented by the project includes:

  • Creating, listing, and configuring Firebase projects and apps.
  • Deploying Firebase project code and assets.
  • Starting a local Firebase Hosting server and HTTPS-triggered Cloud Functions with firebase serve.
  • Starting emulators or running a test script against them with emulators:start and emulators:exec.
  • Setting up the Realtime Database and Firestore emulators.
  • Interacting with Firebase database data.
  • Importing and exporting Firebase Authentication accounts in batches.
  • Distributing application releases, managing testers and groups, and importing or exporting App Distribution test cases.
  • Listing project apps and printing an app's SDK configuration.

Limitations and notes

Deployment and local Hosting behavior depends on the local project directory and its firebase.json configuration. Commands that operate on a specific project require either an active project alias in the current directory or an explicit project ID. Authentication requires access to a Firebase account, and the standard login flow requires a web browser unless a supported non-localhost or non-interactive method is used.

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

firebase-mcp is an MCP server that connects AI assistants to Firebase through the Firebase CLI. Its main tools cover project and app management, deployment, local Hosting and emulator workflows, database interaction, Firebase Authentication account import and export, and App Distribution operations such as tester and test-case management.

Run `npx -y firebase-tools mcp --dir .` from the directory you want to use as the Firebase project context. The npm-based setup requires Node.js and npm. You can also install the Firebase CLI globally with `npm install -g firebase-tools`.

Authenticate with `firebase login` before using Firebase operations. For remote machines, use `firebase login --no-localhost`; for non-interactive environments, the Firebase CLI also provides `firebase login:ci`.

Yes, firebase-mcp can be installed in Cursor using the Firebase project's MCP installation link. The link configures Cursor to run `npx -y firebase-tools mcp --dir .`.

Use a directory with an active Firebase project alias or specify the project ID with `-P <project_id>`. The working directory is also used for local project configuration, including the `firebase.json` file used by deployment and Hosting workflows.

Related MCP servers

All in Cloud Platforms 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/firebase-mcp?style=directory)](https://allmcps.com/mcp/firebase-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/firebase-mcp"><img src="https://allmcps.com/api/badge/firebase-mcp?style=directory" alt="Firebase MCP on AllMCPs" /></a>