mcp -firebase

This MCP server exposes a unified interface to interact with Firebase services, including Authentication, Firestore, and Storage. Clients and other MCP tools can send Model Context Protocol requests to perform user lookups (by ID or email), manage Firestore documents (create, update, delete, and list), and interact with the Storage layer (list directory contents and fetch file metadata or download URLs). The server is configured to read the Firebase service account key from the SERVICE_ACCOUNT_KEY_PATH environment variable, enabling secure access to your Firebase project.

To use the server, point your MCP client at the configured server (as defined in mcp_settings.json) and invoke the available APIs under Authentication, Firestore, and Storage. Ensure your service account file is valid and that the path in SERVICE_ACCOUNT_KEY_PATH is correct. Each API section exposes methods typical for MCP workflows, such as retrieving a user by ID or email, performing CRUD operations on Firestore documents, and listing or downloading files from Storage.

Prerequisites:

• Node.js and npm installed
• Access to a Firebase project and a service account key JSON file
• Git installed (optional for cloning)

Step-by-step:

1. Clone the repository and install dependencies

   • git clone https://github.com/gemini-dk/mcp-server-firebase
   • cd mcp-server-firebase
   • npm install

2. Build the project

   • npm run build This generates the distributable at dist/index.js (path may vary based on build output).

3. Obtain Firebase service account key

   • In Firebase Console, go to Project Settings > Service accounts
   • Generate a new private key and save the JSON file locally

4. Configure mcp_settings.json

   • Create or edit mcp_settings.json to point to the built server and service account key, e.g.:

   { "firebase-mcp": { "command": "node", "args": [ "/path/to/mcp-server-firebase/dist/index.js" ], "env": { "SERVICE_ACCOUNT_KEY_PATH": "/path/to/serviceAccountKey.json" } } }

5. Run the MCP server via your preferred orchestrator (npx/uvx/docker are also options if configured). Ensure the SERVICE_ACCOUNT_KEY_PATH is correct and the path to the built dist/index.js exists.

Tips and common issues:

• Ensure the service account key JSON file is valid and has appropriate Firebase permissions.
• The path values in mcp_settings.json must be absolute paths to the server entrypoint and the service account key file.
• If you encounter authentication errors, double-check the SERVICE_ACCOUNT_KEY_PATH and permissions on the key file.
• If you modify the build output location, update the args in mcp_settings.json accordingly.
• This server currently exposes Authentication (user lookups), Firestore (CRUD operations), and Storage (list and retrieve metadata/download URLs); for complex queries, ensure your client translates MCP requests into the corresponding Firestore queries.
• Monitor logs for startup errors related to missing environment variables or incorrect JSON formats in mcp_settings.json.