Best for
- Developers already using the firebase-tools CLI who want an AI assistant to perform common Firebase operations
- Teams doing Firebase integration work from within a local project directory
F
Firebase MCP Server
Official
Firebase-specific capabilities for AI coding tools
GitHub source repository ↗
59FMRS · C
This server is shipped directly from the official Firebase repository (firebase/firebase-tools), running the firebase-tools npm package's mcp subcommand over stdio. The source material does not list individual tool names or confirm support for clients beyond the Cursor one-click install shown in the README. Users should verify Firebase authentication is configured and be aware the underlying CLI can perform high-privilege actions like deployments and data deletion.
The Firebase MCP Server ships inside the firebase/firebase-tools repository and exposes Firebase platform operations over stdio so AI development tools can work with a Firebase project — deploying Hosting sites and Cloud Functions, reading/writing Realtime Database and Firestore data, managing Auth user import/export, and configuring Remote Config or App Distribution. It runs the firebase-tools npm package via npx with the mcp subcommand and relies on whatever Firebase authentication the user has already set up (firebase login, a service account key, or application default credentials).
Tools
The tool list has not been reviewed yet.
Setup
- Install Node.js/npm locally. 2. Authenticate with
firebase login, or setGOOGLE_APPLICATION_CREDENTIALSto a service account key file. 3. Add a stdio MCP server entry pointing the command atnpxwith args-y firebase-tools mcp --dir .(--dirshould point at your Firebase project folder). 4. Restart the MCP client and confirm the Firebase tools appear in its tool list.
claude_desktop_config.json
{"mcpServers":{"firebase":{"command":"npx","args":["-y","firebase-tools","mcp","--dir","."]}}}
Fit and risk
Not for
- Users without an existing Firebase project or local authentication set up
- Teams that require strict approval gates before an AI agent can trigger production deploys or data deletions
Required permissions
- Local filesystem access (to read the project directory and files like firebase.json)
- Firebase/Google Cloud credentials (user login session, service account key, or application default credentials)
- Network access to the target Firebase project
Risks and side effects
- firebase-tools supports destructive operations (e.g. firestore:delete, database:remove) and production deploys, so overly broad credentials could let an AI agent cause data loss or affect a live project
- Service account keys and long-lived user tokens are highly sensitive credentials if leaked
- Neither the README nor server.json enumerates the specific MCP tools exposed, so the exact operation surface should be verified before use
Troubleshooting
- Verify Node.js and npm are installed and that `npx firebase-tools` runs successfully on its own
- Confirm authentication is complete via `firebase login` or a valid `GOOGLE_APPLICATION_CREDENTIALS` path
- Check that the working directory has a valid firebase.json/project alias, or pass `-P <project_id>` explicitly
- In CI or headless environments, use a service account or a `firebase login:ci`-generated token instead of interactive login
Use cases
Letting an AI assistant inspect and deploy Firebase project resources during development
Reading and writing Firestore / Realtime Database data from within a local project directory for debugging
Triggering Hosting or Cloud Functions deployments through an AI assistant
Managing Firebase Auth user import/export or Remote Config templates as part of routine ops work
Supported clients
CursorFull support