Skip to content
Firebase MCP Server

Firebase MCP Server

by Google
Released
v15.29.0
MIT
Repository Docs npm
Featured Databases & DataCloud & Infrastructure

Summary

Google's official Firebase MCP server — 70+ tools across Firestore, Auth, Crashlytics, Cloud Functions, Storage, Messaging and Remote Config, shipped inside the Firebase CLI.

Features

  • 70+ tools across the Firebase platform
  • Firestore document CRUD, index and database management
  • Authentication, custom claims and SMS region policies
  • Crashlytics issue tracking and report generation
  • Cloud Functions logs, Remote Config and App Hosting
  • MCP prompts (/firebase:init, /firebase:deploy) and documentation resources
  • Reuses Firebase CLI credentials — no separate API key
  • --only flag to load just the feature groups you need

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Firebase MCP Server" tools will be available.
{
  "mcpServers": {
    "firebase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "firebase-tools@latest",
        "mcp"
      ]
    }
  }
}

Description

The Firebase MCP Server is Google's official Model Context Protocol server for Firebase, maintained in the same repository as the Firebase CLI and shipped as part of firebase-tools rather than as a separate package to install and keep in sync.

What it exposes. More than 70 tools spanning the Firebase platform:

  • Firestore — document CRUD, collection listing, database and index management
  • Authentication — user management, custom claims, SMS region policies
  • Crashlytics — issue tracking, event retrieval, report generation and notes
  • Cloud Functions — function listing and log retrieval
  • Realtime Database — reads and writes
  • Cloud Storage — download URL generation
  • Cloud Messaging — sending messages to tokens and topics
  • Remote Config — template management
  • App Hosting — backend management and logs
  • Data Connect / SQL — schema retrieval and operation execution
  • Core — project creation, app registration and security-rules validation

It also ships MCP prompts (/firebase:init, /firebase:deploy) for common workflows and resources that feed Firebase documentation to the model as context — a fuller use of the protocol than the tools-only servers that make up most of the ecosystem.

Auth without a second credential. The server reuses the Firebase CLI's existing credentials — a logged-in user or Application Default Credentials — so there is no separate API key to mint or store. Agents call the firebase_login tool before reaching project-scoped operations.

Scoping the tool surface. Because 70+ tools is a lot of context to hand a model at once, the server takes --only FEATURE_1,FEATURE_2 to load just the feature groups a session needs, and --dir ABSOLUTE_PATH to point at the directory holding firebase.json.

Compatible with Claude Desktop, Claude Code, Cursor, VS Code Copilot, Cline and other MCP clients. MIT-licensed and part of firebase-tools, so it tracks CLI releases directly.

Covered in the Weekly

Related MCP Servers

MCP: Appwrite MCP Server

by Appwrite

Appwrite's official MCP server exposes databases, users, teams, functions and storage as agent tools, over a hosted OAuth endpoint or a local stdio bridge.

Developer Tools

MCP: Neon

by Neon

Neon's official MCP server — manage serverless Postgres projects, branch databases, and run migrations.

Databases & Data
Browse all MCP servers →