Firebase MCP Server
The Firebase MCP Server provides a unified interface to interact with multiple Firebase services:
Authentication: Retrieve user information by ID or email.
Firestore:
Add, update, delete, and get documents by ID.
List collections and documents with optional filtering and pagination.
List root collections or subcollections under a document.
Storage:
List files in specified directories.
Retrieve file metadata and download URLs.
Provides a unified interface to interact with various Firebase services including Authentication, Firestore, and Storage, allowing users to get user information, manage Firestore documents and collections, and handle Storage files
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Firebase MCP Server list all users in the authentication database"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Firebase MCP Server
Overview
This is a Firebase MCP (Model Context Protocol) server that provides a unified interface to interact with various Firebase services including Authentication, Firestore, and Storage.
Related MCP server: Firestore Advanced MCP
Setup
Clone and build the project:
git clone https://github.com/gemini-dk/mcp-server-firebase cd mcp-server-firebase npm install npm run buildGet Firebase service account key:
Go to Firebase Console > Project Settings > Service accounts
Click "Generate new private key"
Save the JSON file to your project directory
Configure
mcp_settings.json:{ "firebase-mcp": { "command": "node", "args": [ "/path/to/mcp-server-firebase/dist/index.js" ], "env": { "SERVICE_ACCOUNT_KEY_PATH": "/path/to/serviceAccountKey.json" } } }Replace
/path/to/mcp-server-firebasewith the actual path where you cloned the repository. Replace/path/to/serviceAccountKey.jsonwith the path to your service account key file.
Available APIs
Authentication
Get user by ID or email
Firestore
Add/update/delete documents
List collections/documents
Storage
List files in a directory
Get File metadata and Download URL
License
MIT License
Available Tools
9 toolsauth_get_userB
Get a user by ID or email from Firebase Authentication
Inputs: identifier (required).
firestore_add_documentC
Add a document to a Firestore collection
Inputs: collection (required), data (required).
firestore_delete_documentC
Delete a document from a Firestore collection
Inputs: collection (required), id (required).
firestore_get_documentC
Get a document from a Firestore collection
Inputs: collection (required), id (required).
firestore_list_collectionsA
List collections in Firestore. If documentPath is provided, returns subcollections under that document; otherwise returns root collections.
Inputs: documentPath, limit, pageToken.
firestore_list_documentsC
List documents from a Firestore collection with optional filtering
Inputs: collection (required), filters, limit, pageToken.
firestore_update_documentC
Update a document in a Firestore collection
Inputs: collection (required), id (required), data (required).
storage_get_file_infoC
Get file information including metadata and download URL
Inputs: filePath (required).
storage_list_filesC
List files in a given path in Firebase Storage
Inputs: directoryPath.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by Firebase service (Authentication, Firestore, Storage) and specific operations within each service, making it easy to distinguish between them. For example, firestore_get_document retrieves a single document while firestore_list_documents lists multiple documents with filtering.
Tool names follow a highly consistent verb_noun pattern throughout, with clear service prefixes (auth_, firestore_, storage_). All tools use snake_case consistently, and the naming convention is predictable and readable across all nine tools.
With 9 tools, this server is well-scoped for covering core Firebase operations across multiple services. Each tool earns its place by addressing distinct functionality without being overwhelming. The count is appropriate for the server's purpose of providing access to Firebase Authentication, Firestore, and Storage.
The tool surface provides excellent coverage for Firestore (full CRUD operations plus listing) and good coverage for Storage and Authentication. Minor gaps exist, such as no user creation/update/deletion in Authentication and no file upload/download in Storage, but agents can work around these limitations for many common workflows.
Maintenance
Related MCP Connectors
Butterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.
Unified.to MCP server — one API for 500+ B2B SaaS integrations across 28+ categories
MCP server for interacting with the Supabase platform
Backend for AI agents: one batched tool over ~668 actions (hosting, storage, auth, payments).
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceThe Firebase MCP server provides a standardized interface to interact with Firebase services, including Firebase Authentication, Firestore, and Firebase Storage.1,817 npm247MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables large language models like Claude to perform comprehensive interactions with Firebase Firestore databases, supporting full CRUD operations, complex queries, and advanced features like transactions and TTL management.15 npm4MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP Server providing access to Google's Firebase API, allowing natural language interaction with Firebase services and resources.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that exposes Firebase Firestore and Authentication to AI agents, supporting multi-project configurations and read operations.5124 npmMIT