Command-Line Interface for Firebase
Command-Line Interface for Firebase. Exposed over MCP by the firebase mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The Firebase Command Line Interface (CLI) Tools can be used to test, manage, and deploy your Firebase project from the command line. This repository is also the home of the official Firebase MCP Server. For more information, please see the Firebase MCP Server documentation.
Everything the assistant can do here goes through one of these:
login — Authenticate to your Firebase account. Requires access to a web browserlogout — Sign out of the Firebase CLIuse — Set active Firebase project, manage project aliasesopen — Quickly open a browser to relevant project resourcesinit — Setup a new Firebase project in the current directory. This command will create a firebase.json configuration file in your current directoryhelp — Display help information about the CLI or specific commandsext — Display information on how to use ext commands and extensions installed to your projectGeneral — The Firebase CLI can use one of four authentication methods listed in descending priority:firebase-tools on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: FIREBASE_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Firebase's toolset — login, logout, use and 5 more — is a fair guide to whether it matches your workflow. It is maintained by google-wombot; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| 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. |
| General | The Firebase CLI can use one of four authentication methods listed in descending priority: |
{
"mcpServers": {
"tools-1": {
"command": "npx",
"args": ["-y", "firebase-tools"],
"env": {
"FIREBASE_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| FIREBASE_TOKEN | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
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.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.