Inspect and work with Firebase projects through the official CLI server.
Firebase's official MCP server runs locally through the Firebase CLI and gives a compatible assistant tools for Firebase projects and the application codebase.
The documented command is npx -y firebase-tools@latest mcp. It uses stdio and the credentials available to the Firebase CLI, including a logged-in user or Application Default Credentials. A local process can still call cloud services; local transport does not mean the project data stays entirely offline.
Launch from the intended application or use the documented directory option. Confirm the selected Firebase project before asking for a change. A development project and a production project can have similar names, so check the identifier explicitly.
The --only option limits enabled feature groups, while core tools remain available. Choose the groups needed for the work instead of assuming the server always exposes the same tool list.
Ask the assistant to inspect the current project and explain a failing development workflow using the existing code. For a data operation, start with a small read and check the result against the console or application. For authentication changes, inspect the affected account and project before proceeding.
Firebase documents setup for Claude Code, Cursor, VS Code and other stdio clients. Use the client-specific configuration shape; VS Code's servers object and a desktop client's mcpServers object are not interchangeable. The existing directory URL is preserved for this Firebase repository so earlier links continue to work.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| login | Authenticate to your Firebase account. Requires access to a web browser. |
| logout | Sign out of the Firebase CLI. |
| use | Set active Firebase project, manage project aliases. |
| open | Quickly open a browser to relevant project resources. |
| init | Setup a new Firebase project in the current directory. This command will create a firebase.json configuration file in your current directory. |
| help | Display help information about the CLI or specific commands. |
| ext | Display information on how to use ext commands and extensions installed to your project. |
{
"mcpServers": {
"firebase": {
"command": "npx",
"args": [
"-y",
"firebase-tools@latest",
"mcp"
]
}
}
}Authenticate the Firebase CLI first and confirm the intended project directory and project ID.
Node.js/npm, Firebase CLI credentials, an intended project directory and a compatible stdio MCP client.
| Variable | Description | Required |
|---|---|---|
| FIREBASE_TOKEN | Credential the server authenticates with. | Yes |
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Enables AI-powered applications to monitor and interact with browser data via a Chrome extension and MCP.
Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript