Firebase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| firestore_add_documentC | Add a document to a Firestore collection |
| firestore_list_collectionsA | List collections in Firestore. If documentPath is provided, returns subcollections under that document; otherwise returns root collections. |
| firestore_list_documentsC | List documents from a Firestore collection with optional filtering |
| firestore_get_documentC | Get a document from a Firestore collection |
| firestore_update_documentC | Update a document in a Firestore collection |
| firestore_delete_documentC | Delete a document from a Firestore collection |
| auth_get_userB | Get a user by ID or email from Firebase Authentication |
| storage_list_filesC | List files in a given path in Firebase Storage |
| storage_get_file_infoC | Get file information including metadata and download URL |
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
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.