fix(crashlytics-autotriage): drop unsupported --project flag (the real MCP blocker)#91
Merged
Merged
Conversation
… config `firebase mcp` does not accept `--project` — passing it makes the server process crash on startup with `ERR_PARSE_ARGS_UNKNOWN_OPTION: Unknown option '--project'`. The MCP client then reports the server as `status: "pending"` forever (confirmed in run #18's SDK init), so the crashlytics_* tools never load. Verified locally: the exact command from the config throws this error. The project resolves from the tracked `.firebaserc` (default openloop-8c266) via `--dir .`, so `--project` was never needed.
…ectly Match the verified-working local config: drop `--project` (unsupported by `firebase mcp`, crashed the server) and invoke the `firebase` binary the Pre-install step puts on PATH, instead of `npx -y firebase-tools` (avoids npx resolution at MCP startup). Project resolves from .firebaserc via --dir.
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
Root cause, confirmed two ways. The Firebase MCP server in
.github/firebase-mcp.jsonwas launched with--project openloop-8c266, butfirebase mcpdoesn't accept that flag:(Reproduced locally by running the exact config command.) The server process crashes on startup, and the Claude SDK then reports the server as
status: "pending"indefinitely (seen in run #18's init block) — which is why thecrashlytics_*tools never surfaced across 6 runs.Fix: remove
--project. The project resolves from the tracked.firebaserc(defaultopenloop-8c266) via--dir ., so the flag was never needed.This is the one variable left after the earlier fixes (single trigger,
--only crashlytics, 120s timeout, pre-install, Crashlytics API enabled).Type of Change
How Has This Been Tested?
...mcp --dir . --project openloop-8c266 --only crashlytics) throwsUnknown option '--project'; removing it resolves the parse error.crashlytics-auto; the firebase server should reachconnectedandcrashlytics_get_issueshould return data.Checklist