USP

This is the official Firebase CLI and MCP Server, providing unparalleled, direct integration and comprehensive control over all Firebase services, ensuring robust and reliable AI-assisted development.

Use cases

• 01Deploying web apps and Cloud Functions
• 02Managing Firebase project configurations
• 03Local development and emulation of Firebase services
• 04Automating CI/CD pipelines for Firebase projects
• 05AI-assisted Firebase project management and development

Detected files (4)

• .agent/skills/resolve-docker-vulnerabilities/SKILL.mdskill
  Show content (2630 bytes)

  ---
  name: resolve-docker-vulnerabilities
  description: Skill to resolve Docker vulnerabilities for the firebase-cli image. Use this skill when you need to check for vulnerabilities in the firebase-cli Docker image and address them.
  ---
  
  # Resolve Docker Vulnerabilities
  
  This skill guides you through the process of listing images, checking for vulnerabilities, planning remediation, and verifying the fixes by publishing to a staging repository.
  
  ## Workflow
  
  ### 1. Publish to Staging
  
  Run the build on `fir-tools-builds` and publish to the `staging` repository in `firebase-cli` to see the baseline vulnerabilities after the build's own updates.
  
  ```bash
  ./scripts/publish/firebase-docker-image/run.sh --build-project fir-tools-builds --repo staging --target firebase-cli
  ```
  
  ### 2. Check Vulnerabilities
  
  Check the vulnerability reports for the image just pushed to staging. You will need to find the digest of the image first.
  
  ```bash
  gcloud artifacts docker images list us-docker.pkg.dev/firebase-cli/staging/firebase
  ```
  
  Then check vulnerabilities using the digest:
  
  ```bash
  gcloud artifacts vulnerabilities list us-docker.pkg.dev/firebase-cli/staging/firebase@sha256:<DIGEST>
  ```
  
  To investigate which layers and file paths are causing the vulnerabilities, run the command with `--format=json`:
  
  ```bash
  gcloud artifacts vulnerabilities list us-docker.pkg.dev/firebase-cli/staging/firebase@sha256:<DIGEST> --format=json
  ```
  
  Look for `fileLocation` and `layerDetails` in the output to understand if the vulnerability is in:
  - Project dependencies (e.g., under `/usr/local/node_packages/node_modules`). Recommend updating the package.json and running the build again. You can use overrides as needed here to upgrade transitive dependencies to non-breaking versions.
  - Global tools (e.g., under `/usr/local/lib/node_modules/npm`). Recommend waiting for upstream fixes (which will be pulled in as soon as they are available).
  - External binaries (e.g., emulator JARs under `/root/.cache/firebase/emulators`). Recommend raising these issues to the team owning the emulator.
  
  ### 3. Plan Remediation
  
  For each vulnerable package identified:
  - Determine if it can be updated in the Dockerfile.
  - Check if a fix is available.
  - Create a plan to address it (e.g., upgrading the base image, upgrading the specific package).
  
  ### 4. Present Plan to User
  
  Present the proposed plan to the user for approval before making changes.
  
  ### 5. Apply Fix and Re-Verify
  
  After making changes to the Dockerfile or related files, repeat Step 1 and Step 2 to publish a new staged image and verify that the vulnerabilities have been resolved.
  

• .agent/skills/update-pubsub-emulator/SKILL.mdskill
  Show content (2696 bytes)

  ---
  name: Update Pub/Sub Emulator
  description: How to update the Pub/Sub emulator
  ---
  
  # Update Pub/Sub Emulator
  
  1.  **Update Local Emulator**
      Run the following command to make sure you have the latest version of the pubsub emulator installed via gcloud:
      ```bash
      gcloud components update pubsub-emulator
      ```
  
  2.  **Locate Emulator Directory**
      The emulator represents a directory likely located at `<gcloud-install-path>/platform/pubsub-emulator`.
      You can find the exact path by running the emulator and checking the output, or by inspecting where `gcloud` is installed (e.g. `which gcloud` usually points to a bin directory, and the platform directory is a sibling of `bin`).
      Verify the version by running the emulator or checking the `VERSION` file if it exists.
  
  3.  **Package the Emulator**
      Zip the directory found in the previous step. Name it `pubsub-emulator-<version>.zip`.
      Ensure the zip structure is such that the top-level directory inside the zip is `pubsub-emulator`.
      *Note: The existing code expects the binary at `pubsub-emulator-<version>/pubsub-emulator/bin/cloud-pubsub-emulator` inside the cache, which usually means the zip contains a root folder `pubsub-emulator`.*
  
  4.  **Upload to Storage**
      Upload the zip file to the Firebase preview bucket:
      ```bash
      gcloud storage cp pubsub-emulator-<version>.zip gs://firebase-preview-drop/emulator/
      ```
      Make the file publicly readable if necessary (usually the bucket permissions handle this, or use `gcloud storage objects update ... --add-acl-grant=entity=allUsers,role=READER`).
  
      **Note:** For the version 0.8.27 update, this step was already done.
  
  5.  **Calculate Metadata**
      Calculate the file size in bytes, MD5 checksum, and SHA256 checksum of the zip file.
      ```bash
      # Size
      ls -l pubsub-emulator-<version>.zip
      
      # MD5 (macOS: `md5`, Linux: `md5sum`)
      md5 pubsub-emulator-<version>.zip
      
      # SHA256 (macOS: `shasum -a 256`, Linux: `sha256sum`)
      shasum -a 256 pubsub-emulator-<version>.zip
      ```
  
  6.  **Update Configuration**
      Edit `src/emulator/downloadableEmulatorInfo.json`:
      - Update `pubsub.version` to the new version.
      - Update `pubsub.expectedSize`.
      - Update `pubsub.expectedChecksum` (MD5).
      - Update `pubsub.expectedChecksumSHA256`.
      - Update `pubsub.remoteUrl` and `pubsub.downloadPathRelativeToCacheDir`.
  
  7.  **Verify**
      Run the emulators to ensure the new version is downloaded and starts correctly.
      ```bash
      firebase emulators:start --only pubsub
      ```
  
  8. **Add a Changelog Entry**
      Add a changelog entry to `CHANGELOG.md` like '- Updated Pub/Sub emulator to version <version>'
      

• src/mcp/server.jsonmcp_server
  Show content (664 bytes)

  {
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
    "name": "io.github.firebase/firebase-mcp",
    "description": "Gives AI development tools Firebase-specific capabilities and expertise.",
    "repository": {
      "url": "https://github.com/firebase/firebase-tools",
      "source": "github",
      "subfolder": "src/mcp"
    },
    "version": "0.3.0",
    "packages": [
      {
        "registryType": "npm",
        "identifier": "firebase-tools",
        "runtimeHint": "npx",
        "runtimeArguments": [{"type": "positional", "value": "mcp"}],
        "version": "14.27.0",
        "transport": {
          "type": "stdio"
        }
      }
    ]
  }
  

• .claude-plugin/marketplace.jsonmarketplace
  Show content (1470 bytes)

  {
    "name": "firebase",
    "owner": {
      "name": "Firebase",
      "email": "firebase-support@google.com"
    },
    "metadata": {
      "description": "Official Claude plugin for Firebase to help understand and manage your Firebase project, resources, and data",
      "version": "1.0.0"
    },
    "plugins": [
      {
        "name": "firebase",
        "description": "Claude plugin for Firebase that installs the Firebase MCP server and helps to manage Firebase projects, add backend services, add AI features, deploy & host apps, and more",
        "version": "1.0.0",
        "author": {
          "name": "Firebase",
          "url": "https://firebase.google.com/"
        },
        "homepage": "https://github.com/firebase/firebase-tools",
        "repository": "https://github.com/firebase/firebase-tools.git",
        "license": "MIT",
        "keywords": [
          "firebase",
          "mcp",
          "cloud",
          "firestore",
          "database",
          "hosting",
          "functions",
          "cli"
        ],
        "category": "development",
        "tags": ["firebase", "backend", "database", "cloud-services"],
        "mcpServers": {
          "firebase": {
            "description": "Firebase MCP server for understanding and managing your Firebase project, resources, and data",
            "command": "npx",
            "args": ["-y", "firebase-tools", "mcp", "--dir", "."],
            "env": {
              "IS_FIREBASE_MCP": "true"
            }
          }
        },
        "source": "./"
      }
    ]
  }
  

README

npm install -g firebase-tools

curl -sL firebase.tools | bash

$ firebase --project="foo" apps:list ANDROID

const client = require("firebase-tools");
client.apps
  .list("ANDROID", { project: "foo" })
  .then((data) => {
    // ...
  })
  .catch((err) => {
    // ...
  });

const client = require("firebase-tools");

// #1 - No arguments or options, defaults will be inferred
client.apps.list();

// #2 - Explicitly provide "" for all arguments and {} for options
client.apps.list("", {});