firebase-tools 15.1.0 → 15.2.0

package/lib/mcp/errors.js

@@ -1,6 +1,9 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.mcpAuthError = exports.noProjectDirectory = exports.requireGeminiToS = exports.NO_PROJECT_ERROR = void 0;
+exports.NO_PROJECT_ERROR = void 0;
+exports.requireGeminiToS = requireGeminiToS;
+exports.noProjectDirectory = noProjectDirectory;
+exports.mcpAuthError = mcpAuthError;
 const util_1 = require("./util");
 const ensureApis_1 = require("../dataconnect/ensureApis");
 exports.NO_PROJECT_ERROR = (0, util_1.mcpError)("To proceed requires an active project. Use the `firebase_update_environment` tool to set a project ID", "PRECONDITION_FAILED");
@@ -15,11 +18,9 @@ async function requireGeminiToS(projectId) {
     }
     return undefined;
 }
-exports.requireGeminiToS = requireGeminiToS;
 function noProjectDirectory(projectRoot) {
     return (0, util_1.mcpError)(`The current project directory '${projectRoot || "<NO PROJECT DIRECTORY FOUND>"}' does not exist. Please use the 'update_firebase_environment' tool to target a different project directory.`);
 }
-exports.noProjectDirectory = noProjectDirectory;
 function mcpAuthError(skipADC) {
     if (skipADC) {
         return (0, util_1.mcpError)(`The user is not currently logged into the Firebase CLI, which is required to use this tool. Please run the 'firebase_login' tool to log in.`);
@@ -27,4 +28,3 @@ function mcpAuthError(skipADC) {
     return (0, util_1.mcpError)(`The user is not currently logged into the Firebase CLI, which is required to use this tool. Please run the 'firebase_login' tool to log in, or instruct the user to configure [Application Default Credentials][ADC] on their machine.
 [ADC]: https://cloud.google.com/docs/authentication/application-default-credentials`);
 }
-exports.mcpAuthError = mcpAuthError;

package/lib/mcp/index.js

@@ -39,15 +39,14 @@ const orderedLogLevels = [
 ];
 class FirebaseMcpServer {
     async trackGA4(event, params = {}) {
-        var _a, _b;
         if (!this.clientInfo)
             await (0, timeout_1.timeoutFallback)(this.ready(), null, 2000);
         const clientInfoParams = {
-            mcp_client_name: ((_a = this.clientInfo) === null || _a === void 0 ? void 0 : _a.name) || "<unknown-client>",
-            mcp_client_version: ((_b = this.clientInfo) === null || _b === void 0 ? void 0 : _b.version) || "<unknown-version>",
+            mcp_client_name: this.clientInfo?.name || "<unknown-client>",
+            mcp_client_version: this.clientInfo?.version || "<unknown-version>",
             gemini_cli_extension: process.env.IS_GEMINI_CLI_EXTENSION ? "true" : "false",
         };
-        return (0, track_1.trackGA4)(event, Object.assign(Object.assign({}, params), clientInfoParams));
+        return (0, track_1.trackGA4)(event, { ...params, ...clientInfoParams });
     }
     constructor(options) {
         this._ready = false;
@@ -72,17 +71,16 @@ class FirebaseMcpServer {
         this.server.setRequestHandler(types_js_1.ListResourcesRequestSchema, this.mcpListResources.bind(this));
         this.server.setRequestHandler(types_js_1.ReadResourceRequestSchema, this.mcpReadResource.bind(this));
         const onInitialized = () => {
-            var _a, _b;
             const clientInfo = this.server.getClientVersion();
             this.clientInfo = clientInfo;
-            if (clientInfo === null || clientInfo === void 0 ? void 0 : clientInfo.name) {
+            if (clientInfo?.name) {
                 void this.trackGA4("mcp_client_connected");
             }
-            if (!((_a = this.clientInfo) === null || _a === void 0 ? void 0 : _a.name))
+            if (!this.clientInfo?.name)
                 this.clientInfo = { name: "<unknown-client>" };
             this._ready = true;
             while (this._readyPromises.length) {
-                (_b = this._readyPromises.pop()) === null || _b === void 0 ? void 0 : _b.resolve();
+                this._readyPromises.pop()?.resolve();
             }
         };
         this.server.oninitialized = () => {
@@ -102,8 +100,7 @@ class FirebaseMcpServer {
         });
     }
     get clientName() {
-        var _a, _b;
-        return (_b = (_a = this.clientInfo) === null || _a === void 0 ? void 0 : _a.name) !== null && _b !== void 0 ? _b : ((0, env_1.isFirebaseStudio)() ? "Firebase Studio" : "<unknown-client>");
+        return this.clientInfo?.name ?? ((0, env_1.isFirebaseStudio)() ? "Firebase Studio" : "<unknown-client>");
     }
     get clientConfigKey() {
         return `mcp.clientConfigs.${this.clientName}:${this.startupRoot || process.cwd()}`;
@@ -113,7 +110,7 @@ class FirebaseMcpServer {
     }
     updateStoredClientConfig(update) {
         const config = configstore_1.configstore.get(this.clientConfigKey) || {};
-        const newConfig = Object.assign(Object.assign({}, config), update);
+        const newConfig = { ...config, ...update };
         configstore_1.configstore.set(this.clientConfigKey, newConfig);
         return newConfig;
     }
@@ -131,8 +128,7 @@ class FirebaseMcpServer {
         return this.cachedProjectDir;
     }
     async detectActiveFeatures() {
-        var _a;
-        if ((_a = this.detectedFeatures) === null || _a === void 0 ? void 0 : _a.length)
+        if (this.detectedFeatures?.length)
             return this.detectedFeatures;
         this.logger.debug("detecting active features of Firebase MCP server...");
         const projectId = (await this.getProjectId()) || "";
@@ -171,8 +167,7 @@ class FirebaseMcpServer {
         return `http://${host}:${emulatorInfo.port}`;
     }
     async getAvailableTools() {
-        var _a;
-        const features = ((_a = this.activeFeatures) === null || _a === void 0 ? void 0 : _a.length) ? this.activeFeatures : this.detectedFeatures;
+        const features = this.activeFeatures?.length ? this.activeFeatures : this.detectedFeatures;
         const projectId = (await this.getProjectId()) || "";
         const accountEmail = await this.getAuthenticatedUser();
         const isBillingEnabled = projectId ? await (0, cloudbilling_1.checkBillingEnabled)(projectId) : false;
@@ -184,8 +179,7 @@ class FirebaseMcpServer {
         return tools.find((t) => t.mcp.name === name) || null;
     }
     async getAvailablePrompts() {
-        var _a;
-        const features = ((_a = this.activeFeatures) === null || _a === void 0 ? void 0 : _a.length) ? this.activeFeatures : this.detectedFeatures;
+        const features = this.activeFeatures?.length ? this.activeFeatures : this.detectedFeatures;
         const projectId = (await this.getProjectId()) || "";
         const accountEmail = await this.getAuthenticatedUser();
         const isBillingEnabled = projectId ? await (0, cloudbilling_1.checkBillingEnabled)(projectId) : false;
@@ -216,7 +210,7 @@ class FirebaseMcpServer {
             this.logger.debug("calling requireAuth");
             const email = await (0, requireAuth_1.requireAuth)(await this.resolveOptions(), skipAutoAuth);
             this.logger.debug(`detected authenticated account: ${email || "<none>"}`);
-            return email !== null && email !== void 0 ? email : (skipAutoAuth ? null : "Application Default Credentials");
+            return email ?? (skipAutoAuth ? null : "Application Default Credentials");
         }
         catch (e) {
             this.logger.debug(`error in requireAuth: ${e}`);
@@ -261,29 +255,28 @@ class FirebaseMcpServer {
         };
     }
     async mcpCallTool(request) {
-        var _a, _b, _c, _d;
         await this.detectProjectRoot();
         const toolName = request.params.name;
         const toolArgs = request.params.arguments;
         const tool = await this.getTool(toolName);
         if (!tool)
             throw new Error(`Tool '${toolName}' could not be found.`);
-        if (!((_a = tool.mcp._meta) === null || _a === void 0 ? void 0 : _a.optionalProjectDir)) {
+        if (!tool.mcp._meta?.optionalProjectDir) {
             if (!this.cachedProjectDir || !(0, node_fs_1.existsSync)(this.cachedProjectDir)) {
                 return (0, errors_1.noProjectDirectory)(this.cachedProjectDir);
             }
         }
         let projectId = await this.getProjectId();
-        if (((_b = tool.mcp._meta) === null || _b === void 0 ? void 0 : _b.requiresProject) && !projectId) {
+        if (tool.mcp._meta?.requiresProject && !projectId) {
             return errors_1.NO_PROJECT_ERROR;
         }
         projectId = projectId || "";
         const skipAutoAuthForStudio = (0, env_1.isFirebaseStudio)();
         const accountEmail = await this.getAuthenticatedUser(skipAutoAuthForStudio);
-        if (((_c = tool.mcp._meta) === null || _c === void 0 ? void 0 : _c.requiresAuth) && !accountEmail) {
+        if (tool.mcp._meta?.requiresAuth && !accountEmail) {
             return (0, errors_1.mcpAuthError)(skipAutoAuthForStudio);
         }
-        if ((_d = tool.mcp._meta) === null || _d === void 0 ? void 0 : _d.requiresGemini) {
+        if (tool.mcp._meta?.requiresGemini) {
             const err = await (0, errors_1.requireGeminiToS)(projectId);
             if (err)
                 return err;

package/lib/mcp/prompt.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.prompt = void 0;
+exports.prompt = prompt;
 const availability_1 = require("./util/availability");
 function prompt(feature, options, fn, isAvailable) {
     const isAvailableFunc = isAvailable || (0, availability_1.getDefaultFeatureAvailabilityCheck)(feature);
@@ -10,4 +10,3 @@ function prompt(feature, options, fn, isAvailable) {
         isAvailable: isAvailableFunc,
     };
 }
-exports.prompt = prompt;

package/lib/mcp/prompts/core/consult.js

@@ -19,7 +19,6 @@ exports.consult = (0, prompt_1.prompt)("core", {
         title: "Consult Firebase Assistant",
     },
 }, async ({ prompt }, { config, projectId }) => {
-    var _a, _b, _c;
     const gifTosError = await (0, errors_1.requireGeminiToS)(projectId);
     if (gifTosError) {
         return [
@@ -27,7 +26,7 @@ exports.consult = (0, prompt_1.prompt)("core", {
                 role: "user",
                 content: {
                     type: "text",
-                    text: `Missing required conditions to run this prompt:\n\n${(_a = gifTosError.content[0]) === null || _a === void 0 ? void 0 : _a.text}\n\nPlease ask the user if they would like to accept these terms of service before proceeding. If they decline, inform them that this operation cannot continue without their acceptance.`,
+                    text: `Missing required conditions to run this prompt:\n\n${gifTosError.content[0]?.text}\n\nPlease ask the user if they would like to accept these terms of service before proceeding. If they decline, inform them that this operation cannot continue without their acceptance.`,
                 },
             },
         ];
@@ -39,7 +38,7 @@ App Platform(s): ${platforms.join(", ")}
 
 Question: ${prompt}`;
     const result = await (0, fdcExperience_1.chatWithFirebase)(gifPrompt, projectId);
-    const outputString = (_c = (_b = result.output.messages) === null || _b === void 0 ? void 0 : _b[0].content) !== null && _c !== void 0 ? _c : "";
+    const outputString = result.output.messages?.[0].content ?? "";
     return [
         {
             role: "user",

package/lib/mcp/prompts/crashlytics/connect.js

@@ -2,145 +2,38 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.connect = void 0;
 const prompt_1 = require("../../prompt");
+const crashlytics_connect_1 = require("../../resources/guides/crashlytics_connect");
 exports.connect = (0, prompt_1.prompt)("crashlytics", {
     name: "connect",
     omitPrefix: false,
-    description: "Access a Firebase application's Crashlytics data.",
+    description: "Use this command to access a Firebase application's Crashlytics data.",
     annotations: {
         title: "Access Crashlytics data",
     },
 }, async (unused, { accountEmail, firebaseCliCommand }) => {
+    const loggedInInstruction = `
+**The user is logged into Firebase as ${accountEmail || ""}.
+    `.trim();
+    const notLoggedInInstruction = `
+**Instruct the User to Log In**
+  The user is not logged in to Firebase. None of the Crashlytics tools will be able to authenticate until the user has logged in. Instruct the user to run \`${firebaseCliCommand} login\` before continuing, then use the \`firebase_get_environment\` tool to verify that the user is logged in.
+    `.trim();
     return [
         {
             role: "user",
             content: {
                 type: "text",
                 text: `
-You are going to help a developer prioritize and fix issues in their
-mobile application by accessing their Firebase Crashlytics data.
+You will assist developers in investigating and resolving mobile application issues by leveraging Firebase Crashlytics data. 
 
-Active user: ${accountEmail || "<NONE>"}
+### Required First Steps
 
-General rules:
-**ASK THE USER WHAT THEY WOULD LIKE TO DO BEFORE TAKING ACTION**
-**ASK ONLY ONE QUESTION OF THE USER AT A TIME**
-**MAKE SURE TO FOLLOW THE INSTRUCTIONS, ESPECIALLY WHERE THEY ASK YOU TO CHECK IN WITH THE USER**
-**ADHERE TO SUGGESTED FORMATTING**
+  ${accountEmail ? loggedInInstruction : notLoggedInInstruction}
 
-## Required first steps! Absolutely required! Incredibly important!
+**Obtain the Firebase App ID.** 
+    If an App ID is not readily available, consult this guide for selection: [Firebase App Id Guide](firebase://guides/app_id).
 
-  1. **Make sure the user is logged in. No Crashlytics tools will work if the user is not logged in.**
-    a. Use the \`firebase_get_environment\` tool to verify that the user is logged in.
-    b. If the Firebase 'Active user' is set to <NONE>, instruct the user to run \`${firebaseCliCommand} login\` 
-       before continuing. Ignore other fields that are set to <NONE>. We are just making sure the
-       user is logged in. 
-
-  2. **Get the app ID for the Firebase application.** 
-    a. **PRIORITIZE REMEMBERED APP ID ENTRIES** If an entry for this directory exists in the remembered app ids, use the remembered app id 
-       for this directory without presenting any additional options.
-       i. If there are multiple remembered app ids for this directory, ask the user to choose one by providing 
-          a numbered list of all the package names. Tell them that these values came from memories and how they can modify those values.
-    b. **IF THERE IS NO REMEMBERED ENTRY FOR THIS DIRECTORY** Use the app IDs from the \`firebase_get_environment\` tool. 
-       i. If you've already called this tool, use the previous response from context.
-       ii. If the 'Detected App IDs' is set to <NONE>, ask the user for the value they want to use.
-       iii. If there are multiple 'Detected App IDs', ask the user to choose one by providing 
-            a numbered list of all the package names and app ids.
-    c. **IF THERE IS A REMEMBERED VALUE BUT IT DOES NOT MATCH ANY DETECTED APP IDS** Ask if the user would like to replace the value with one of
-       the detected values.
-       i. **Description:** A valid app ID to remember contains four colon (":") delimited parts: a version 
-          number (typically "1"), a project number, a platform type ("android", "ios", or "web"), 
-          and a sequence of hexadecimal characters. 
-       ii. Replace the value for this directory with this valid app id, the android package name or ios bundle identifier, and the project directory.
-    c. **IF THERE IS NO REMEMBERED ENTRY FOR THIS DIRECTORY** Ask if the user would like to remember the app id selection
-       i. **Description:** A valid app ID to remember contains four colon (":") delimited parts: a version 
-          number (typically "1"), a project number, a platform type ("android", "ios", or "web"), 
-          and a sequence of hexadecimal characters. 
-       ii. Store the valid app id value, the android package name or ios bundle identifier, and the project directory.
-
-## Next steps
-
-Once you have confirmed that the user is logged in to Firebase, confirmed the
-id for the application that they want to access, and asked if they want to remember the app id for this directory, 
-ask the user what actions they would like to perform. 
-
-Use the following format to ask the user what actions they would like to perform:
-
-  1. Prioritize the most impactful stability issues
-  2. Diagnose and propose a fix for a crash
-
-Wait for their response before taking action.
-
-## Instructions for Using Crashlytics Data
-
-### How to prioritize issues
-
-Follow these steps to fetch issues and prioritize them.
-
-  1. Use the 'crashlytics_get_top_issues' tool to fetch up to 20 issues.
-    1a. Analyze the user's query and apply the appropriate filters.
-    1b. If the user asks for crashes, then set the issueErrorType filter to *FATAL*.
-    1c. If the user asks about a particular time range, then set both the intervalStartTime and intervalEndTime.
-  2. Use the 'crashlytics_get_top_versions' tool to fetch the top versions for this app.
-  3. If the user instructions include statements about prioritization, use those instructions.
-  4. If the user instructions do not include statements about prioritization, 
-  then prioritize the returned issues using the following criteria:
-    4a. The app versions for the issue include the most recent version of the app.
-    4b. The number of users experiencing the issue across variants
-    4c. The volume of crashes
-  5. Return the top 5 issues, with a brief description each in a numerical list with the following format: 
-    1. Issue <issue id>
-        * <the issue title>
-        * <the issue subtitle>
-        * **Description:** <a discription of the issue based on information from the tool response>
-        * **Rationale:** <the reason this issue was prioritized in the way it was>
-  6. Ask the user if they would like to diagnose and fix any of the issues presented
-
-### How to diagnose and fix issues
-
-Follow these steps to diagnose and fix issues.
-
-  1. Make sure you have a good understanding of the code structure and where different functionality exists
-  2. Use the 'crashlytics_get_issue' tool to get more context on the issue.
-  3. Use the 'crashlytics_batch_get_events' tool to get an example crash for this issue. Use the event names in the sampleEvent fields.
-    3a. If you need to read more events, use the 'crashlytics_list_events' tool.
-    3b. Apply the same filtering criteria that you used to find the issue, so that you find a appropriate events.
-  4. Read the files that exist in the stack trace of the issue to understand the crash deeply.
-  5. Determine possible root causes for the crash - no more than 5 potential root causes.
-  6. Critique your own determination, analyzing how plausible each scenario is given the crash details.
-  7. Choose the most likely root cause given your analysis.
-  8. Write out a plan for the most likely root cause using the following criteria:
-    8a. Write out a description of the issue and including
-        * A brief description of the cause of the issue
-        * A determination of your level of confidence in the cause of the issue using your analysis.
-        * A determination of which library is at fault, this codebase or a dependent library
-        * A determination for how complex the fix will be
-    8b. The plan should include relevant files to change
-    8c. The plan should include a test plan for how the user might verify the fix
-    8d. Use the following format for the plan:
-
-    ## Cause
-    <A description of the root cause leading to the issue>
-      - **Fault**: <a determination of whether this code base is at fault or a dependent library is at fault>
-      - **Complexity**: <one of "simple", "moderately simple", "moderately hard", "hard", "oof, I don't know where to start">
-    
-    ## Fix
-    <A description of the fix for this issue and a break down of the changes.>
-      1. <Step 1>
-      2. <Step 2>
-
-    ## Test
-    <A plan for how to test that the issue has been fixed and protect against regressions>
-      1. <Test case 1>
-      2. <Test case 2>
-
-    ## Other potential causes
-    1. <Another possible root cause>
-    2. <Another possible root cause>
-      
-  9. Present the plan to the user and get approval before making the change.
-  10. Only if they approve the plan, create a fix for the issue.
-    10a. Be mindful of API contracts and do not add fields to resources without a clear way to populate those fields
-    10b. If there is not enough information in the crash report to find a root cause, describe why you cannot fix the issue instead of making a guess.
+${crashlytics_connect_1.RESOURCE_CONTENT}
 `.trim(),
             },
         },

package/lib/mcp/prompts/dataconnect/schema.js

@@ -7,15 +7,15 @@ const types_1 = require("../../../dataconnect/types");
 const content_1 = require("../../util/dataconnect/content");
 const compile_1 = require("../../util/dataconnect/compile");
 function renderServices(fdcServices) {
-    var _a;
     if (!fdcServices.length)
         return "Data Connect Status: <UNCONFIGURED>";
     return `\n\n## Data Connect Schema
 
 The following is the up-to-date content of existing schema files (their paths are relative to the Data Connect source directory).
 
-${(_a = (0, types_1.mainSchema)(fdcServices[0].schemas)
-        .source.files) === null || _a === void 0 ? void 0 : _a.map((f) => `\`\`\`graphql ${f.path}\n${f.content}\n\`\`\``).join("\n\n")}`;
+${(0, types_1.mainSchema)(fdcServices[0].schemas)
+        .source.files?.map((f) => `\`\`\`graphql ${f.path}\n${f.content}\n\`\`\``)
+        .join("\n\n")}`;
 }
 function renderErrors(errors) {
     return `\n\n## Current Schema Build Errors\n\n${errors || "<NO ERRORS>"}`;

package/lib/mcp/prompts/index.js

@@ -1,6 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.markdownDocsOfPrompts = exports.availablePrompts = void 0;
+exports.availablePrompts = availablePrompts;
+exports.markdownDocsOfPrompts = markdownDocsOfPrompts;
 const core_1 = require("./core");
 const dataconnect_1 = require("./dataconnect");
 const crashlytics_1 = require("./crashlytics");
@@ -21,8 +22,8 @@ const prompts = {
 };
 function namespacePrompts(promptsToNamespace, feature) {
     return promptsToNamespace.map((p) => {
-        const newPrompt = Object.assign({}, p);
-        newPrompt.mcp = Object.assign({}, p.mcp);
+        const newPrompt = { ...p };
+        newPrompt.mcp = { ...p.mcp };
         if (newPrompt.mcp.omitPrefix) {
         }
         else if (feature === "core") {
@@ -31,7 +32,7 @@ function namespacePrompts(promptsToNamespace, feature) {
         else {
             newPrompt.mcp.name = `${feature}:${p.mcp.name}`;
         }
-        newPrompt.mcp._meta = Object.assign(Object.assign({}, p.mcp._meta), { feature });
+        newPrompt.mcp._meta = { ...p.mcp._meta, feature };
         return newPrompt;
     });
 }
@@ -45,10 +46,9 @@ async function availablePrompts(ctx, activeFeatures) {
     }));
     return allPrompts.filter((_, i) => availabilities[i]);
 }
-exports.availablePrompts = availablePrompts;
 function getAllPrompts(activeFeatures) {
     const promptDefs = [];
-    if (!(activeFeatures === null || activeFeatures === void 0 ? void 0 : activeFeatures.length)) {
+    if (!activeFeatures?.length) {
         activeFeatures = Object.keys(prompts);
     }
     if (!activeFeatures.includes("core")) {
@@ -60,15 +60,14 @@ function getAllPrompts(activeFeatures) {
     return promptDefs;
 }
 function markdownDocsOfPrompts() {
-    var _a, _b;
     const allPrompts = getAllPrompts();
     let doc = `
 | Prompt Name | Feature Group | Description |
 | ----------- | ------------- | ----------- |`;
     for (const prompt of allPrompts) {
-        const feature = ((_a = prompt.mcp._meta) === null || _a === void 0 ? void 0 : _a.feature) || "";
+        const feature = prompt.mcp._meta?.feature || "";
         let description = prompt.mcp.description || "";
-        if ((_b = prompt.mcp.arguments) === null || _b === void 0 ? void 0 : _b.length) {
+        if (prompt.mcp.arguments?.length) {
             const argsList = prompt.mcp.arguments.map((arg) => ` <br>&lt;${arg.name}&gt;${arg.required ? "" : " (optional)"}: ${arg.description || ""}`);
             description += ` <br><br>Arguments:${argsList.join("")}`;
         }
@@ -78,4 +77,3 @@ function markdownDocsOfPrompts() {
     }
     return doc;
 }
-exports.markdownDocsOfPrompts = markdownDocsOfPrompts;

package/lib/mcp/resource.js

@@ -1,27 +1,16 @@
 "use strict";
-var __rest = (this && this.__rest) || function (s, e) {
-    var t = {};
-    for (var p in s) if (Object.prototype.hasOwnProperty.call(s, p) && e.indexOf(p) < 0)
-        t[p] = s[p];
-    if (s != null && typeof Object.getOwnPropertySymbols === "function")
-        for (var i = 0, p = Object.getOwnPropertySymbols(s); i < p.length; i++) {
-            if (e.indexOf(p[i]) < 0 && Object.prototype.propertyIsEnumerable.call(s, p[i]))
-                t[p[i]] = s[p[i]];
-        }
-    return t;
-};
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.resourceTemplate = exports.resource = void 0;
+exports.resource = resource;
+exports.resourceTemplate = resourceTemplate;
 function resource(options, fnOrText) {
     const fn = typeof fnOrText === "string"
         ? async (uri) => ({ contents: [{ uri, text: fnOrText }] })
         : fnOrText;
     return { mcp: options, fn };
 }
-exports.resource = resource;
 function resourceTemplate(options, fnOrText) {
     let matchFn;
-    const { match } = options, mcp = __rest(options, ["match"]);
+    const { match, ...mcp } = options;
     if (match instanceof RegExp) {
         matchFn = (uri) => match.test(uri);
     }
@@ -36,4 +25,3 @@ function resourceTemplate(options, fnOrText) {
         : fnOrText;
     return { mcp, match: matchFn, fn };
 }
-exports.resourceTemplate = resourceTemplate;

package/lib/mcp/resources/guides/app_id.js

@@ -0,0 +1,39 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.app_id = exports.RESOURCE_CONTENT = void 0;
+const resource_1 = require("../../resource");
+exports.RESOURCE_CONTENT = `
+### Firebase App ID
+  The Firebase App ID is used to identify a mobile or web client application to Firebase back end services such as Crashlytics or Remote Config. Use the information below to find the developer's App ID.
+
+  1. **PRIORITIZE REMEMBERED APP ID ENTRIES** If an entry for this directory exists in the remembered app ids, use the remembered app id 
+       for this directory without presenting any additional options.
+       i. If there are multiple remembered app ids for this directory, ask the user to choose one by providing 
+          a numbered list of all the package names. Tell them that these values came from memories and how they can modify those values.
+  2. **IF THERE IS NO REMEMBERED ENTRY FOR THIS DIRECTORY** Use the app IDs from the \`firebase_get_environment\` tool. 
+       i. If you've already called this tool, use the previous response from context.
+       ii. If the 'Detected App IDs' is set to <NONE>, ask the user for the value they want to use.
+       iii. If there are multiple 'Detected App IDs', ask the user to choose one by providing 
+            a numbered list of all the package names and app ids.
+  3. **IF THERE IS A REMEMBERED VALUE BUT IT DOES NOT MATCH ANY DETECTED APP IDS** Ask if the user would like to replace the value with one of
+       the detected values.
+       i. **Description:** A valid app ID to remember contains four colon (":") delimited parts: a version 
+          number (typically "1"), a project number, a platform type ("android", "ios", or "web"), 
+          and a sequence of hexadecimal characters. 
+       ii. Replace the value for this directory with this valid app id, the android package name or ios bundle identifier, and the project directory.
+  4. **IF THERE IS NO REMEMBERED ENTRY FOR THIS DIRECTORY** Ask if the user would like to remember the app id selection
+       i. **Description:** A valid app ID to remember contains four colon (":") delimited parts: a version 
+          number (typically "1"), a project number, a platform type ("android", "ios", or "web"), 
+          and a sequence of hexadecimal characters. 
+       ii. Store the valid app id value, the android package name or ios bundle identifier, and the project directory.
+`.trim();
+exports.app_id = (0, resource_1.resource)({
+    uri: "firebase://guides/app_id",
+    name: "app_id_guide",
+    title: "Firebase App Id Guide",
+    description: "guides the coding agent through choosing a Firebase App ID in the current project",
+}, async (uri) => {
+    return {
+        contents: [{ uri, type: "text", text: exports.RESOURCE_CONTENT }],
+    };
+});

package/lib/mcp/resources/guides/crashlytics_connect.js

@@ -0,0 +1,51 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.crashlytics_connect = exports.RESOURCE_CONTENT = void 0;
+const resource_1 = require("../../resource");
+exports.RESOURCE_CONTENT = `
+### Instructions for Working with Firebase Crashlytics Tools
+
+When working interactively with a user, only ask the one question at a time. Do not proceed without user instructions. Upon receiving user instructions, refer to the relevant resources for guidance.
+
+Use the \`firebase_read_resources\` tool to access the following guides.
+
+  1. [Firebase App Id Guide](firebase://guides/app_id)
+     This guide provides crucial instructions for obtaining the application's App Id which is required for all API calls.
+
+  2. [Firebase Crashlytics Reports Guide](firebase://guides/crashlytics/reports)
+     This guide details how to request and use aggregated numerical data from Crashlytics. The agent should read this guide before requesting any report.
+    
+  3. [Firebase Crashlytics Issues Guide](firebase://guides/crashlytics/issues)
+     This guide details how to work with issues within Crashlytics. The agent should read this guide before prioritizing issues or presenting issue data to the user.
+
+  4. [Investigating Crashlytics Issues Guide](firebase://guides/crashlytics/investigations)
+     This guide provides instructions on investigating the root causes of crashes and exceptions reported in Crashlytics issues.
+
+### How to Check That You Are Connected
+
+Verify that you can read the app's Crashlytics data by getting the topVersions report. This report will tell you which app versions have the most events.
+  a. Read the firebase://guides/app_id if you need to find the app_id.
+  b. Call the \`crashlytics_get_report\` tool to read the \`topVersions\` report.
+  c. Help the user resolve any issues that arise when trying to connect.
+
+After confirming that you can access Crashlytics, ask the user what they would like help with. Your capabilities include:
+
+  - *Reading Crashlytics reports to prioritize or find important issues.*
+    Before fetching reports, read the critical instructions for the \`crashlytics_get_report\` tool in the [Firebase Crashlytics Reports Guide](firebase://guides/crashlytics/reports).
+
+  - *Investigating bug reports using Crashlytics event data.* 
+    Before attempting to investigate an individual issue, read the [Investigating Crashlytics Issues Guide](firebase://guides/crashlytics/investigations) to understand the best practices for debugging issues.
+
+  - *Proposing code changes to resolve identified bugs.*
+    
+`.trim();
+exports.crashlytics_connect = (0, resource_1.resource)({
+    uri: "firebase://guides/crashlytics/connect",
+    name: "crashlytics_connect_guide",
+    title: "Firebase Crashlytics Connect Guide",
+    description: "Guides the coding agent to connect to Firebase Crashlytics.",
+}, async (uri) => {
+    return {
+        contents: [{ uri, type: "text", text: exports.RESOURCE_CONTENT }],
+    };
+});

package/lib/mcp/resources/guides/crashlytics_investigations.js

@@ -0,0 +1,51 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.crashlytics_investigations = void 0;
+const resource_1 = require("../../resource");
+const RESOURCE_CONTENT = `
+### How to Diagnose and Fix Crashlytics Issues
+
+  Follow these steps to diagnose bugs and and propose fixes for issues.
+
+  1. Make sure you have a good understanding of the code structure and where different functionality exists.
+  2. Use the 'crashlytics_get_issue' tool to get more context on the issue.
+  3. Use the 'crashlytics_batch_get_events' tool to get an example crash for this issue. Use the event names in the sampleEvent fields.
+    3a. If you need to read more events, use the 'crashlytics_list_events' tool.
+    3b. Apply the same filtering criteria that you used to find the issue, so that you find a appropriate events.
+  4. Read the files that exist in the stack trace of the issue to understand the crash deeply.
+  5. Determine possible root causes for the crash - no more than 5 potential root causes.
+  6. Critique your own determination, analyzing how plausible each scenario is given the crash details.
+  7. Choose the most likely root cause given your analysis.
+  8. Create a plan for the most likely root cause using the following format for the plan:
+
+    ## Cause
+    <A description of the root cause leading to the issue>
+      - **Fault**: <a determination of whether this code base is at fault or a dependent library is at fault>
+      - **Complexity**: <one of "simple", "moderately simple", "moderately hard", "hard", "oof, I don't know where to start">
+    
+    ## Fix
+    <A description of the fix for this issue and a break down of the changes.>
+      1. <Step 1>
+      2. <Step 2>
+
+    ## Test
+    <A plan for how to test that the issue has been fixed and protect against regressions>
+      1. <Test case 1>
+      2. <Test case 2>
+
+    ## Other potential causes
+    1. <Another possible root cause>
+    2. <Another possible root cause>
+      
+  9. If there is not enough information in the crash report to find a root cause, describe why you cannot fix the issue instead of making a guess.
+`.trim();
+exports.crashlytics_investigations = (0, resource_1.resource)({
+    uri: "firebase://guides/crashlytics/investigations",
+    name: "crashlytics_investigations_guide",
+    title: "Firebase Crashlytics Investigations Guide",
+    description: "Guides the coding agent when investigating bugs reported in Crashlytics issues, including procedures for diagnosing and fixing crashes.",
+}, async (uri) => {
+    return {
+        contents: [{ uri, type: "text", text: RESOURCE_CONTENT }],
+    };
+});