Firebase MCP Server
Connect your AI to Firebase projects, Firestore, Crashlytics, messaging, and Remote Config.
Firebase MCP Server
The official Firebase MCP server connects your AI assistant to your Firebase project through the Firebase CLI. Ordinary product events use Wire by default. Inspect Firebase Analytics and explicitly set user properties in the Firebase or linked Google Analytics console; the official MCP tool list does not expose Analytics queries.
Features
- Firestore Inspection: Read collections and documents to understand your NoSQL schema.
- Remote Config Management: Read and propose updates to your Remote Config template.
- Crashlytics Insights: Summarize recent crash reports and their stack traces.
- Project Operations: Inspect apps, authentication users, security rules, messaging, functions, and project configuration.
Installation & Configuration
Prerequisites
- Firebase Project Created.
firebase-toolsCLI installed and authenticated (runfirebase login).- A Firebase CLI login or Application Default Credentials.
Method 1: Using CLI Auth (Quick Start)
If you have firebase-tools installed and are logged in, the MCP server can often reuse your local credentials.
Setup for Cursor
- Open Cursor Settings > Features > MCP.
- Click + Add New MCP Server.
- Fill in the details:
| Field | Value |
|---|---|
| Name | firebase |
| Type | command |
| Command | npx -y firebase-tools@latest mcp |
Run the server from the app directory. Pin the default project in .firebaserc, or use the MCP environment tools to select it.
Setup for Claude Code
{
"mcpServers": {
"firebase": {
"command": "npx",
"args": ["-y", "firebase-tools@latest", "mcp"]
}
}
}Usage Examples
1. Explore Data:
"List the collections in my Firestore root." "Show me the structure of a document in the
userscollection."
2. Inspect project configuration:
"List the Firebase apps registered in the active project."
Use the Firebase or linked Google Analytics console for explicit Firebase Analytics properties. Use Wire for ordinary lifecycle, screen, onboarding, purchase-funnel, and activation-event questions.
3. Debug Crashes:
"Summarize the top 3 most frequent crashes from the last 24 hours."