# Install firebase-cli with Homebrew, winget, scoop

Firebase command-line tools. Version 15.22.4 via Homebrew; verified 2026-07-02.

## Install

```sh
sudo av install brew:firebase-cli
```

## Agent safety answer

firebase-cli deploys and manages Firebase projects and Google-backed resources.

- **Credential access:** Reads Firebase auth tokens, project config, service credentials, and environment variables.
- **Remote mutation:** Can deploy hosting, functions, rules, and project configuration.
- **Publish/artifact risk:** Publishes web assets, functions, and security rules.
- **Recommended control:** Gate deploy, functions, rules, login, and token operations.
- **Agent-use guidance:** Allow project inspection; require approval before deploys or rule changes.

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install firebase-cli
```

  Evidence: local Homebrew formula metadata

### Windows

- winget (92%):

```sh
winget install --id Google.FirebaseCLI -e
```

  Evidence: Windows Package Manager source index: Google.FirebaseCLI from https://cdn.winget.microsoft.com/cache/source.msix

- Scoop (92%):

```sh
scoop install main/firebase
```

  Evidence: Scoop official bucket manifest trees: bucket/firebase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:firebase-cli
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/firebase-cli>
- **Version:** 15.22.4
- **Source summary:** Firebase command-line tools
- **Homepage:** <https://firebase.google.com/docs/cli/>
- **Repository:** <https://github.com/firebase/firebase-tools>
- **Upstream docs:** <https://firebase.google.com/docs/cli>
- **License:** MIT
- **Source archive:** <https://registry.npmjs.org/firebase-tools/-/firebase-tools-15.22.4.tgz>
- **Last updated:** 2026-07-02T00:04:56Z
- **Generated:** 2026-07-09T07:20:21+00:00

## Executables

- firebase (cli)
- firebase (alias)

## Dependencies

- node

## Install behavior

- Post-install hook: not defined
- Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Freshness

- Page generated: 2026-07-09
- Package-manager version: 15.22.4
- Package-manager updated: 2026-07-02
- Local data: ok
- Upstream repository: https://firebase.google.com/docs/cli/
- info: Release/tag comparison is only available for GitHub repositories.
## Project history and usage

Firebase CLI is Google's command-line tool for testing, managing, and deploying Firebase projects. The `firebase` executable covers project setup, deployment, local emulation, Hosting, Realtime Database, Firestore, Cloud Functions, Authentication import/export, Extensions, App Distribution, Remote Config, and related Firebase operations.

### Project history

The firebase-tools GitHub repository was created in December 2013, during Firebase's early developer-platform era. The official README now describes it as both the Firebase Command Line Interface tools and the home of the official Firebase MCP Server.

Firebase CLI grew with the Firebase platform. Its README command list shows the tool expanding beyond Hosting deployment into project management, local emulators, App Distribution, Authentication, Realtime Database, Extensions, Firestore, Cloud Functions, Hosting, and Remote Config.

### Adoption history

The primary installation path is npm: `npm install -g firebase-tools` provides the globally accessible `firebase` command. The official README also documents a standalone binary installer, which matters for users who want a dependency-light CLI outside a Node development environment.

Firebase CLI adoption is tied to Firebase project workflows. Developers use it locally for `firebase init`, `firebase login`, emulator startup, and deployment; teams use it in CI for deploys, project listing, and authenticated service-account or token-based automation.

### How it is used

A typical workflow starts with `firebase login` and `firebase init`, which creates a `firebase.json` configuration file in the current project directory. Deployment commands then rely on that local project folder and configuration.

The CLI is also a local development surface. Commands such as `emulators:start`, `emulators:exec`, `serve`, and Functions shell support let developers test Firebase services before deploying to Google-hosted infrastructure.

### Why package nerds care

Firebase CLI is significant because it is a cloud product's operational surface packaged as a local developer tool. Installing one package gives a project its deploy command, emulator runner, auth setup, project selector, data import/export utility, and CI automation hook.

For package managers, it is also a Node-based CLI with standalone binary distribution, so it sits at the intersection of npm global installs, Homebrew-style desktop tooling, and vendor-managed cloud workflows.

### Timeline

- 2013: firebase-tools repository is created on GitHub.
- 2010s: npm global installation becomes the primary documented installation path for the `firebase` command.
- 2020s: CLI command surface includes local emulators, App Distribution, Extensions, Firestore, Functions, Hosting, and Remote Config workflows.
- 2026: Repository metadata and the README snapshot used for this enrichment show active maintenance and the addition of the official Firebase MCP Server in the same repository.

### Related projects

- Firebase Hosting, Cloud Functions for Firebase, Realtime Database, Cloud Firestore, Authentication, Remote Config, App Distribution, Extensions, and the Emulator Suite are first-party services managed by the CLI.
- Node.js and npm are the primary runtime and package-manager path documented for installing firebase-tools.
- Google Cloud service-account credentials and Application Default Credentials are supported authentication paths for automation.

### Sources

- <https://firebase.google.com/docs/cli>
- <https://github.com/firebase/firebase-tools>
- <https://raw.githubusercontent.com/firebase/firebase-tools/master/README.md>
- <https://api.github.com/repos/firebase/firebase-tools>


## Security Notes

No matching local secret-handling manifest was found for firebase-cli. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.config/configstore/firebase-tools.json

## Credential files

- Unix: ~/.config/configstore/firebase-tools.json
## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** firebase-cli
- **Version Scheme:** 0
- **Revision:** 0
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** stable

## Other Package-Manager Records

- winget - Google.FirebaseCLI: normalized package name match | Windows Package Manager source index: Google.FirebaseCLI from https://cdn.winget.microsoft.com/cache/source.msix
- Scoop - main/firebase: installed executable or alias match | Scoop official bucket manifest trees: bucket/firebase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Related links

- [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family.
- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [Documentation packages](https://www.automicvault.com/pkg/documentation-tools/) - Matched documentation, manual, or publishing metadata.
- [node](https://www.automicvault.com/pkg/brew/node/) - Runtime dependency declared by Homebrew.
- [aiven-client](https://www.automicvault.com/pkg/brew/aiven-client/) - Shares av.db curated category or tags: cli, cloud, cloud-infrastructure.
- [aliyun-cli](https://www.automicvault.com/pkg/brew/aliyun-cli/) - Shares av.db curated category or tags: cli, cloud, cloud-infrastructure.
- [linode-cli](https://www.automicvault.com/pkg/brew/linode-cli/) - Shares av.db curated category or tags: cli, cloud, cloud-infrastructure.
- [openstackclient](https://www.automicvault.com/pkg/brew/openstackclient/) - Shares av.db curated category or tags: cli, cloud, cloud-infrastructure.
- [railway](https://www.automicvault.com/pkg/brew/railway/) - Shares av.db curated category or tags: cli, cloud, cloud-infrastructure, deployment, hosting.
- [scalingo](https://www.automicvault.com/pkg/brew/scalingo/) - Shares av.db curated category or tags: cli, cloud, cloud-infrastructure, deployment, hosting.
- [scw](https://www.automicvault.com/pkg/brew/scw/) - Shares av.db curated category or tags: cli, cloud, cloud-infrastructure.
- [static-web-apps-cli](https://www.automicvault.com/pkg/brew/static-web-apps-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, deployment.

## Combined YAML source

View the package source record on GitHub. [combined/firebase-cli.yml](https://github.com/automic-vault/db/blob/main/combined/firebase-cli.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
- curated agent safety answer
