Firebase MCP logo

Firebase MCP

Exposes Firebase CLI workflows for project management, deployment, emulation, authentication, databases, and app distribution.

Install Firebase MCP

Run the project’s own setup commands, in order.

Setup steps from the project

firebase-mcp installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Install
    npm install -g firebase-tools
    
  2. 2. Install
    curl -sL firebase.tools | bash
    

Overview

firebase-mcp brings Firebase CLI operations into AI-assisted development workflows through the official Firebase MCP Server. It can support project and app management, deployment, local emulators, Hosting, Authentication data transfer, Realtime Database work, and App Distribution tasks. Reach for it when an AI assistant needs to work with Firebase projects alongside a local project directory and Firebase CLI configuration. The repository provides an npm-based launch command and a Cursor installation link.

Use cases

  • Deploy Firebase project code and assets
  • Run Firebase Hosting and emulator workflows locally
  • Manage Firebase projects, apps, and project aliases
  • Import or export Firebase Authentication accounts
  • Distribute app releases and manage testers

Key features

  • Firebase project and app management
  • Project deployment and local Hosting
  • Firebase emulator startup and test execution
  • Authentication account import and export
  • Realtime Database interaction
  • App Distribution release and tester management

Security & health

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

ActiveLast checked

Recent health check succeeded.

46/46 checks healthy over the last 63d

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 connects AI development workflows with Firebase CLI capabilities. The underlying Firebase CLI is used to test, manage, and deploy Firebase projects from a command line. Its supported areas include project and app administration, deployment, local development, Authentication account transfer, Realtime Database operations, Firebase Hosting, and App Distribution.

Project-focused actions can use the active project alias in the local directory or receive a project ID explicitly. Deployment uses the local project files and firebase.json configuration. This makes the server most relevant when an assistant needs to operate on an existing Firebase project or help set up one locally.

How it works

The repository contains the official Firebase MCP Server alongside the Firebase CLI. The MCP process is launched through the Firebase Tools npm package with npx, using the MCP command and a directory argument:

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

The --dir . argument points the process at the current project directory. Firebase CLI authentication and project selection remain part of the surrounding CLI setup. The CLI supports browser-based login, a no-localhost login flow for remote environments, multiple authorized accounts, and project aliases.

Setup and configuration

Install Node.js and npm, then use the npx command above to start the MCP process without a separate global installation. The repository also documents two ways to install the Firebase CLI itself:

  • npm install -g firebase-tools
  • curl -sL firebase.tools | bash

After installation, authenticate with firebase login or use firebase login --no-localhost where opening a local browser is impractical. A project can be initialized with firebase init, which creates firebase.json, or selected with the Firebase project and alias commands. Project-specific CLI operations require either an active project alias in the working directory or an explicit project ID using -P.

Tools and capabilities

The Firebase CLI operations represented by this integration cover:

  • Creating, listing, and configuring Firebase projects and registered apps.
  • Deploying project code and assets.
  • Starting Hosting and HTTPS-triggered Cloud Functions locally with serve.
  • Starting emulators or running test scripts through emulators:start and emulators:exec.
  • Setting up the Realtime Database and Firestore emulators.
  • Importing and exporting Firebase Authentication accounts.
  • Reading and modifying Realtime Database data through the Firebase CLI workflow.
  • Uploading App Distribution releases, managing testers and groups, and importing or exporting test cases.
  • Listing apps, printing app SDK configuration, and adding Firebase resources to Google Cloud projects.

Limitations and notes

Operations that change Firebase projects, deploy assets, manage users, or distribute builds depend on the authenticated Firebase account and its permissions. Deployment and local serving rely on the project directory and its firebase.json configuration. Emulator workflows require the relevant emulator setup commands before use. The CLI's login command normally requires browser access, although --no-localhost supports code-based authentication on remote machines.

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 development workflows to Firebase projects through the Firebase CLI. Its main tools cover project and app management, deployment, local emulators, Hosting, Authentication account import and export, Realtime Database operations, and App Distribution tasks.

Start it with `npx -y firebase-tools mcp --dir .` from the Firebase project directory. Node.js and npm are required. The repository also provides npm and standalone installation methods for the Firebase CLI, which can then be authenticated and configured for a project.

Authenticate through the Firebase CLI with `firebase login`. For remote environments where a local browser cannot be opened, use `firebase login --no-localhost` to complete authentication with a copied code.

Yes, Cursor is supported through the installation link published for this server. The linked configuration launches `firebase-tools mcp` with `npx` and points it at the current directory.

Use an active Firebase project alias in the working directory or provide a project ID with the CLI's `-P <project_id>` option. The project directory should also contain the relevant `firebase.json` configuration for deployment and local serving workflows.

Related MCP servers

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>