Firebase MCP Server
Firebase MCP Server
Connect Claude to your Firebase project through Firebase's official MCP Server.
The Firebase MCP Server enables Claude to interact with Firestore databases, Firebase Authentication, Cloud Functions, Hosting, Storage, and other Firebase services using natural language commands.
What Can Claude Do with the Firebase MCP Server?
The Firebase MCP Server exposes Firebase service functionality to Claude through the Model Context Protocol.
Core capabilities:
- Firestore and Data Connect Access — Read and write documents, query collections, and manage database data
- Authentication Management — Access user information, manage auth states, and query user records
- Cloud Functions — Interact with deployed functions and view function logs
- Hosting and Storage — Manage deployed sites and access Cloud Storage resources
- Security-Rule-Aware Assistance — Work with Firebase security rules and configurations
- Project Operations — View Firebase project configuration and service status
Access scope: Claude can access Firebase services based on your Firebase CLI authentication and project permissions. The integration respects Firebase security rules and IAM permissions.
How to Install the Firebase MCP Server
Firebase provides an official MCP Server through Firebase Tools.
For Claude Code (Recommended)
Option 1: Plugin Marketplace
claude plugin marketplace add firebase/firebase-tools
claude plugin install firebase@firebase
Option 2: Manual MCP Setup
claude mcp add firebase npx -- -y firebase-tools@latest mcp
Both methods connect Claude to the official Firebase MCP Server.
For Claude Desktop
Add the Firebase MCP Server to your claude_desktop_config.json file:
Configuration file locations:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Configuration structure:
{
"mcpServers": {
"firebase": {
"command": "npx",
"args": ["-y", "firebase-tools@latest", "mcp"]
}
}
}
Restart Claude Desktop after saving the configuration file.
Firebase MCP Authentication
The Firebase MCP Server uses the same credentials as your authorized Firebase CLI environment.
Authentication methods:
- Firebase CLI Session (Default)
- Run
firebase loginin your terminal - Your authenticated session is used by the MCP Server
- No additional credential setup required
- Runtime Environment Credentials
- In CI/CD or server environments, Firebase CLI uses Application Default Credentials (ADC)
- Service accounts or other environment-specific auth can apply
- Advanced: Service Account Configuration
- For specific deployment scenarios, service accounts can be configured
- This is an advanced option, not the default setup path
Typical setup:
Most users authenticate with firebase login before using the MCP Server. This provides access to all Firebase projects your account can access.
Firebase MCP Use Cases & Examples
Example workflows that become possible with the Firebase MCP Server.
Query Firestore Documents
Example prompt:
> "Show me all documents in the 'users' collection where status is 'active'."
Claude can query Firestore collections with filtering criteria.
Create Firestore Documents
Example prompt:
> "Add a new document to the 'posts' collection with title 'New Article', author 'John Doe', and published set to true."
Claude can create documents in Firestore collections.
Manage Authentication Users
Example prompt:
> "List all users who signed up in the last 7 days."
Claude can query Firebase Authentication user records.
View Cloud Functions
Example prompt:
> "Show me the status and recent logs for my deployed Cloud Functions."
Claude can access function deployment information and execution logs.
Check Security Rules
Example prompt:
> "What are the current Firestore security rules for the 'posts' collection?"
Claude can retrieve and display security rule configurations.
Note: These are example use cases. Actual capabilities depend on your Firebase project configuration, security rules, and the MCP server's exposed toolset.
Firebase MCP in an App Ops Surface
Firebase MCP tends to show up in app teams that need Claude to work with Firebase projects, data, and deployment tasks.
What this shows: This screenshot captures Firebase's MCP documentation, representing the real setup path used for app-side debugging and project automation.
Why this scenario matters: It ties the page to a real Firebase operator surface, which is where app teams actually debug data, auth, and project wiring with assistant help.
Typical assistant task: Inspect project resources, reason about app data, and troubleshoot Firebase-linked workflows from one assistant session.
Source: Firebase MCP Docs
When to Pick Firebase MCP Server vs Supabase
This comparison is most useful when both options look plausible on paper but differ in operating model, team fit, and day-to-day workflow cost.
| Decision Lens | This Page's MCP Path | Competitor |
|---|---|---|
| Best For | Google-first app teams using Firebase services as the center of product operations. | Teams building around SQL, Postgres tooling, and policy-led data access rather than document-first app data. |
| Where MCP Wins | Firebase MCP wins when the stack already lives in Firebase and the assistant should work close to that app surface. | |
| Tradeoff to Watch | It is a weaker fit than Supabase when relational data models and SQL-native workflows drive the product architecture. | |
| Choose This Path When | Choose Firebase MCP for Firebase-native app operations; choose Supabase when Postgres and SQL are central to the stack. | |
| Sources | ||
Frequently Asked Questions
Is the Firebase MCP Server free?
Do I need to set up a Service Account?
What's the difference between plugin install and manual MCP setup?
Can Claude trigger Cloud Functions?
Do Firebase security rules apply?
Does it work with Firebase Emulator?
How do I switch between Firebase projects?
firebase use <project-id> to switch projects in your CLI. The MCP server follows your active project selection.Use Firebase MCP in Verdent
Verdent provides streamlined Firebase integration with simplified authentication. This is Verdent's platform-level integration flow, not the default setup path from Firebase's official documentation.
Connect your Firebase project once and access Firestore, Auth, and other services across all Verdent projects without manual CLI configuration.