firebase-tools 15.0.0 → 15.2.0

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 }],
+    };
+});

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

@@ -0,0 +1,42 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.crashlytics_issues = void 0;
+const resource_1 = require("../../resource");
+const RESOURCE_CONTENT = `
+### How to Display Issues
+
+When displaying a list of issues, use the following format:
+
+  1. Issue <full issue id>
+    * <the issue title>
+    * <the issue subtitle>
+    * **Description:** <a discription of the issue based on information from the tool response>
+
+### How to Prioritize Crashlytics Issues
+
+Follow these steps to fetch issues and prioritize them.
+
+  1. Use the 'crashlytics_get_report' tool to fetch the 'topIssues' report.
+    1a. Analyze the user's query and apply the appropriate filters. Use the information in the [Firebase Crashlytics Reports Guide](firebase://guides/crashlytics/reports) to further construct appropriate report requests.
+    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_report' tool to fetch the 'topVersions' 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 recommended format.
+    5a. Describe the rationale for the prioritization order.
+  6. Ask the user if they would like to diagnose and fix any of the issues presented before taking any action.
+`.trim();
+exports.crashlytics_issues = (0, resource_1.resource)({
+    uri: "firebase://guides/crashlytics/issues",
+    name: "crashlytics_issues_guide",
+    title: "Firebase Crashlytics Issues Guide",
+    description: "Guides the coding agent when working with Crashlytics issues, including prioritization rules and procedures for diagnosing and fixing crashes. ",
+}, async (uri) => {
+    return {
+        contents: [{ uri, type: "text", text: RESOURCE_CONTENT }],
+    };
+});

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

@@ -0,0 +1,112 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.crashlytics_reports = void 0;
+const resource_1 = require("../../resource");
+const RESOURCE_CONTENT = `
+### Crashlytics Reports
+
+Aggregate metrics for all of the events sent to Crashlytics are available as reports. 
+The following reports are available for all Crashlytics applications.
+
+  - name: "topIssues"
+    display_name: "Top Issues"
+    usage: |
+      Counts events and distinct impacted users, grouped by issue.
+      Issue groups are sorted by event count, in descending order.
+
+  - name: "topVariants"
+    display_name: "Top Variants"
+    usage: |
+      Counts events and distinct impacted users, grouped by issue variant.
+      Issue variant groups are sorted by event count, in descending order.
+    required: |
+      An issue filter including an issue id is required.
+  
+  - name: "topVersions"
+    display_name: "Top Versions"
+    usage: |
+      Counts events, grouped by app version.
+      Versions are sorted by event count, in descending order.
+
+  - name: "topOperatingSystems"
+    display_name: "Top Operating Systems"
+    usage: |
+      Counts events, grouped by device operating systems and their versions.
+      Operating systems are sorted by event count, in descending order.
+
+Mobile apps have one of the following reports available, depending on the platform. 
+
+  - name: "topAndroidDevices"
+    display_name: "Top Android Devices"
+    usage: |
+      Counts events, grouped by android device.
+      Devices are sorted by event count, in descending order.
+
+  - name: "topAppleDevices"
+    display_name: "Top Apple Devices"
+    usage:
+      Counts events, grouped by operating system and Apple device.
+      Devices are sorted by event count, in descending order.
+
+Report responses contain the following metrics:
+
+  - eventsCount: the number of events matching
+  - impactedUsers: the number of distinct end users in all the matching events
+
+Report responses are always grouped by one of the following dimensions:
+
+  - app version
+  - issue
+  - variant
+  - operating system
+  - mobile device type
+
+### Filters
+
+When setting report filters adhere to the following instructions.
+
+  * Issue Filtering:
+    * Use the \`issueErrorTypes\` field to focus on events of different fatalities: 
+      * FATAL: native crashes, which caused the app to exit.
+      * NON_FATAL: uncaught or manually reported exceptions, which did not crash the app.
+      * ANR: "app not responding" events, only relevant on Android platforms.
+
+  * Time Interval:
+    * For a custom time range, you must specify both intervalStartTime and intervalEndTime.
+    * The specified time range must be within the last 90 days.
+    * If you don't provide a time range, it will default to the last 7 days.
+
+  * Display Names (for app versions, operating systems, and devices):
+    * The values for versionDisplayNames,operatingSystemDisplayNames, and deviceDisplayNames must be obtained from the displayName field of a previous API response.
+    * These display names must match specific formats:
+      * Device: 'manufacturer (device)'
+      * Operating System: 'os (version)'
+      * App Version: 'version (build)'
+
+### Useful Reports
+
+  * The "topIssues" report is comparable to the default view on the Crashlytics web dashboard. Use this report first to prioritize which issues are impacting the most users. Apply appropriate filters for time interval based on the user's query.
+
+  * Report responses grouped by issue will include a sample event URI. Use the "crashlytics_batch_get_events" tool to fetch the complete record for any sample event.
+  
+  * When investigating an issue, use the appropriate top devices and top operating systems reports to understand what systems are impacted by the problem. Pass the "issueId" in the filter to narrow any report to a specific issue.
+
+### How to Display Issues
+
+When displaying a list of issues, use the following format:
+
+  1. Issue <full issue id>
+    * <the issue title>
+    * <the issue subtitle>
+    * **Description:** <a discription of the issue based on information from the tool response>
+`.trim();
+exports.crashlytics_reports = (0, resource_1.resource)({
+    uri: "firebase://guides/crashlytics/reports",
+    name: "crashlytics_reports_guide",
+    title: "Firebase Crashlytics Reports Guide",
+    description: "Guides the coding agent through requesting Crashlytics reports, including setting appropriate filters and how to understand the metrics. The agent should read this guide before requesting any report.",
+}, async (uri) => {
+    return {
+        contents: [{ uri, type: "text", text: RESOURCE_CONTENT }],
+    };
+});

package/lib/mcp/resources/index.js

@@ -1,15 +1,25 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.markdownDocsOfResources = exports.resolveResource = exports.resourceTemplates = exports.resources = void 0;
+exports.resourceTemplates = exports.resources = void 0;
+exports.resolveResource = resolveResource;
+exports.markdownDocsOfResources = markdownDocsOfResources;
 const docs_1 = require("./docs");
+const app_id_1 = require("./guides/app_id");
 const init_ai_1 = require("./guides/init_ai");
 const init_auth_1 = require("./guides/init_auth");
 const init_backend_1 = require("./guides/init_backend");
 const init_firestore_1 = require("./guides/init_firestore");
 const init_firestore_rules_1 = require("./guides/init_firestore_rules");
 const init_hosting_1 = require("./guides/init_hosting");
+const crashlytics_investigations_1 = require("./guides/crashlytics_investigations");
 const track_1 = require("../../track");
+const crashlytics_issues_1 = require("./guides/crashlytics_issues");
+const crashlytics_reports_1 = require("./guides/crashlytics_reports");
 exports.resources = [
+    app_id_1.app_id,
+    crashlytics_investigations_1.crashlytics_investigations,
+    crashlytics_issues_1.crashlytics_issues,
+    crashlytics_reports_1.crashlytics_reports,
     init_backend_1.init_backend,
     init_ai_1.init_ai,
     init_firestore_1.init_firestore,
@@ -37,7 +47,6 @@ async function resolveResource(uri, ctx, track = true) {
         void (0, track_1.trackGA4)("mcp_read_resource", { resource_name: uri, not_found: "true" });
     return null;
 }
-exports.resolveResource = resolveResource;
 function markdownDocsOfResources() {
     const allResources = [...exports.resources, ...exports.resourceTemplates];
     const headings = `
@@ -52,4 +61,3 @@ function markdownDocsOfResources() {
     });
     return headings + resourceRows.join("");
 }
-exports.markdownDocsOfResources = markdownDocsOfResources;

package/lib/mcp/tool.js

@@ -1,27 +1,15 @@
 "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.tool = void 0;
+exports.tool = tool;
 const zod_to_json_schema_1 = require("zod-to-json-schema");
 const util_1 = require("./util");
 const availability_1 = require("./util/availability");
 function tool(feature, options, fn) {
-    const { isAvailable } = options, mcpOptions = __rest(options, ["isAvailable"]);
+    const { isAvailable, ...mcpOptions } = options;
     const isAvailableFunc = isAvailable || (0, availability_1.getDefaultFeatureAvailabilityCheck)(feature);
     return {
-        mcp: Object.assign(Object.assign({}, mcpOptions), { inputSchema: (0, util_1.cleanSchema)((0, zod_to_json_schema_1.zodToJsonSchema)(options.inputSchema)) }),
+        mcp: { ...mcpOptions, inputSchema: (0, util_1.cleanSchema)((0, zod_to_json_schema_1.zodToJsonSchema)(options.inputSchema)) },
         fn,
         isAvailable: isAvailableFunc,
     };
 }
-exports.tool = tool;

package/lib/mcp/tools/apphosting/fetch_logs.js

@@ -31,20 +31,19 @@ exports.fetch_logs = (0, tool_1.tool)("apphosting", {
         requiresProject: true,
     },
 }, async ({ buildLogs, backendId, location } = {}, { projectId }) => {
-    var _a, _b;
     location || (location = "");
     if (!backendId) {
         return (0, util_1.toContent)(`backendId must be specified.`);
     }
     const backend = await (0, apphosting_1.getBackend)(projectId, location, backendId);
     const traffic = await (0, apphosting_1.getTraffic)(projectId, location, backendId);
-    const data = Object.assign(Object.assign({}, backend), { traffic });
+    const data = { ...backend, traffic };
     if (buildLogs) {
         const builds = await (0, apphosting_1.listBuilds)(projectId, location, backendId);
         builds.builds.sort((a, b) => new Date(a.createTime).getTime() - new Date(b.createTime).getTime());
         const build = (0, utils_1.last)(builds.builds);
         const r = new RegExp(`region=${location}/([0-9a-f-]+)?`);
-        const match = r.exec((_a = build.buildLogsUri) !== null && _a !== void 0 ? _a : "");
+        const match = r.exec(build.buildLogsUri ?? "");
         if (!match) {
             throw new error_1.FirebaseError("Unable to determine the build ID.");
         }
@@ -59,7 +58,7 @@ exports.fetch_logs = (0, tool_1.tool)("apphosting", {
         }
         return (0, util_1.toContent)(entries);
     }
-    const serviceName = (_b = (0, utils_1.last)(data.managedResources)) === null || _b === void 0 ? void 0 : _b.runService.service;
+    const serviceName = (0, utils_1.last)(data.managedResources)?.runService.service;
     if (!serviceName) {
         throw new error_1.FirebaseError("Unable to get service name from managedResources.");
     }

package/lib/mcp/tools/apphosting/list_backends.js

@@ -44,7 +44,7 @@ exports.list_backends = (0, tool_1.tool)("apphosting", {
             (0, apphosting_1.getTraffic)(projectId, location, id),
             (0, apphosting_1.listDomains)(projectId, location, id),
         ]);
-        return Object.assign(Object.assign({}, backend), { traffic: traffic, domains: domains });
+        return { ...backend, traffic: traffic, domains: domains };
     });
     const data = await Promise.all(promises);
     return (0, util_1.toContent)(data);

package/lib/mcp/tools/auth/get_users.js

@@ -1,15 +1,4 @@
 "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.get_users = void 0;
 const zod_1 = require("zod");
@@ -42,23 +31,23 @@ exports.get_users = (0, tool_1.tool)("auth", {
     },
 }, async ({ uids, emails, phone_numbers, limit }, { projectId }) => {
     const prune = (user) => {
-        const { passwordHash, salt } = user, prunedUser = __rest(user, ["passwordHash", "salt"]);
+        const { passwordHash, salt, ...prunedUser } = user;
         return prunedUser;
     };
     let users = [];
-    if (uids === null || uids === void 0 ? void 0 : uids.length) {
+    if (uids?.length) {
         const promises = uids.map((uid) => (0, auth_1.findUser)(projectId, undefined, undefined, uid).catch(() => null));
         users.push(...(await Promise.all(promises)).filter((u) => !!u));
     }
-    if (emails === null || emails === void 0 ? void 0 : emails.length) {
+    if (emails?.length) {
         const promises = emails.map((email) => (0, auth_1.findUser)(projectId, email, undefined, undefined).catch(() => null));
         users.push(...(await Promise.all(promises)).filter((u) => !!u));
     }
-    if (phone_numbers === null || phone_numbers === void 0 ? void 0 : phone_numbers.length) {
+    if (phone_numbers?.length) {
         const promises = phone_numbers.map((phone) => (0, auth_1.findUser)(projectId, undefined, phone, undefined).catch(() => null));
         users.push(...(await Promise.all(promises)).filter((u) => !!u));
     }
-    if (!(uids === null || uids === void 0 ? void 0 : uids.length) && !(emails === null || emails === void 0 ? void 0 : emails.length) && !(phone_numbers === null || phone_numbers === void 0 ? void 0 : phone_numbers.length)) {
+    if (!uids?.length && !emails?.length && !phone_numbers?.length) {
         users = await (0, auth_1.listUsers)(projectId, limit || 100);
     }
     return (0, util_1.toContent)(users.map(prune));

package/lib/mcp/tools/core/create_android_sha.js

@@ -36,5 +36,8 @@ exports.create_android_sha = (0, tool_1.tool)("core", {
         shaHash: sha_hash,
         certType,
     });
-    return (0, util_1.toContent)(Object.assign(Object.assign({}, shaCertificate), { message: `Successfully added ${certType} certificate to Android app ${app_id}` }));
+    return (0, util_1.toContent)({
+        ...shaCertificate,
+        message: `Successfully added ${certType} certificate to Android app ${app_id}`,
+    });
 });

package/lib/mcp/tools/core/get_environment.js

@@ -1,6 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.get_environment = exports.hydrateTemplate = void 0;
+exports.get_environment = void 0;
+exports.hydrateTemplate = hydrateTemplate;
 const zod_1 = require("zod");
 const tool_1 = require("../../tool");
 const util_1 = require("../../util");
@@ -15,6 +16,7 @@ function hydrateTemplate(config) {
         : "<NONE>";
     const projectConfigPath = config.projectConfigPath || "<NO CONFIG PRESENT>";
     const geminiTosAccepted = config.geminiTosAccepted ? "Accepted" : "<NOT ACCEPTED>";
+    const billingEnabled = config.projectId ? (config.isBillingEnabled ? "Yes" : "No") : "N/A";
     const authenticatedUser = config.authenticatedUser || "<NONE>";
     const detectedApps = Object.entries(config.detectedAppIds).length > 0
         ? `\n\n${(0, js_yaml_1.dump)(config.detectedAppIds).trim()}\n`
@@ -30,6 +32,7 @@ Project Directory: ${config.projectDir}
 Project Config Path: ${projectConfigPath}
 Active Project ID: ${activeProject}
 Gemini in Firebase Terms of Service: ${geminiTosAccepted}
+Billing Enabled: ${billingEnabled}
 Authenticated User: ${authenticatedUser}
 Detected App IDs: ${detectedApps}
 Available Project Aliases (format: '[alias]: [projectId]'): ${availableProjects}${hasOtherAccounts ? `\nAvailable Accounts: \n\n${availableAccounts}` : ""}
@@ -50,10 +53,9 @@ b) Initialize a new Firebase project directory using the 'firebase_init' tool.
 
 Confirm with the user before taking action.`}`;
 }
-exports.hydrateTemplate = hydrateTemplate;
 exports.get_environment = (0, tool_1.tool)("core", {
     name: "get_environment",
-    description: "Use this to retrieve the current Firebase **environment** configuration for the Firebase CLI and Firebase MCP server, including current authenticated user, project directory, active Firebase Project, and more.",
+    description: "Use this to retrieve the current Firebase **environment** configuration for the Firebase CLI and Firebase MCP server, including current authenticated user, project directory, active Firebase Project, and more. All tools require the user to be authenticated, but not all information is required for all tools. Pay attention to the tool requirements for which pieces of information are required.",
     inputSchema: zod_1.z.object({}),
     annotations: {
         title: "Get Firebase Environment Info",
@@ -63,7 +65,7 @@ exports.get_environment = (0, tool_1.tool)("core", {
         requiresAuth: false,
         requiresProject: false,
     },
-}, async (_, { projectId, host, accountEmail, rc, config }) => {
+}, async (_, { projectId, host, accountEmail, rc, config, isBillingEnabled }) => {
     const aliases = projectId ? (0, projectUtils_1.getAliases)({ rc }, projectId) : [];
     const geminiTosAccepted = !!configstore_1.configstore.get("gemini");
     const projectFileExists = config.projectFileExists("firebase.json");
@@ -84,6 +86,7 @@ exports.get_environment = (0, tool_1.tool)("core", {
         projectDir: host.cachedProjectDir,
         projectConfigPath: projectFileExists ? config.path("firebase.json") : undefined,
         geminiTosAccepted,
+        isBillingEnabled,
         authenticatedUser: accountEmail || undefined,
         projectAliasMap: rc.projects,
         allAccounts,

package/lib/mcp/tools/core/get_sdk_config.js

@@ -28,13 +28,12 @@ exports.get_sdk_config = (0, tool_1.tool)("core", {
         requiresAuth: true,
     },
 }, async ({ platform: inputPlatform, app_id: appId }, { projectId }) => {
-    var _a, _b;
-    let platform = inputPlatform === null || inputPlatform === void 0 ? void 0 : inputPlatform.toUpperCase();
+    let platform = inputPlatform?.toUpperCase();
     if (!platform && !appId)
         return (0, util_1.mcpError)("Must specify one of 'web', 'ios', or 'android' for platform or an app_id for get_sdk_config tool.");
-    const apps = await (0, apps_1.listFirebaseApps)(projectId, platform !== null && platform !== void 0 ? platform : apps_1.AppPlatform.ANY);
-    platform = platform || ((_a = apps.find((app) => app.appId === appId)) === null || _a === void 0 ? void 0 : _a.platform);
-    appId = appId || ((_b = apps.find((app) => app.platform === platform)) === null || _b === void 0 ? void 0 : _b.appId);
+    const apps = await (0, apps_1.listFirebaseApps)(projectId, platform ?? apps_1.AppPlatform.ANY);
+    platform = platform || apps.find((app) => app.appId === appId)?.platform;
+    appId = appId || apps.find((app) => app.platform === platform)?.appId;
     if (!appId)
         return (0, util_1.mcpError)(`Could not find an app for platform '${inputPlatform}' in project '${projectId}'`);
     const sdkConfig = await (0, apps_1.getAppConfig)(appId, platform);

package/lib/mcp/tools/core/get_security_rules.js

@@ -23,7 +23,6 @@ exports.get_security_rules = (0, tool_1.tool)("core", {
         requiresAuth: true,
     },
 }, async ({ type }, { projectId }) => {
-    var _a;
     if (type === "rtdb") {
         const dbUrl = await (0, getDefaultDatabaseInstance_1.getDefaultDatabaseInstance)(projectId);
         if (dbUrl === "") {
@@ -51,5 +50,5 @@ exports.get_security_rules = (0, tool_1.tool)("core", {
     if (!rulesetName)
         return (0, util_1.mcpError)(`No active ${productName} rules were found in project '${projectId}'`);
     const rules = await (0, rules_1.getRulesetContent)(rulesetName);
-    return (0, util_1.toContent)((_a = rules === null || rules === void 0 ? void 0 : rules[0].content) !== null && _a !== void 0 ? _a : "Ruleset contains no rules files.");
+    return (0, util_1.toContent)(rules?.[0].content ?? "Ruleset contains no rules files.");
 });

package/lib/mcp/tools/core/init.js

@@ -213,8 +213,8 @@ exports.init = (0, tool_1.tool)("core", {
         };
     }
     const setup = {
-        config: config === null || config === void 0 ? void 0 : config.src,
-        rcfile: rc === null || rc === void 0 ? void 0 : rc.data,
+        config: config?.src,
+        rcfile: rc?.data,
         projectId: projectId,
         features: [...featuresList],
         featureInfo: featureInfo,

package/lib/mcp/tools/core/logout.js

@@ -32,7 +32,7 @@ exports.logout = (0, tool_1.tool)("core", {
     if (email && accountsToLogOut.length === 0) {
         return (0, util_1.toContent)(`No account matches ${email}, can't log out.`);
     }
-    const logoutDefault = email === (defaultAccount === null || defaultAccount === void 0 ? void 0 : defaultAccount.user.email);
+    const logoutDefault = email === defaultAccount?.user.email;
     let newDefaultAccount = undefined;
     if (logoutDefault && additionalAccounts.length > 0) {
         newDefaultAccount = additionalAccounts[0];

package/lib/mcp/tools/core/read_resources.js

@@ -21,7 +21,7 @@ exports.read_resources = (0, tool_1.tool)("core", {
             .describe("list of resource uris to read. each must start with `firebase://` prefix. omit to list all available resources"),
     }),
 }, async ({ uris }, ctx) => {
-    if (!(uris === null || uris === void 0 ? void 0 : uris.length)) {
+    if (!uris?.length) {
         void (0, track_1.trackGA4)("mcp_read_resource", { resource_name: "__list__" });
         return (0, util_1.toContent)(resources_1.resources
             .map((r) => `Available resources:\n\n- [${r.mcp.title || r.mcp.name}](${r.mcp.uri}): ${r.mcp.description}`)
@@ -34,7 +34,7 @@ exports.read_resources = (0, tool_1.tool)("core", {
             out.push(`<resource uri="${uri}" error>\nRESOURCE NOT FOUND\n</resource>`);
             continue;
         }
-        out.push(`<resource uri="${uri}" title="${resolved.mcp.title || resolved.mcp.name}">\n${resolved.result.contents.map((c) => c.text).join("")}\n</resource>`);
+        out.push(`<resource uri="${uri}" title="${resolved.mcp.title || resolved.mcp.name}">\n${resolved.result.contents.map((c) => ("text" in c ? c.text : "")).join("")}\n</resource>`);
     }
     return (0, util_1.toContent)(out.join("\n\n"));
 });

package/lib/mcp/tools/core/validate_security_rules.js

@@ -79,7 +79,6 @@ exports.validate_security_rules = (0, tool_1.tool)("core", {
         return rtdbActive || storageActive || firestoreActive;
     },
 }, async ({ type, source, source_file }, { projectId, config, host }) => {
-    var _a, _b;
     let rulesSourceContent;
     if (source && source_file) {
         return (0, util_1.mcpError)("Must supply `source` or `source_file`, not both.");
@@ -116,7 +115,7 @@ exports.validate_security_rules = (0, tool_1.tool)("core", {
     const result = await (0, rules_1.testRuleset)(projectId, [
         { name: "test.rules", content: rulesSourceContent },
     ]);
-    if ((_b = (_a = result.body) === null || _a === void 0 ? void 0 : _a.issues) === null || _b === void 0 ? void 0 : _b.length) {
+    if (result.body?.issues?.length) {
         const issues = result.body.issues;
         let out = `Found ${issues.length} issues in rules source:\n\n`;
         out += formatRulesetIssues(issues, rulesSourceContent);