fix(crashlytics-autotriage): raise MCP_TIMEOUT so the Firebase MCP server connects#90
Merged
Merged
Conversation
…rver connects Root cause (anthropics/claude-code-action#1152): the Claude CLI's MCP startup timeout defaults to 30s. The firebase-tools MCP server exceeds that while booting + authenticating to Google, so it never connects and the crashlytics_* tools never surface (4 consecutive runs on #87). Pre-install alone didn't help because the bottleneck is boot/auth time, not download. - Raise MCP_TIMEOUT and MCP_TOOL_TIMEOUT to 120s via GITHUB_ENV before the action. - Drop the `_comment` key from .github/firebase-mcp.json in case the MCP config parser is strict (keep only the canonical {"mcpServers": {...}} shape).
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
Four consecutive runs on #87 failed with the Firebase MCP server never surfacing the
crashlytics_*tools. Root cause is a documented, fixed claude-code-action issue: #1152 — the Claude CLI's MCP startup timeout defaults to 30s, andfirebase-tools mcpexceeds it while booting + authenticating to Google, so the server is killed before it connects. Pre-installing the package (PR #89) didn't help because the bottleneck is boot/auth time, not download.Changes
MCP_TIMEOUT+MCP_TOOL_TIMEOUTto 120s viaGITHUB_ENVbefore the action (the propagation bug from #1152 is fixed in@v1)._commentkey from.github/firebase-mcp.json— keep the canonical{"mcpServers": {...}}shape only, in case the config parser is strict.show_full_output(still temporary).Type of Change
How Has This Been Tested?
show_full_output) + the upstream issue #1152, which matches the symptom exactly.crashlytics-auto; the firebase MCP server should now connect within the 120s window andcrashlytics_get_issueshould return data.If it still fails
show_full_outputis on, so the log will show the firebase server's actual error — at that point it's almost certainly auth: confirm the Firebase Crashlytics API is enabled onopenloop-8c266and thegh-crashlytics-readerSA hasroles/firebasecrashlytics.viewer. Also note: a re-test needs a real, current Crashlytics issue ID (a stale/closed ID returns no data even when the tools work).Checklist