Name: Firebase MCP Server
Author: firebase

LABSCO SUMMARY

The Firebase CLI wearing an MCP interface: same credentials, same active project, one tool group per product.

Because it inherits the CLI's authentication and its active project, what an agent can reach is exactly what you can reach from that terminal — and firebase_update_environment is how you move it to a different project mid-session rather than restarting. Some tools route through Gemini in Firebase to generate SQL Connect schemas and answer product questions; Firebase's own guidance is to check that output before shipping it, which is worth taking seriously for generated security rules.

What it is

The Firebase CLI in MCP mode. It is launched as firebase-tools mcp over stdio, acts with the credentials that authorize the CLI in that environment, and groups its tools by Firebase product.

What you get

Sign-in and the working environment — which account, which project directory, which active project the rest of the tools use — firebase_login, firebase_logout, firebase_get_environment, firebase_update_environment
Projects and apps: list and create projects, register iOS, Android and Web apps, read back SDK config, add an Android SHA hash — firebase_list_projects, firebase_get_project, firebase_create_project, firebase_create_app, firebase_list_apps, firebase_get_sdk_config, firebase_create_android_sha
Services initialized in the workspace, and deploys driven from firebase.json with a job id you can poll — firebase_init, firebase_deploy, firebase_deploy_status
Security rules for Firestore, Storage and Realtime Database, retrieved and checked for syntax and validation errors — firebase_get_security_rules, firebase_validate_security_rules
Firestore: collections listed, documents fetched by path, collections queried, documents deleted — firestore_list_collections, firestore_get_documents, firestore_query_collection, firestore_delete_document
Authentication users looked up by UID or email, enabled, disabled or given custom claims, plus an SMS region policy — auth_get_users, auth_update_user, auth_set_sms_region_policy
Crashlytics issues, their events and stack traces, aggregate reports and notes — crashlytics_get_issue, crashlytics_list_events, crashlytics_batch_get_events, crashlytics_get_report, crashlytics_update_issue, crashlytics_create_note, crashlytics_list_notes, crashlytics_delete_note
Realtime Database reads and writes, Cloud Functions logs, Cloud Messaging sends, Remote Config templates, App Hosting backends and logs, and Storage download URLs — realtimedatabase_get_data, realtimedatabase_set_data, functions_get_logs, functions_list_functions, messaging_send_message, remoteconfig_get_template, remoteconfig_update_template, apphosting_list_backends, apphosting_fetch_logs, storage_get_object_download_url
Firebase SQL Connect services listed, schemas and operations compiled, and GraphQL run against a service or its emulator — dataconnect_list_services, dataconnect_build, dataconnect_execute
Google developer documentation searched and answered from a grounded corpus — developerknowledge_search_documents, developerknowledge_answer_query, developerknowledge_get_documents
firebase:// resources the agent can read on its own: init guides for Firestore, Auth, Hosting and GenAI, Crashlytics investigation guides, and Firebase docs pages — firebase_read_resources

Requirements

A Google Account signed in to the Firebase CLI — firebase_login can do it from inside the conversation. Node.js and npm; the server runs as npx -y firebase-tools@latest mcp over stdio, and there is also a Claude plugin and a Gemini CLI extension that install the same thing. Tool calls use whatever credentials authorize the Firebase CLI where the server runs, against whichever project is active.

Setup effort

One command — npx -y firebase-tools@latest mcp

See installation options

USE CASES

01

Setting Firebase services up inside a project you are already working in

Check which account and project are active, then initialize only the services you want.

firebase_get_environmentfirebase_init

02

Debugging against real data instead of a fixture

List the collections, query the one that matters, then pull the specific documents by path.

03

Working out why one user cannot get in

Look the account up by email or UID, then enable it or set the claim it is missing.

04

Chasing a crash your users are hitting

Open the issue, read sample events with their stack traces, and record what you found on the issue itself.

05

Shipping a change and watching it land

Deploy what firebase.json describes, then poll the job until it reports back.

firebase_deployfirebase_deploy_status

06

Checking security rules before they reach production

Retrieve the current rules for the service, then run them through validation for syntax and rule errors.

firebase_get_security_rules

19 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`developerknowledge_answer_query`

Use answer_query to get a grounded answer to a query about Google developer products. This tool has limited quota. This tool will synthesize information from the corpus to generate an answer to the query. answer_query grounds answers using the same corpus as search_documents. This tool returns the generated answer_text and a list of document names (references) used to generate the answer. Use get_documents with the document names to fetch the entire document content if needed.

If you get a 429 out of quota error, use search_documents instead.

BEFORE YOU INSTALL

What to know first

Tools you get

19 tools when we connected. The documentation lists 43 tools in feature groups such as auth, firestore and storage; with no active Firebase project directory or initialised services, only the core group plus a few extras appear.

Requires

npx on PATH

CONTEXT COST

Moderate Standing cost

Rated by the size of the 19 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y firebase-tools@latest mcp

MCP Clients

Gemini CLI

GEMINI CLI · TERMINAL

gemini extensions install https://github.com/firebase/agent-skills

Claude Code — npx

CLAUDE CODE — NPX · TERMINAL

claude mcp add firebase npx -- -y firebase-tools@latest mcp

Claude Code — plugin

CLAUDE CODE — PLUGIN · TERMINAL

claude plugin marketplace add firebase/firebase-tools
claude plugin install firebase@firebase

Cursor, Windsurf, Firebase Studio

JSON

{
  "mcpServers": {
    "firebase": {
      "command": "npx",
      "args": [
        "-y",
        "firebase-tools@latest",
        "mcp"
      ]
    }
  }
}

Firebase MCP Server

The Firebase CLI wearing an MCP interface: same credentials, same active project, one tool group per product.

What it is

What you get

Requirements

Setup effort

Setting Firebase services up inside a project you are already working in

Debugging against real data instead of a fixture

Working out why one user cannot get in

Chasing a crash your users are hitting

Shipping a change and watching it land

Checking security rules before they reach production

19 tools

developerknowledge_answer_query

developerknowledge_get_documents

developerknowledge_search_documents

firebase_create_android_sha

firebase_create_app

firebase_create_project

firebase_deploy

firebase_deploy_status

firebase_get_environment

firebase_get_project

firebase_get_sdk_config

firebase_get_security_rules

firebase_init

firebase_list_apps

firebase_list_projects

firebase_login

firebase_logout

firebase_read_resources

firebase_update_environment

What to know first

Tools you get

Requires

Moderate Standing cost

Connect your client

Server setup

MCP Clients

Gemini CLI

Claude Code — npx

Claude Code — plugin

Cursor, Windsurf, Firebase Studio

Same category

Azure MCP Server

Terry-Form MCP

Terraform RAG

Aiven

`developerknowledge_answer_query`

`developerknowledge_get_documents`

`developerknowledge_search_documents`

`firebase_create_android_sha`

`firebase_create_app`

`firebase_create_project`

`firebase_deploy`

`firebase_deploy_status`

`firebase_get_environment`

`firebase_get_project`

`firebase_get_sdk_config`

`firebase_get_security_rules`

`firebase_init`

`firebase_list_apps`

`firebase_list_projects`

`firebase_login`

`firebase_logout`

`firebase_read_resources`

`firebase_update_environment`