firebase-tools 14.14.0 → 14.15.1

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

@@ -43,14 +43,57 @@ ${prompt || "<the user didn't supply specific instructions>"}
 Follow the steps below taking note of any user instructions provided above.
 
 1. If there is no active user, prompt the user to run \`firebase login\` in an interactive terminal before continuing.
-2. If there is no \`firebase.json\` file and the current workspace is a static web application, manually create a \`firebase.json\` with \`"hosting"\` configuration based on the current directory's web app configuration. Add a \`{"hosting": {"predeploy": "<build_script>"}}\` config to build before deploying.
-3. If there is no active project, ask the user if they want to use an existing project or create a new one.
-  3a. If create a new one, use the \`firebase_create_project\` tool.
-  3b. If they want to use an existing one, ask them for a project id (the \`firebase_list_projects\` tool may be helpful).
-4. Only after making sure Firebase has been initialized, run the \`firebase deploy\` shell command to perform the deploy. This may take a few minutes.
-5. If the deploy has errors, attempt to fix them and ask the user clarifying questions as needed.
-6. If the deploy needs \`--force\` to run successfully, ALWAYS prompt the user before running \`firebase deploy --force\`.
-7. If only one specific feature is failing, use command \`firebase deploy --only <feature>\` as you debug.
+2. Analyze the source code in the current working directory to determine if this is a web app. If it isn't, end this process and tell the user "The /deploy command only works with web apps."
+3. Analyze the source code in the current working directory to determine if the app requires a server for Server-Side Rendering (SSR). This will determine whether or not to use Firebase App Hosting. Here are instructions to determine if the app needs a server:
+  Objective: Analyze the provided codebase files to determine if the web application requires a backend for Server-Side Rendering (SSR). Your final output must be a clear "Yes" or "No" followed by a brief justification.
+  Primary Analysis: package.json
+    This is the most critical step. If the package.json file is present, perform the following checks in order.
+    Parse package.json: Locate and read the contents of the package.json file.
+      Check Dependencies:
+        Examine the dependencies and devDependencies objects.
+        If any of the following packages are listed as keys, you can conclude the app uses SSR.
+          next
+          nuxt
+          @sveltejs/kit
+          @angular/ssr
+          remix
+        If a match is found, proceed directly to the Final Determination step.
+      Check Scripts: If no framework dependency was found, examine the scripts object.
+        Look for scripts (commonly start or serve) that execute a server process.
+        Examples include: "start": "next start", "start": "nuxt start", or "dev": "ng serve --ssr".
+        If such a script is found, conclude the app uses SSR and proceed to the Final Determination step.
+  Secondary Analysis: Project File Structure
+    Perform this analysis only if package.json is missing or inconclusive.
+    Scan for Framework-Specific Files and Directories: Search the codebase for the following patterns:
+      Next.js: A directory named app/ or pages/. Inside these, check for files containing the function name getServerSideProps.
+      Nuxt.js: A directory named server/.
+      SvelteKit: Any file ending with the .server.js suffix (e.g., +page.server.js, +layout.server.js).
+      Angular: A file named server.ts.
+    If any of these patterns are found, conclude the app uses SSR.
+  Final Determination
+    State Your Conclusion: Begin your response with a definitive "Yes" or "No".
+      Yes: The application requires a backend for SSR.
+      No: The application does not appear to require a backend for SSR and is likely a static or client-side rendered app.
+    Provide Justification: Follow your conclusion with a single sentence explaining the evidence.
+      Example (Yes): "Yes, the project requires SSR, as evidenced by the next dependency in package.json."
+      Example (Yes): "Yes, the project requires SSR, as evidenced by the presence of a +page.server.js file."
+      Example (No): "No, there are no dependencies or file structures that indicate the use of a server-side rendering framework."
+4. If there is no \`firebase.json\` file, manually create one based on whether the app requires SSR:
+  4a. If the app requires SSR, configure Firebase App Hosting:
+     Create \`firebase.json\ with an "apphosting" configuration, setting backendId to the app's name in package.json: \`{"apphosting": {"backendId": "<backendId>"}}\ 
+  4b. If the app does NOT require SSR, configure Firebase Hosting:
+    Create \`firebase.json\ with a "hosting" configuration. Add a \`{"hosting": {"predeploy": "<build_script>"}}\` config to build before deploying.
+5. Check if there is an active Firebase project for this environment (the \`firebase_get_environment\` tool may be helpful). If there is, proceed using that project. If there is not an active project, give the user two options: Use an existing Firebase project or Create a new one. Wait for their response before proceeding.
+  5a. If the user chooses to use an existing Firebase project, the \`firebase_list_projects\` tool may be helpful. Set the selected project as the active project (the \`firebase_update_environment\` tool may be helpful).
+  5b. If the user chooses to create a new project, use the \`firebase_create_project	\` tool. Then set the new project as the active project (the \`firebase_update_environment\` tool may be helpful).
+6. If firebase.json contains an "apphosting" configuration, check if a backend exists matching the provided backendId (the \`apphosting_list_backends\` tool may be helpful). 
+   If it doesn't exist, create one by running the \`firebase apphosting:backends:create --backend <backendId> --primary-region us-central1 --root-dir .\` shell.
+7. Only after making sure Firebase has been initialized, run the \`firebase deploy\` shell command to perform the deploy. This may take a few minutes.
+  7a. If deploying to apphosting, tell the user the deployment will take a few minutes, and they can monitor deployment progress in the Firebase console: \`https://console.firebase.google.com/project/<projectId>/apphosting\`
+8. If the deploy has errors, attempt to fix them and ask the user clarifying questions as needed.
+9. If the deploy needs \`--force\` to run successfully, ALWAYS prompt the user before running \`firebase deploy --force\`.
+10. If only one specific feature is failing, use command \`firebase deploy --only <feature>\` as you debug.
+11. If the deploy succeeds, your job is finished.
 `.trim(),
             },
         },

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

@@ -0,0 +1,10 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.getAppIdInstruction = exports.ACTIVE_USER_INSTRUCTION = void 0;
+exports.ACTIVE_USER_INSTRUCTION = "If the Firbase 'Active user' is set to <NONE>, instruct the user to run `firebase login` before continuing. You will know that the user is not logged in if we have nothing in the 'Active user' field.";
+const getAppIdInstruction = (index) => `If there is no active app id, then do the following:
+  ${index}a. If this is an Android app, read the mobilesdk_app_id value specified in the google-services.json file. If there are multiple files or multiple app ids in single file. Ask the user to disambiguate.
+  ${index}b. If this is an iOS app, read the GOOGLE_APP_ID from GoogleService-Info.plist file. If there are multiple files or multiple app ids in single file. Ask the user to disambiguate.
+  ${index}c. If you can't find either of the above, ask the user for the app id.
+`;
+exports.getAppIdInstruction = getAppIdInstruction;

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

@@ -0,0 +1,89 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.fix_issue = void 0;
+const prompt_1 = require("../../prompt");
+const common_1 = require("./common");
+const APP_ID_INSTRUCTION = (0, common_1.getAppIdInstruction)(2);
+exports.fix_issue = (0, prompt_1.prompt)({
+    name: "fix_issue",
+    omitPrefix: false,
+    description: "Fix a Crashlytics issue",
+    arguments: [
+        {
+            name: "app_id",
+            description: "A Firebase app id.",
+            required: false,
+        },
+        {
+            name: "issue_id",
+            description: "A Crashlytics issue id.",
+            required: true,
+        },
+    ],
+    annotations: {
+        title: "Prioritize Crashlytics Issues",
+    },
+}, async ({ app_id, issue_id }, { accountEmail }) => {
+    return [
+        {
+            role: "user",
+            content: {
+                type: "text",
+                text: `
+Your goal is to fix a specific issue from Crashlytics.
+
+Active user: ${accountEmail || "<NONE>"}
+Active app: ${app_id || "<NONE>"}
+Issue id: ${issue_id}
+
+## Required information
+
+## Required information
+
+Before fetching and prioritizing issues, secure the following information:
+
+First, and this is INCREDIBLY IMPORTANT, verify the active user. IT IS SO IMPORTANT THAT YOU DO THIS FIRST. NO TOOL CALL WILL WORK WITHOUT IT. ${common_1.ACTIVE_USER_INSTRUCTION}
+Then, verify the app id. ${APP_ID_INSTRUCTION}
+Finally, verify the issue id is not null or empty.
+
+All are required to successfully investigate and fix an issue.
+
+## Steps
+
+1. Make sure you have a good understanding of the code structure and where different functionality exists
+2. Use the 'crashlytics_get_issue_details' tool to get more context on the issue.
+3. Use the 'crashlytics_get_sample_crash_for_issue' tool to get 3 example crashes for this issue.
+4. Read the files that exist in the stack trace of the issue to understand the crash deeply.
+5. Determine the root cause of the crash.
+6. Write out a plan using the following criteria:
+   6a. 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
+       * A determination of which library is at fault, this codebase or a dependent library
+       * A determination for how complex the fix will be
+   6b. The plan should include relevant files to change
+   6c. The plan should include a test plan to verify the fix
+   6d. Use the following format for the plan:
+
+   **Cause**
+   <A description of the cause of the issue>
+  
+   **Confidence**: <one of "not at all confident", "somewhat confident", "confident", "very confident">
+   **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 plan for how to fix the issue>
+
+   **Test**
+   <a plan for how to test that the issue has been fixed an protect against regressions>
+7. Present the plan to the user and get approval before making the change.
+8. Fix the issue.
+   8a. Be mindful of API contracts and do not add fields to resources without a clear way to populate those fields
+   8b. 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.
+9. Ask the developer if they would like you to test the fix for them.
+`.trim(),
+            },
+        },
+    ];
+});

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

@@ -0,0 +1,6 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.crashlyticsPrompts = void 0;
+const fix_issue_1 = require("./fix_issue");
+const prioritize_issues_1 = require("./prioritize_issues");
+exports.crashlyticsPrompts = [fix_issue_1.fix_issue, prioritize_issues_1.prioritize_issues];

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

@@ -0,0 +1,79 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.prioritize_issues = void 0;
+const prompt_1 = require("../../prompt");
+const common_1 = require("./common");
+const APP_ID_INSTRUCTION = (0, common_1.getAppIdInstruction)(2);
+exports.prioritize_issues = (0, prompt_1.prompt)({
+    name: "prioritize_issues",
+    omitPrefix: false,
+    description: "Fetch and prioritize issues from Crashlytics.",
+    arguments: [
+        {
+            name: "app_id",
+            description: "AppId for which the issues list should be fetched.",
+            required: false,
+        },
+        {
+            name: "issue_count",
+            description: "The number of issues that should be returned in the final list. Defaults to 5.",
+            required: false,
+        },
+        {
+            name: "prompt",
+            description: "Any additional instructions you wish to provide about issue prioritization.",
+            required: false,
+        },
+    ],
+    annotations: {
+        title: "Prioritize Crashlytics Issues",
+    },
+}, async ({ app_id, prompt, issue_count }, { accountEmail }) => {
+    return [
+        {
+            role: "user",
+            content: {
+                type: "text",
+                text: `
+Your goal is to prioritize issues from Crashlytics and return the top ${issue_count || 5} issues based on the criteria below.
+
+Active user: ${accountEmail || "<NONE>"}
+Active app: ${app_id || "<NONE>"}
+
+## User Instructions
+
+${prompt || "<the user didn't supply specific instructions>"}
+
+## Required information
+
+Before fetching and prioritizing issues, secure the following information:
+
+First, and this is INCREDIBLY IMPORTANT, verify the active user. IT IS SO IMPORTANT THAT YOU DO THIS FIRST. NO TOOL CALL WILL WORK WITHOUT IT. ${common_1.ACTIVE_USER_INSTRUCTION}
+Then, verify the app id. ${APP_ID_INSTRUCTION}
+
+Both pieces of information are required to successfully prioritize issues.
+
+## Steps
+
+Follow the steps below taking note of any user instructions provided above.
+
+1. Use the 'crashlytics_list_top_issues' tool to fetch up to 20 issues.
+2. Use the 'crashlytics_list_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 ${issue_count || 5} issue ids, with a brief description of the issue in the following format: 
+   * 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>
+
+The point of this command is to surface information only.
+`.trim(),
+            },
+        },
+    ];
+});

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

@@ -0,0 +1,9 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.dataconnectPrompts = void 0;
+const experiments_1 = require("../../../experiments");
+const schema_1 = require("./schema");
+exports.dataconnectPrompts = [];
+if ((0, experiments_1.isEnabled)("mcpalpha")) {
+    exports.dataconnectPrompts.push(schema_1.schema);
+}

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

@@ -0,0 +1,68 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.schema = void 0;
+const prompt_1 = require("../../prompt");
+const load_1 = require("../../../dataconnect/load");
+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 = fdcServices[0].schema.source.files) === null || _a === void 0 ? void 0 : _a.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>"}`;
+}
+exports.schema = (0, prompt_1.prompt)({
+    name: "schema",
+    description: "Generate or update your Firebase Data Connect schema.",
+    arguments: [
+        {
+            name: "prompt",
+            description: "describe the schema you want generated or the edits you want to make to your existing schema",
+            required: true,
+        },
+    ],
+    annotations: {
+        title: "Generate Data Connect Schema",
+    },
+}, async ({ prompt }, { config, projectId, accountEmail }) => {
+    const fdcServices = await (0, load_1.loadAll)(projectId, config);
+    const buildErrors = fdcServices.length
+        ? await (0, compile_1.compileErrors)(fdcServices[0].sourceDirectory)
+        : "";
+    return [
+        {
+            role: "user",
+            content: {
+                type: "text",
+                text: `
+${content_1.MAIN_INSTRUCTIONS}\n\n${content_1.BUILTIN_SDL}
+
+==== CURRENT ENVIRONMENT INFO ====
+
+User Email: ${accountEmail || "<NONE>"}
+Project ID: ${projectId || "<NONE>"}
+${renderServices(fdcServices)}${renderErrors(buildErrors)}
+
+==== USER PROMPT ====
+
+${prompt}
+
+==== TASK INSTRUCTIONS ====
+
+1. If Data Connect is marked as \`<UNCONFIGURED>\`, first run the \`firebase_init\` tool with \`{dataconnect: {}}\` arguments to initialize it.
+2. If there is not an existing schema to work with (or the existing schema is the commented-out default schema about a movie app), follow the user's prompt to generate a robust schema meeting the specified requirements.
+3. If there is already a schema, perform edits to the existing schema file(s) based on the user's instructions. If schema build errors are present and seem relevant to your changes, attempt to fix them.
+4. After you have performed edits on the schema, run the \`dataconnect_compile\` tool to build the schema and see if there are any errors. Fix errors that are related to the user's prompt or your changes.
+5. If there are errors, attempt to fix them. If you have attempted to fix them 3 times without success, ask the user for help.
+6. If there are no errors, write a brief paragraph summarizing your changes.`,
+            },
+        },
+    ];
+});

package/lib/mcp/prompts/index.js

@@ -2,15 +2,17 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.availablePrompts = void 0;
 const core_1 = require("./core");
+const dataconnect_1 = require("./dataconnect");
+const crashlytics_1 = require("./crashlytics");
 const prompts = {
     core: core_1.corePrompts,
     firestore: [],
     storage: [],
-    dataconnect: [],
+    dataconnect: dataconnect_1.dataconnectPrompts,
     auth: [],
     messaging: [],
     remoteconfig: [],
-    crashlytics: [],
+    crashlytics: crashlytics_1.crashlyticsPrompts,
     apphosting: [],
     database: [],
 };
@@ -24,7 +26,7 @@ function namespacePrompts(promptsToNamespace, feature) {
             newPrompt.mcp.name = `firebase:${p.mcp.name}`;
         }
         else {
-            newPrompt.mcp.name = `firebase:${feature}:${p.mcp.name}`;
+            newPrompt.mcp.name = `${feature}:${p.mcp.name}`;
         }
         newPrompt.mcp._meta = Object.assign(Object.assign({}, p.mcp._meta), { feature });
         return newPrompt;

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

@@ -78,7 +78,8 @@ exports.init = (0, tool_1.tool)({
                     .describe("The Postgres database ID to use in the Firebase Data Connect service."),
             })
                 .optional()
-                .describe("Provide this object to initialize Firebase Data Connect with Cloud SQL Postgres in this project directory."),
+                .describe("Provide this object to initialize Firebase Data Connect with Cloud SQL Postgres in this project directory.\n" +
+                "It installs Data Connect Generated SDKs in all detected apps in the folder."),
             storage: zod_1.z
                 .object({
                 rules_filename: zod_1.z
@@ -138,6 +139,9 @@ exports.init = (0, tool_1.tool)({
             cloudSqlInstanceId: features.dataconnect.cloudsql_instance_id || "",
             cloudSqlDatabase: features.dataconnect.cloudsql_database || "",
         };
+        featureInfo.dataconnectSdk = {
+            apps: [],
+        };
     }
     const setup = {
         config: config === null || config === void 0 ? void 0 : config.src,
@@ -145,10 +149,19 @@ exports.init = (0, tool_1.tool)({
         projectId: projectId,
         features: [...featuresList],
         featureInfo: featureInfo,
+        instructions: [],
     };
     await (0, index_1.actuate)(setup, config, { force: true });
     config.writeProjectFile("firebase.json", setup.config);
     config.writeProjectFile(".firebaserc", setup.rcfile);
-    return (0, util_1.toContent)(`Successfully setup the project ${projectId} with those features: ${featuresList.join(", ")}` +
-        " To deploy them, you can run `firebase deploy` in command line.");
+    if (featureInfo.dataconnectSdk && !featureInfo.dataconnectSdk.apps.length) {
+        setup.instructions.push(`No app is found in the current folder. We recommend you create an app (web, ios, android) first, then re-run the 'firebase_init' MCP tool to add Data Connect SDKs to your apps.
+  Consider popular commands like 'npx create-react-app my-app', 'npx create-next-app my-app', 'flutter create my-app', etc`);
+    }
+    return (0, util_1.toContent)(`Successfully setup those features: ${featuresList.join(", ")}
+
+To get started:
+
+- ${setup.instructions.join("\n\n- ")}
+`);
 });

package/lib/mcp/tools/crashlytics/add_note.js

@@ -0,0 +1,32 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.add_note = void 0;
+const zod_1 = require("zod");
+const tool_1 = require("../../tool");
+const util_1 = require("../../util");
+const addNote_1 = require("../../../crashlytics/addNote");
+const constants_1 = require("./constants");
+exports.add_note = (0, tool_1.tool)({
+    name: "add_note",
+    description: "Add a note to an issue from crashlytics.",
+    inputSchema: zod_1.z.object({
+        app_id: constants_1.APP_ID_FIELD,
+        issue_id: zod_1.z.string().describe("The issue id to add the note to."),
+        note: zod_1.z.string().describe("The note to add to the issue."),
+    }),
+    annotations: {
+        title: "Add note to Crashlytics issue.",
+        readOnlyHint: true,
+    },
+    _meta: {
+        requiresAuth: true,
+    },
+}, async ({ app_id, issue_id, note }) => {
+    if (!app_id)
+        return (0, util_1.mcpError)(`Must specify 'app_id' parameter.`);
+    if (!issue_id)
+        return (0, util_1.mcpError)(`Must specify 'issue_id' parameter.`);
+    if (!note)
+        return (0, util_1.mcpError)(`Must specify 'note' parameter.`);
+    return (0, util_1.toContent)(await (0, addNote_1.addNote)(app_id, issue_id, note));
+});

package/lib/mcp/tools/crashlytics/constants.js

@@ -0,0 +1,11 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.APP_ID_FIELD = void 0;
+const zod_1 = require("zod");
+exports.APP_ID_FIELD = zod_1.z
+    .string()
+    .describe("AppId for the application. For an Android application, read the " +
+    "mobilesdk_app_id value specified in the google-services.json file for " +
+    "the current package name. For an iOS Application, read the GOOGLE_APP_ID " +
+    "from GoogleService-Info.plist. If neither is available, ask the user to " +
+    "provide the app id.");

package/lib/mcp/tools/crashlytics/delete_note.js

@@ -0,0 +1,35 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.delete_note = void 0;
+const zod_1 = require("zod");
+const tool_1 = require("../../tool");
+const util_1 = require("../../util");
+const deleteNote_1 = require("../../../crashlytics/deleteNote");
+const constants_1 = require("./constants");
+exports.delete_note = (0, tool_1.tool)({
+    name: "delete_note",
+    description: "Delete a note from an issue in Crashlytics.",
+    inputSchema: zod_1.z.object({
+        app_id: constants_1.APP_ID_FIELD,
+        issue_id: zod_1.z.string().describe("The issue id to delete the note from."),
+        note_id: zod_1.z.string().describe("The note id to delete."),
+    }),
+    annotations: {
+        title: "Delete Note from Crashlytics Issue.",
+        readOnlyHint: true,
+    },
+    _meta: {
+        requiresAuth: true,
+    },
+}, async ({ app_id, issue_id, note_id }) => {
+    if (!app_id) {
+        return (0, util_1.mcpError)(`Must specify 'app_id' parameter.`);
+    }
+    if (!issue_id) {
+        return (0, util_1.mcpError)(`Must specify 'issue_id' parameter.`);
+    }
+    if (!note_id) {
+        return (0, util_1.mcpError)(`Must specify 'note_id' parameter.`);
+    }
+    return (0, util_1.toContent)(await (0, deleteNote_1.deleteNote)(app_id, issue_id, note_id));
+});

package/lib/mcp/tools/crashlytics/get_issue_details.js

@@ -5,13 +5,12 @@ const zod_1 = require("zod");
 const tool_1 = require("../../tool");
 const util_1 = require("../../util");
 const getIssueDetails_1 = require("../../../crashlytics/getIssueDetails");
+const constants_1 = require("./constants");
 exports.get_issue_details = (0, tool_1.tool)({
     name: "get_issue_details",
     description: "Gets the details about a specific crashlytics issue.",
     inputSchema: zod_1.z.object({
-        app_id: zod_1.z
-            .string()
-            .describe("The AppID for which the issues list should be fetched. For an Android application, read the mobilesdk_app_id value specified in the google-services.json file for the current package name. For an iOS Application, read the GOOGLE_APP_ID from GoogleService-Info.plist. If neither is available, use the `firebase_list_apps` tool to find an app_id to pass to this tool."),
+        app_id: constants_1.APP_ID_FIELD,
         issue_id: zod_1.z
             .string()
             .describe("The issue ID for which the details needs to be fetched. This is the value of the field `id` in the list of issues. Defaults to the first id in the list of issues."),
@@ -22,7 +21,6 @@ exports.get_issue_details = (0, tool_1.tool)({
     },
     _meta: {
         requiresAuth: true,
-        requiresProject: false,
     },
 }, async ({ app_id, issue_id }) => {
     if (!app_id)

package/lib/mcp/tools/crashlytics/get_sample_crash.js

@@ -5,13 +5,12 @@ const zod_1 = require("zod");
 const tool_1 = require("../../tool");
 const util_1 = require("../../util");
 const getSampleCrash_1 = require("../../../crashlytics/getSampleCrash");
+const constants_1 = require("./constants");
 exports.get_sample_crash = (0, tool_1.tool)({
     name: "get_sample_crash_for_issue",
     description: "Gets the sample crash for an issue.",
     inputSchema: zod_1.z.object({
-        app_id: zod_1.z
-            .string()
-            .describe("AppId for which the issues list should be fetched. For an Android application, read the mobilesdk_app_id value specified in the google-services.json file for the current package name. For an iOS Application, read the GOOGLE_APP_ID from GoogleService-Info.plist. If neither is available, use the `firebase_list_apps` tool to find an app_id to pass to this tool."),
+        app_id: constants_1.APP_ID_FIELD,
         issue_id: zod_1.z
             .string()
             .describe("The issue Id for which the sample crash needs to be fetched. This is the value of the field `id` in the list of issues. Defaults to the first id in the list of issues."),
@@ -30,13 +29,14 @@ exports.get_sample_crash = (0, tool_1.tool)({
     },
     _meta: {
         requiresAuth: true,
-        requiresProject: false,
     },
 }, async ({ app_id, issue_id, variant_id, sample_count }) => {
     if (!app_id)
         return (0, util_1.mcpError)(`Must specify 'app_id' parameter.`);
     if (!issue_id)
         return (0, util_1.mcpError)(`Must specify 'issue_id' parameter.`);
+    if (!sample_count)
+        sample_count = 1;
     if (sample_count > 3)
         sample_count = 3;
     return (0, util_1.toContent)(await (0, getSampleCrash_1.getSampleCrash)(app_id, issue_id, sample_count, variant_id));

package/lib/mcp/tools/crashlytics/index.js

@@ -1,11 +1,25 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.crashlyticsTools = void 0;
+const add_note_1 = require("./add_note");
+const delete_note_1 = require("./delete_note");
 const get_issue_details_1 = require("./get_issue_details");
-const list_top_issues_1 = require("./list_top_issues");
 const get_sample_crash_1 = require("./get_sample_crash");
+const list_notes_1 = require("./list_notes");
+const list_top_devices_1 = require("./list_top_devices");
+const list_top_issues_1 = require("./list_top_issues");
+const list_top_operating_systems_1 = require("./list_top_operating_systems");
+const list_top_versions_1 = require("./list_top_versions");
+const update_issue_1 = require("./update_issue");
 exports.crashlyticsTools = [
-    list_top_issues_1.list_top_issues,
+    add_note_1.add_note,
+    delete_note_1.delete_note,
     get_issue_details_1.get_issue_details,
     get_sample_crash_1.get_sample_crash,
+    list_notes_1.list_notes,
+    list_top_devices_1.list_top_devices,
+    list_top_issues_1.list_top_issues,
+    list_top_operating_systems_1.list_top_operating_systems,
+    list_top_versions_1.list_top_versions,
+    update_issue_1.update_issue,
 ];

package/lib/mcp/tools/crashlytics/list_notes.js

@@ -0,0 +1,37 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.list_notes = void 0;
+const zod_1 = require("zod");
+const tool_1 = require("../../tool");
+const util_1 = require("../../util");
+const listNotes_1 = require("../../../crashlytics/listNotes");
+const constants_1 = require("./constants");
+exports.list_notes = (0, tool_1.tool)({
+    name: "list_notes",
+    description: "List all notes for an issue in Crashlytics.",
+    inputSchema: zod_1.z.object({
+        app_id: constants_1.APP_ID_FIELD,
+        issue_id: zod_1.z.string().describe("The issue id to list notes for."),
+        note_count: zod_1.z
+            .number()
+            .optional()
+            .default(10)
+            .describe("Number of notes that needs to be fetched. Defaults to 10 if unspecified."),
+    }),
+    annotations: {
+        title: "List notes for a Crashlytics issue.",
+        readOnlyHint: true,
+    },
+    _meta: {
+        requiresAuth: true,
+    },
+}, async ({ app_id, issue_id, note_count }) => {
+    if (!app_id) {
+        return (0, util_1.mcpError)(`Must specify 'app_id' parameter.`);
+    }
+    if (!issue_id) {
+        return (0, util_1.mcpError)(`Must specify 'issue_id' parameter.`);
+    }
+    note_count !== null && note_count !== void 0 ? note_count : (note_count = 10);
+    return (0, util_1.toContent)(await (0, listNotes_1.listNotes)(app_id, issue_id, note_count));
+});

package/lib/mcp/tools/crashlytics/list_top_devices.js

@@ -0,0 +1,33 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.list_top_devices = void 0;
+const zod_1 = require("zod");
+const tool_1 = require("../../tool");
+const util_1 = require("../../util");
+const listTopDevices_1 = require("../../../crashlytics/listTopDevices");
+const constants_1 = require("./constants");
+exports.list_top_devices = (0, tool_1.tool)({
+    name: "list_top_devices",
+    description: "List the top devices from Crashlytics for an application.",
+    inputSchema: zod_1.z.object({
+        app_id: constants_1.APP_ID_FIELD,
+        issue_id: zod_1.z.string().optional().describe("The issue id to filter on"),
+        device_count: zod_1.z
+            .number()
+            .optional()
+            .default(10)
+            .describe("Number of devices that needs to be fetched. Defaults to 10 if unspecified."),
+    }),
+    annotations: {
+        title: "List Top Crashlytics Devices.",
+        readOnlyHint: true,
+    },
+    _meta: {
+        requiresAuth: true,
+    },
+}, async ({ app_id, issue_id, device_count }) => {
+    if (!app_id)
+        return (0, util_1.mcpError)(`Must specify 'app_id' parameter.`);
+    device_count !== null && device_count !== void 0 ? device_count : (device_count = 10);
+    return (0, util_1.toContent)(await (0, listTopDevices_1.listTopDevices)(app_id, device_count, issue_id));
+});