Enables inspection and management of Firebase Emulator data, including tools for listing Firestore collections and documents, querying collections with filters, and retrieving Firebase function logs with advanced filtering.
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 show me the last 10 error logs for the processPayment function"
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.
MCP server for inspecting Firebase Emulator Firestore and function logs.
npm install
npm run buildRelated MCP server: Firestore MCP Server
Copy .env.example to .env and adjust:
FIRESTORE_EMULATOR_HOST=localhost:8080
FIREBASE_PROJECT_ID=demo-project
FIREBASE_EMULATOR_HUB=localhost:4000Add to claude_desktop_config.json:
{
"mcpServers": {
"firebase": {
"command": "node",
"args": ["/path/to/firebase_mcp_server/dist/index.js"],
"env": {
"FIRESTORE_EMULATOR_HOST": "localhost:8080",
"FIREBASE_PROJECT_ID": "your-project-id",
"FIREBASE_EMULATOR_HUB": "localhost:4000"
}
}
}
}Tool | Description |
| List top-level Firestore collections |
| List subcollections of a document |
| List documents in a collection |
| Get a single document by path |
| Query with filters, ordering, limit |
| Get function logs with grep-style filtering |
pattern - Regex to filter log messages
level - DEBUG/INFO/WARN/ERROR
functionName - Filter by function name
limit - Max entries (default 50)
since - ISO timestamp cutoff
Get an ID token for a user in the Auth emulator. Lists users if no uid provided.
Inputs: uid.
Get a single document by path
Inputs: documentPath (required).
Get information about the current Firebase environment
Inputs: no named parameters.
Get Firebase function logs. Returns 20 lines by default - use filters (pattern, level, functionName) to narrow results before increasing limit.
Inputs: pattern, level, functionName, limit, +1 more.
List top-level collections in Firestore
Inputs: no named parameters.
List documents in a collection with optional limit
Inputs: collectionPath (required), limit.
List all Cloud Functions registered in the emulator
Inputs: no named parameters.
List subcollections of a document
Inputs: documentPath (required).
Query a collection with filters
Inputs: collectionPath (required), filters, orderBy, orderDirection, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 9 tools
Most tools have distinct purposes targeting different Firebase services (Auth, Firestore, Functions, Environment). However, 'list_documents' and 'query_collection' could cause some confusion as both operate on collections, though descriptions clarify that one lists while the other filters.
All tools follow a consistent verb_noun pattern (e.g., get_auth_token, list_collections, query_collection). The naming is uniform across all 9 tools with no deviations in style or structure.
With 9 tools, this is well-scoped for a Firebase server covering Auth, Firestore, Functions, and environment management. Each tool appears purposeful and earns its place without feeling excessive or sparse.
The server covers read operations well (get, list, query) but lacks write operations (create, update, delete) for Firestore documents or Auth users, which are core to Firebase workflows. This creates notable gaps that agents may struggle with for full CRUD functionality.
Interact with your Google Cloud Firestore resources using natural language commands.
Manage FireCMS Cloud from an AI agent: Firestore data, collections, schemas and users.
Ingest and search LogsLoom logs from coding agents.
Run SOQL queries to explore and retrieve Salesforce data. Inspect records, fields, and relationshi…