Firebase Emulator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIREBASE_PROJECT_ID | Yes | Your Firebase project ID | |
| FIREBASE_RTDB_NAMESPACE | Yes | Your Realtime Database namespace (e.g., <proj_id>-default-rtdb) |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| emulator_statusB | Check reachability of all Firebase emulators |
| firestore_list_collectionsA | List root-level collection IDs from Firestore emulator |
| firestore_queryD | Query documents in a Firestore collection |
| firestore_getA | Get a single Firestore document by path (e.g. Member/abc123) |
| rtdb_getA | Read data from Realtime Database emulator at a given path |
| auth_list_usersB | List users from Auth emulator |
| auth_get_userA | Get a single Auth user by email or localId |
| emulator_logsB | Stream recent log entries from the Firebase emulator hub WebSocket (ws://127.0.0.1:4500/) |
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 8 tools
Each tool targets a clear, distinct resource and action: Firestore operations are separate (list collections, query, get document), RTDB has a single get, Auth has list and get, and status/logs are emulator-wide. No two tools overlap in purpose.
Most tools follow a consistent {service}_{action} pattern (firestore_list_collections, firestore_get, auth_list_users), but emulator_status and emulator_logs deviate to a noun-based pattern. Still predictable and easy to navigate.
Eight tools is well-scoped for a Firebase emulator server, covering the core services (Firestore, RTDB, Auth) plus status and logs without unnecessary bloat.
The tool surface is heavily read-only: Firestore only supports list, query, and get, with no create, update, or delete operations. RTDB and Auth similarly lack write operations, making it impossible to fully manage data in the emulator.