fix(crashlytics-autotriage): pre-install Firebase CLI so the MCP server connects#89
Merged
Merged
Conversation
…er connects The MCP config ran `npx -y firebase-tools@latest mcp`, which cold-downloads the whole firebase-tools package at MCP-startup time — exceeding the SDK's connection window on a fresh runner, so the firebase server "failed to connect" and the crashlytics_* tools never loaded (issue #87, 3 runs). - Add a step to `npm install -g firebase-tools@latest` before the Claude step. - Point firebase-mcp.json at the pre-installed copy (drop `@latest` force-fetch) so the MCP `npx` resolves instantly instead of re-downloading. - Temporarily enable `show_full_output: true` so the MCP startup is visible if anything still fails (revert once green).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
After #88, the workflow runs once and the Crashlytics tool group is activated — but Claude still reported the Firebase MCP server "failed to connect" (3 runs on #87, no stacktrace).
The run log shows the action itself is healthy (OIDC ✓, Claude installed ✓, 12 turns, success) and that the MCP server startup happens inside the SDK's hidden output. The most likely cause: the MCP config launches
npx -y firebase-tools@latest mcp, which cold-downloads the entire firebase-tools package at MCP-startup time, exceeding the SDK's connection window on a fresh runner.Changes
firebase-toolsin a step before the Claude step, so the MCP server launches instantly..github/firebase-mcp.jsonnow callsfirebase-tools(no@latest), so npx resolves the pre-installed global copy instead of re-downloading.show_full_output: "true"on the action so the MCP startup logs are visible if anything still fails. Revert this once the run is green.Type of Change
How Has This Been Tested?
npx @latestcold-download is the prime suspect).crashlytics-auto; with full output on, confirm the firebase MCP server connects andcrashlytics_get_issuereturns data.Follow-up
show_full_outputagain.roles/firebasecrashlytics.viewer/ Crashlytics API not enabled) vs. another startup error.Checklist