Firebase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIREBASE_PROJECT_ID | Yes | The Firebase project ID | |
| FIREBASE_EMULATOR_HUB | Yes | The host and port for the Firebase emulator hub (e.g., localhost:4000) | localhost:4000 |
| FIRESTORE_EMULATOR_HOST | Yes | The host and port for the Firestore emulator (e.g., localhost:8080) | localhost:8080 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_environmentB | Get information about the current Firebase environment |
| list_collectionsB | List top-level collections in Firestore |
| list_subcollectionsC | List subcollections of a document |
| list_documentsC | List documents in a collection with optional limit |
| get_documentC | Get a single document by path |
| query_collectionC | Query a collection with filters |
| list_functionsB | List all Cloud Functions registered in the emulator |
| get_auth_tokenA | Get an ID token for a user in the Auth emulator. Lists users if no uid provided. |
| get_function_logsA | Get Firebase function logs. Returns 20 lines by default - use filters (pattern, level, functionName) to narrow results before increasing limit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.