Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for firebase-mcp

Pod holds 24 of 98 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to firebase-mcp.

Most discussed

[MCP] Firebase Crashlytics calls lead to 404 errors

Summary

My colleagues and I have started utilizing the firebase MCP server to get summaries of crashlytics issues in our project.

I have followed the setup instructions for both Claude CLI and Cursor, but anytime the MCP server actually tries to fetch information from crashlytics, the tool receives a 404 error.

 fireba

[Read the thread](https://github.com/firebase/firebase-tools/issues/9876) · 2026-02-04 · closed · external user · 10 comments

### [MCP] Firebase MCP server hangs/crashes during tools/list initialization with large datasets

# [MCP] Firebase MCP server hangs/crashes during tools/list initialization with large datasets

## Description
The Firebase MCP server (`firebase-tools@latest mcp`) hangs, times out, or crashes with out-of-memory errors when Claude Code (or other MCP clients) attempts to list available tools via the `tools/list` MCP method. This issue occurs specifically when the Firebase project contains a large volume of Crashlytics data, making the MCP integration completely unusable for production applicatio

[Read the thread](https://github.com/firebase/firebase-tools/issues/9663) · 2025-12-19 · closed · external user · 10 comments

### Storage hangs without completing or errors when uploading or getting files in parallel

Hi, @abhis3.
I'm still experiencing this issue, although, I should add it doesn't happen all that consistantly.
Here are the following specs:
Device: `MacBook Pro (Retina, 13-inch, Mid 2014)`
OS: `macOS Big Sur, 11.7.8`
Firebase tools: `firebase-tools@12.4.5`

**Additional context**
The error doesn't just happen when uploading many files but also when downloading many of them in parallel, for instance, in context of a messaging application this would be when downloading in-chat media, li

[Read the thread](https://github.com/firebase/firebase-tools/issues/6194) · 2023-07-28 · closed · external user · 13 comments

### Calling functions.config() from JS broken on 9.19.0 when running functions emulator

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/bug_report.md
-->

<!--
Thank you for contributing to the Firebase community!

Think you found a bug?
=======================
Yeah, we're definitely not perfect! Please use this template and include a minimal repro when opening the issue. If you know how to solve the issue, please create a Pull Request, and we'd be happy to review it!

Have a feature request?
========================
Great, we love heari

[Read the thread](https://github.com/firebase/firebase-tools/issues/3793) · 2021-09-30 · closed · external user · 12 comments

### Non-interactive version of firebase init

<!-- DO NOT DELETE
validate_template=false
template_path=.github/ISSUE_TEMPLATE/feature_request.md
-->

Right now there is no way to do `firebase init --project=foo {product}` within a script.  Since hand-crafting a `firebase.json` file is a lot of guesswork it could be cool to make `firebase init --noninteractive` accept all defaults.

@mbleigh is that possible or reasonable?

[Read the thread](https://github.com/firebase/firebase-tools/issues/2333) · 2020-06-05 · open · outside contributor · 15 comments

### Callable function in emulator returns 'unauthenticated' when passing in mock auth via firebase/testing lib

<!-- DO NOT DELETE 
validate_template=true
template_path=.github/ISSUE_TEMPLATE/bug_report.md
-->

<!--
Thank you for contributing to the Firebase community!

Think you found a bug?
=======================
Yeah, we're definitely not perfect! Please use this template and include a minimal repro when opening the issue. If you know how to solve the issue, please create a Pull Request, and we'd be happy to review it!

Have a feature request?
========================
Great, we love hear

[Read the thread](https://github.com/firebase/firebase-tools/issues/1475) · 2019-07-06 · closed · external user · 18 comments

### "Error: The incoming JSON object does not contain a client_email field" after upgrading to 7.0.2

<!-- DO NOT DELETE 
validate_template=true
template_path=.github/ISSUE_TEMPLATE/bug_report.md
-->

<!--
Thank you for contributing to the Firebase community!

Think you found a bug?
=======================
Yeah, we're definitely not perfect! Please use this template and include a minimal repro when opening the issue. If you know how to solve the issue, please create a Pull Request, and we'd be happy to review it!

Have a feature request?
========================
Great, we love hear

[Read the thread](https://github.com/firebase/firebase-tools/issues/1451) · 2019-06-28 · closed · external user · 61 comments

### Pre-serve hooks similar to pre-deploy

<!--

Thank you for contributing to the Firebase community! Please follow this template, issues that do not follow it will be closed.

Have a usage question?
=======================
We get lots of those and we love helping you, but GitHub is not the best place for them and they
will be closed. Go through the guide first: https://firebase.google.com/docs/cli/

If you are still unable to resolve the issue, try asking through our official support channels:

https://firebase.google.com/su

[Read the thread](https://github.com/firebase/firebase-tools/issues/701) · 2018-03-12 · closed · outside contributor · 15 comments

## Most recent

### [MCP] Enforce Session ID output for AI Agents during firebase_login for security verification

<!-- DO NOT DELETE
validate_template=false
template_path=.github/ISSUE_TEMPLATE/feature_request.md
-->

<!--
Thank you for contributing to the Firebase community!

Have a feature request?
========================
Great, we love hearing how we can improve our products! However, GitHub is not the place to submit them. Please submit your feature requests to:
https://firebase.google.com/support/contact/bugs-features/

**Think you found a bug?** Please do not use this template - use the `🐛 Bug report

[Read the thread](https://github.com/firebase/firebase-tools/issues/10942) · 2026-08-15 · closed · external user · 0 comments

### MCP firebase_login builds a malformed login URL (stray "}" in studio_prototyper param) → "Unable to verify client"

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/bug_report.md
-->

### Version
  firebase-tools 15.25.1 (MCP server 0.3.0), Windows 11, Node v24.16.0

  ### Bug
  `loginPrototyper()` in src/auth.ts builds the login URL with a stray closing
  brace inside the template literal, so the emitted URL ends with
  `studio_prototyper=true}` instead of `studio_prototyper=true`:

  https://github.com/firebase/firebase-tools/blob/master/src/auth.ts#L450

  ```js
  const loginU

[Read the thread](https://github.com/firebase/firebase-tools/issues/10888) · 2026-08-04 · closed · external user · 1 comment

### [MCP]

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

<!-- what is your bug / feature request / feedback? -->

## Bug Info <!-- please fill this out if you have a bug -->

- **Affected Tool(s):** <!-- Which specific tool(s) were you using when you encountered the issue? -->
- **MCP Client:** <!-- e.g. "Cursor v0.50.0" -->
- **Operating System:** <!-- e.g. "Windows 11" or "macOS Sequoia" -->

### Steps to Reproduce

<!-- write a detailed descriptio

[Read the thread](https://github.com/firebase/firebase-tools/issues/10865) · 2026-07-30 · closed · external user · 1 comment

### [MCP]

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

<!-- what is your bug / feature request / feedback? -->

## Bug Info <!-- please fill this out if you have a bug -->

- **Affected Tool(s):** <!-- Which specific tool(s) were you using when you encountered the issue? -->
- **MCP Client:** <!-- e.g. "Cursor v0.50.0" -->
- **Operating System:** <!-- e.g. "Windows 11" or "macOS Sequoia" -->

### Steps to Reproduce

<!-- write a detailed descriptio

[Read the thread](https://github.com/firebase/firebase-tools/issues/10718) · 2026-06-25 · closed · external user · 1 comment

### [MCP]

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

<!-- what is your bug / feature request / feedback? -->

## Bug Info <!-- please fill this out if you have a bug -->

- **Affected Tool(s):** <!-- Which specific tool(s) were you using when you encountered the issue? -->
- **MCP Client:** <!-- e.g. "Cursor v0.50.0" -->
- **Operating System:** <!-- e.g. "Windows 11" or "macOS Sequoia" -->

### Steps to Reproduce

<!-- write a detailed descriptio

[Read the thread](https://github.com/firebase/firebase-tools/issues/10707) · 2026-06-24 · closed · external user · 1 comment

### [MCP] Firebase MCP reconnect succeeds but tool fetching fails with FetchError: Premature close

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

After selecting Reconnect for `plugin:firebase:firebase` in the `/mcp` menu, Claude Code reports a successful reconnect, but then fails to fetch tools from the Firebase MCP endpoint with a `FetchError: Invalid response body while trying to fetch https://developerknowledge.googleapis.com/mcp: Premature close`.

## Bug Info

* **Affected Tool(s):** Firebase MCP (`plugin:firebase:firebase`)
* **MC

[Read the thread](https://github.com/firebase/firebase-tools/issues/10699) · 2026-06-23 · closed · external user · 3 comments

### [Apphosting] Support revoke Secret Manager secret CLI command

<!-- DO NOT DELETE
validate_template=false
template_path=.github/ISSUE_TEMPLATE/feature_request.md
-->

### Description
Currently, the Firebase CLI provides the `firebase apphosting:secrets:grantaccess` command to easily grant the App Hosting service account access to a specific Secret Manager secret. However, there is no symmetrical command to revoke this access when a secret is no longer needed or removed from `apphosting.yaml`.

To follow the Principle of Least Privilege (PoLP), users should 

[Read the thread](https://github.com/firebase/firebase-tools/issues/10645) · 2026-06-13 · closed · outside contributor · 2 comments

### [MCP]

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

<!-- what is your bug / feature request / feedback? -->

## Bug Info <!-- please fill this out if you have a bug -->

- **Affected Tool(s):** <!-- Which specific tool(s) were you using when you encountered the issue? -->
- **MCP Client:** <!-- e.g. "Cursor v0.50.0" -->
- **Operating System:** <!-- e.g. "Windows 11" or "macOS Sequoia" -->

### Steps to Reproduce

<!-- write a detailed descriptio

[Read the thread](https://github.com/firebase/firebase-tools/issues/10644) · 2026-06-13 · closed · external user · 1 comment

### Firebase Extension stuck in DEPLOYING forever — cannot delete (FAILED_PRECONDITION)

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/bug_report.md
-->

<!--
Thank you for contributing to the Firebase community!

Think you found a bug?
=======================
Yeah, we're definitely not perfect! Please use this template and include a minimal repro when opening the issue. If you know how to solve the issue, please create a Pull Request, and we'd be happy to review it!

Have a feature request?
========================
Great, we love hearing how we can 

[Read the thread](https://github.com/firebase/firebase-tools/issues/10581) · 2026-05-31 · closed · external user · 7 comments

### [MCP]firebase login --reauth when claude call MCP tools

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

├── firebase-tools@15.18.0
├── firebase@12.13.0

<!-- what is your bug / feature request / feedback? -->
     Available Project Aliases (format: '[alias]: [projectId]'): <NONE>

     No firebase.json file was found.

     If this project does not use Firebase services that require a firebase.json file, no action is necessary.

     If this project uses Firebase services that require a firebas

[Read the thread](https://github.com/firebase/firebase-tools/issues/10525) · 2026-05-18 · open · external user · 4 comments

### [MCP] Crashlytics tools are not available for Unity projects

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

<!-- what is your bug / feature request / feedback? -->
When working in Cursor, there are no available Crashlytics MCP tools.
According to the docs , it's a known issue -
https://firebase.google.com/docs/crashlytics/ai-assistance-mcp#troubleshooting-faq

But still, i believe it should be tracked and handled soon.

## Bug Info <!-- please fill this out if you have a bug -->

- **Affected Tool(s)

[Read the thread](https://github.com/firebase/firebase-tools/issues/10482) · 2026-05-10 · open · external user · 0 comments

### MCP: structuredContent returns array instead of object for list-type tools (breaks MCP clients)

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

Several Firebase MCP tools return a bare JSON array in the `structuredContent`
field of the tool response. The MCP spec requires `structuredContent` to be a
JSON **object** (record), not an array. MCP clients that validate the response
schema reject these tools with:

> MCP error -32602: Invalid tools/call result: expected record, received array (path: structuredContent)

## Bug Info

- **Affec

[Read the thread](https://github.com/firebase/firebase-tools/issues/10437) · 2026-04-30 · closed · external user · 1 comment

### [MCP] Crashlytics tools return 404 "Method not found" with service account credentials (ADC), but work with firebase login:ci token

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

When using Workload Identity Federation (WIF) authentication in a GitHub Actions CI environment, calling the Firebase MCP `crashlytics_get_report` tool results in an **"HTTP Error: 404, Method not found"** for all report types. 

Interestingly, the same environment works perfectly when using a token obtained via `firebase login:ci`. While `firebase_update_environment` succeeds, any subsequent r

[Read the thread](https://github.com/firebase/firebase-tools/issues/10310) · 2026-04-10 · closed · external user · 2 comments

### [MCP]

<!-- DO NOT DELETE
validate_template=true
template_path=.github/ISSUE_TEMPLATE/mcp.md
-->

## Summary

<!-- what is your bug / feature request / feedback? -->

## Bug Info <!-- please fill this out if you have a bug -->

- **Affected Tool(s):** <!-- Which specific tool(s) were you using when you encountered the issue? -->
- **MCP Client:** <!-- e.g. "Cursor v0.50.0" -->
- **Operating System:** <!-- e.g. "Windows 11" or "macOS Sequoia" -->

### Steps to Reproduce

<!-- write a detailed descriptio

[Read the thread](https://github.com/firebase/firebase-tools/issues/10277) · 2026-04-07 · closed · external user · 1 comment

### [MCP] Crashlytics auto-detection can fail in Flutter projects and hide Crashlytics tools

## Summary

I ran into a Firebase MCP discovery problem in a Flutter app that already has Crashlytics configured.

When the server starts in its default auto-detect mode, Crashlytics tools are not exposed. After digging into it locally, the reason appears to be an internal exception during feature detection, as opposed to something missing in my Crashlytics config.

The same install exposes the Crashlytics tools immediately if I force features with `--only`, so this looks like an MCP auto-detect

[Read the thread](https://github.com/firebase/firebase-tools/issues/10211) · 2026-03-28 · closed · outside contributor · 4 comments

### Accessing internal Firebase Tools APIs on a self-hosted MCP

Hello Firebase team,

We want to use MCP within our company, but due to security concerns, we do not want all tools to be exposed. As a workaround, we cloned your project from GitHub and tried to make only the Crashlytics tool visible.

However, by doing this, we were unable to access the internal APIs used within MCP. Is there any support or recommended approach to bypass these technical limitations?

For reference, we implemented a similar setup with Figma MCP and were able to run it smoothly 

[Read the thread](https://github.com/firebase/firebase-tools/issues/10205) · 2026-03-27 · open · external user · 2 comments

The remaining reports are on [the project's issue tracker](https://github.com/firebase/firebase-tools/issues).