firebase-tools 14.18.0 → 14.19.1

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

@@ -15,7 +15,7 @@ exports.deploy = (0, prompt_1.prompt)({
     annotations: {
         title: "Deploy to Firebase",
     },
-}, async ({ prompt }, { config, projectId, accountEmail }) => {
+}, async ({ prompt }, { config, projectId, accountEmail, firebaseCliCommand }) => {
     return [
         {
             role: "user",
@@ -41,7 +41,7 @@ ${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.
+1. If there is no active user, prompt the user to run \`${firebaseCliCommand} login\` in an interactive terminal before continuing.
 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 /firebase: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.
@@ -79,19 +79,19 @@ Follow the steps below taking note of any user instructions provided above.
       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>"}}\ 
+     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, provide the active project ID to the user and ask them if they want to proceed using that project. If there is not an active project, give the user two options: Provide an existing project ID or create a new project. Only use the list_projects tool on user request. 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.
+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 \`${firebaseCliCommand} apphosting:backends:create --backend <backendId> --primary-region us-central1 --root-dir .\` shell.
+7. Only after making sure Firebase has been initialized, run the \`${firebaseCliCommand} 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.
+9. If the deploy needs \`--force\` to run successfully, ALWAYS prompt the user before running \`${firebaseCliCommand} deploy --force\`.
+10. If only one specific feature is failing, use command \`${firebaseCliCommand} deploy --only <feature>\` as you debug.
 11. If the deploy succeeds, your job is finished.
 `.trim(),
             },

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

@@ -6,12 +6,12 @@ const types_1 = require("../../../dataconnect/types");
 const prompt_1 = require("../../prompt");
 exports.init = (0, prompt_1.prompt)({
     name: "init",
-    description: "Use this command to setup Firebase for the current workspace.",
+    description: "Use this command to set up Firebase services, like backend and AI features.",
     annotations: {
         title: "Initialize Firebase",
     },
 }, async (_, mcp) => {
-    const { config, projectId, accountEmail } = mcp;
+    const { config, projectId, accountEmail, firebaseCliCommand } = mcp;
     const platform = await (0, appFinder_1.getPlatformFromFolder)(config.projectDir);
     return [
         {
@@ -41,22 +41,17 @@ ${config.readProjectFile("firebase.json", { fallback: "<FILE DOES NOT EXIST>" })
 
 
 ## Steps
-
 Follow the steps below taking note of any user instructions provided above.
 
 1. If there is no active user, use the \`firebase_login\` tool to help them sign in.
-   - If you run into issues logging the user in, suggest that they run \`npx firebase-tools login --reauth\` in a separate terminal
-2.1 If the user supplied specific instructions, determine which of the services listed below are the best match for the user's needs. Skip to 2.2 if they didn't provide a prompt
-  1. Backend Services: Backend services for the user such as user authentication, database, or hosting.
-  2. Firebase AI Logic: Add AI features such as chat experiences, multimodal prompts, image generation and editing (via nano banana), etc.
-  - UNAVAILABLE SERVICES: Analytics, Remote Config (feature flagging), A/B testing, Crashlytics (crash reporting), and Cloud Messaging (push notifications) are not yet available for setup via this command.
-2.2 Start by listing out the existing init options that are available to the user. Ask the user which set of services they would like to add to their app. Always enumerate them and list the options out explicitly for the user.
-  1. Backend Services: Backend services for the user such as user authentication, database, or cloud file hosting.
-    - IMPORTANT: The backend setup guide is for web apps only. If the user requests backend setup for a mobile app (iOS, Android, or Flutter), inform them that this is not supported and do not use the backend setup guide. You can still assist with other requests. 
-  2. Firebase AI Logic: Add AI features such as chat experiences, multimodal prompts, image generation and editing (via nano banana), etc.
+   - If you run into issues logging the user in, suggest that they run \`${firebaseCliCommand} login --reauth\` in a separate terminal
+2. Start by listing out the existing init options that are available to the user. Ask the user which set of services they would like to add to their app. Always enumerate them and list the options out explicitly for the user:
+  - Backend Services: Backend services for the app, such as setting up a database, adding a user-authentication sign up and login page, and deploying a web app to a production URL.
+    - IMPORTANT: The backend setup guide is for web apps only. If the user requests backend setup for a mobile app (iOS, Android, or Flutter), inform them that this is not supported and do not use the backend setup guide. You can still assist with other requests.
+  - Firebase AI Logic: Add AI features such as chat experiences, multimodal prompts, image generation and editing (via nano banana), etc.
     - IMPORTANT: The Firebase AI Logic setup guide is for web, flutter, and android apps only. If the user requests firebase setup for unsupported platforms (iOS, Unity, or anything else), inform them that this is not supported and direct the user to Firebase Docs to learn how to set up AI Logic for their application (share this link with the user https://firebase.google.com/docs/ai-logic/get-started?api=dev). You can still assist with other requests.
-3. After the user chooses an init option, create a plan based on the remaining steps in this guide, share it with the user, and give them an opportunity to accept or adjust it.   
-4. If there is no active Firebase project, ask the user if they would like to create a project, or use an existing one, and ask them for the project ID
+3. After the user chooses an init option, create a plan based on the remaining steps in this guide, share it with the user, and give them an opportunity to accept or adjust it.
+4. If there is no active Firebase project, ask the user if they want to create a new project or use an existing one. If using an existing project, ask for the project ID and explain how to find it: open the Firebase Console (http://console.firebase.google.com/), locate the project ID under the project name in the projects list, or open the project and go to Project Overview → Project Settings.
    - If they would like to create a project, use the firebase_create_project with the project ID
    - If they would like to use an existing project, use the firebase_update_environment tool with the active_project argument.
    - If you run into issues creating the firebase project, ask the user to go to the [Firebase Console](http://console.firebase.google.com/) and create a project. Wait for the user to report back before continuing.
@@ -65,11 +60,13 @@ Follow the steps below taking note of any user instructions provided above.
      - Run the \`firebase_list_apps\` tool to list their apps, and find an app that matches their "Workspace platform"
      - If there is no app that matches that criteria, use the \`firebase_create_app\` tool to create the app with the appropriate platform
    - Do the following only for Flutter apps
-     - Install the Flutterfire CLI 
-     - Use the Flutterfire CLI tool to connect to the project  
+     - Execute \`firebase --version\`  to check if the Firebase CLI is installed
+       - If it isn't installed, run \`npm install -g firebase-tools\` to install it. If it is installed, skip to the next step. 
+     - Install the Flutterfire CLI
+     - Use the Flutterfire CLI tool to connect to the project
      - Use the Flutterfire CLI to register the appropriate applications based on the user's input
        - Let the developer know that you currently only support configuring web, ios, and android targets together in a bundle. Each of those targets will have appropriate apps registered in the project using the flutterfire CLI
-       - Execute flutterfire config using the following pattern: flutterfire config --yes --project=<aliasOrProjectId> --platforms=<platforms> 
+       - Execute flutterfire config using the following pattern: flutterfire config --yes --project=<aliasOrProjectId> --platforms=<platforms>
 6. Now that we have a working environment, print out 1) Active user 2) Firebase Project and 3) Firebase App & platform they are using for this process.
    - Ask the user to confirm this is correct before continuing
 7. Set up the web Firebase SDK. Skip straight to #8 for Flutter and Android apps
@@ -88,7 +85,7 @@ Follow the steps below taking note of any user instructions provided above.
     '''
 8. Read the guide for the appropriate services and follow the instructions. If no guides match the user's need, inform the user.
 - Use the Firebase \`read_resources\` tool to load the instructions for the service the developer chose in step 2 of this guide
-  - [Backend Services](firebase://guides/init/backend): Read this resource to setup backend services for the user such as user authentication, database, or hosting.
+  - [Backend Services](firebase://guides/init/backend): Read this resource to set up backend services for the app, such as setting up a database, adding a user-authentication sign up and login page, and deploying a web app to a production URL.
   - [Firebase AI Logic](firebase://guides/init/ai): Read this resource to add Gemini-powered AI features such as chat experiences, multimodal prompts, image generation, image editing (via nano banana), etc.
 `.trim(),
             },

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

@@ -9,7 +9,7 @@ exports.connect = (0, prompt_1.prompt)({
     annotations: {
         title: "Access Crashlytics data",
     },
-}, async (unused, { accountEmail }) => {
+}, async (unused, { accountEmail, firebaseCliCommand }) => {
     return [
         {
             role: "user",
@@ -25,7 +25,7 @@ Active user: ${accountEmail || "<NONE>"}
 
   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 \`firebase login\` 
+    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. 
 

package/lib/mcp/prompts/index.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.availablePrompts = void 0;
+exports.markdownDocsOfPrompts = exports.availablePrompts = void 0;
 const core_1 = require("./core");
 const dataconnect_1 = require("./dataconnect");
 const crashlytics_1 = require("./crashlytics");
@@ -33,16 +33,37 @@ function namespacePrompts(promptsToNamespace, feature) {
         return newPrompt;
     });
 }
-function availablePrompts(features) {
-    const allPrompts = namespacePrompts(prompts["core"], "core");
-    if (!features) {
-        features = Object.keys(prompts).filter((f) => f !== "core");
+function availablePrompts(activeFeatures) {
+    const allPrompts = [];
+    if (!(activeFeatures === null || activeFeatures === void 0 ? void 0 : activeFeatures.length)) {
+        activeFeatures = Object.keys(prompts);
     }
-    for (const feature of features) {
-        if (prompts[feature] && feature !== "core") {
-            allPrompts.push(...namespacePrompts(prompts[feature], feature));
-        }
+    if (!activeFeatures.includes("core")) {
+        activeFeatures = ["core", ...activeFeatures];
+    }
+    for (const feature of activeFeatures) {
+        allPrompts.push(...namespacePrompts(prompts[feature], feature));
     }
     return allPrompts;
 }
 exports.availablePrompts = availablePrompts;
+function markdownDocsOfPrompts() {
+    var _a, _b;
+    const allPrompts = availablePrompts();
+    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) || "";
+        let description = prompt.mcp.description || "";
+        if ((_b = prompt.mcp.arguments) === null || _b === void 0 ? void 0 : _b.length) {
+            const argsList = prompt.mcp.arguments.map((arg) => ` <br>&lt;${arg.name}&gt;${arg.required ? "" : " (optional)"}: ${arg.description || ""}`);
+            description += ` <br><br>Arguments:${argsList.join("")}`;
+        }
+        description = description.replaceAll("\n", "<br>");
+        doc += `
+| ${prompt.mcp.name} | ${feature} | ${description} |`;
+    }
+    return doc;
+}
+exports.markdownDocsOfPrompts = markdownDocsOfPrompts;

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

@@ -60,6 +60,10 @@ Take the following actions depending on the language and platform or framework t
 
 - Use the firebase_init tool to set up ailogic
 
+- For Android, the Google Services Gradle plugin is required to prevent the app from crashing. You must add it in two files:
+  - 1.  In your project-level \`/build.gradle.kts\` file, add the plugin to the plugins block: id("com.google.gms.google-services") version "4.4.2" apply false
+  - 2.  In your **app-level** \`/app/build.gradle.kts\` file, apply the plugin: id("com.google.gms.google-services")
+
 ### 3\. Implement AI Features
 
 #### Gather Building Blocks for Code Generation
@@ -77,6 +81,10 @@ Take the following actions depending on the language and platform or framework t
     - Kotlin Only
       - implementation(platform("com.google.firebase:firebase-bom:34.3.0")) or a higher bom version if it is available
       - implementation("com.google.firebase:firebase-ai")
+    - CRITICAL: When initializing the Firebase AI model in Kotlin, you must explicitly specify the Google AI backend by calling the googleAI() function. The correct syntax is GenerativeBackend.googleAI().
+      - Correct Example: val model = Firebase.ai(backend = GenerativeBackend.googleAI()).generativeModel(...)
+      - Incorrect: Do not use the invalid constant GenerativeBackend.GOOGLE_AI.
+    - The Kotlin SDK public API makes extensive use of suspend functions and coroutines. Make sure the code you generate is based on that paradigm and avoid using callbacks unless absolutely necessary in Kotlin
   - For Flutter apps, always include the following imports. do not forget or modify them
     - import 'package:firebase_core/firebase_core.dart';
     - import 'package:firebase_ai/firebase_ai.dart';

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

@@ -27,6 +27,10 @@ exports.init_auth = (0, resource_1.resource)({
 **Testing & Deployment:**
 - Test the complete sign-up and sign-in flow to verify authentication functionality
 - Deploy the application to production once authentication is verified and working properly
+
+**Next Steps:**
+- **Security Rules**: If an app uses *Cloud Firestore database*, *Cloud Storage for Firebase*, or *Firebase Realtime Database*, then please update user-based Security Rules that are structured according to the app's specific requirements.
+- **App Deployment**: Deploy the app to production after Security Rules are verified to be working properly.
 `.trim(),
             },
         ],

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

@@ -30,6 +30,8 @@ ${config.readProjectFile("firestore.rules", { fallback: "<FILE DOES NOT EXIST>"
 
 For database entities that neatly fall into the "personal" and "public categories, you can use the personalData and publicData rules. Use the following firestore.rules file, and add a comment above 'personalData' and 'publicData' to note what entities apply to each rule.
 
+**Next Steps:**
+- **App Deployment**: Deploy the app to production after Security Rules are verified to be working properly.
 \`\`\`
 rules_version = '2';
 

package/lib/mcp/resources/index.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.resolveResource = exports.resourceTemplates = exports.resources = void 0;
+exports.markdownDocsOfResources = exports.resolveResource = exports.resourceTemplates = exports.resources = void 0;
 const docs_1 = require("./docs");
 const init_ai_1 = require("./guides/init_ai");
 const init_auth_1 = require("./guides/init_auth");
@@ -42,3 +42,18 @@ async function resolveResource(uri, ctx, track = true) {
     return null;
 }
 exports.resolveResource = resolveResource;
+function markdownDocsOfResources() {
+    const allResources = [...exports.resources, ...exports.resourceTemplates];
+    const headings = `
+| Resource Name | Description |
+| ------------- | ----------- |`;
+    const resourceRows = allResources.map((res) => {
+        let desc = res.mcp.title ? `${res.mcp.title}: ` : "";
+        desc += res.mcp.description || "";
+        desc = desc.replaceAll("\n", "<br>");
+        return `
+| ${res.mcp.name} | ${desc} |`;
+    });
+    return headings + resourceRows.join("");
+}
+exports.markdownDocsOfResources = markdownDocsOfResources;

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

@@ -13,7 +13,7 @@ exports.list_backends = (0, tool_1.tool)({
         "is the resource name of the Cloud Run service serving the App Hosting backend. The last segment of that name is the service ID. " +
         "`domains` is the list of domains that are associated with the backend. They either have type `CUSTOM` or `DEFAULT`. " +
         "  Every backend should have a `DEFAULT` domain. " +
-        "  The actual domain that a user would use to conenct to the backend is the last parameter of the domain resource name. " +
+        "  The actual domain that a user would use to connect to the backend is the last parameter of the domain resource name. " +
         "  If a custom domain is correctly set up, it will have statuses ending in `ACTIVE`.",
     inputSchema: zod_1.z.object({
         location: zod_1.z

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

@@ -8,6 +8,7 @@ const projectUtils_1 = require("../../../projectUtils");
 const js_yaml_1 = require("js-yaml");
 const auth_1 = require("../../../auth");
 const configstore_1 = require("../../../configstore");
+const appUtils_1 = require("../../../appUtils");
 exports.get_environment = (0, tool_1.tool)({
     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.",
@@ -23,32 +24,48 @@ exports.get_environment = (0, tool_1.tool)({
 }, async (_, { projectId, host, accountEmail, rc, config }) => {
     const aliases = projectId ? (0, projectUtils_1.getAliases)({ rc }, projectId) : [];
     const geminiTosAccepted = !!configstore_1.configstore.get("gemini");
+    const projectFileExists = config.projectFileExists("firebase.json");
+    const detectedApps = await (0, appUtils_1.detectApps)(process.cwd());
+    const allAccounts = (0, auth_1.getAllAccounts)().map((account) => account.user.email);
+    const hasOtherAccounts = allAccounts.filter((email) => email !== accountEmail).length > 0;
+    const projectConfigPathString = projectFileExists
+        ? config.path("firebase.json")
+        : "<NO CONFIG PRESENT>";
+    const detectedAppsMap = detectedApps
+        .filter((app) => !!app.appId)
+        .reduce((map, app) => {
+        if (app.appId) {
+            map.set(app.appId, app.bundleId ? app.bundleId : "<UNKNOWN BUNDLE ID>");
+        }
+        return map;
+    }, new Map());
+    const activeProjectString = projectId
+        ? `${projectId}${aliases.length ? ` (alias: ${aliases.join(",")})` : ""}`
+        : "<NONE>";
+    const acceptedGeminiTosString = geminiTosAccepted ? "Accepted" : "<NOT ACCEPTED>";
     return (0, util_1.toContent)(`# Environment Information
 
 Project Directory: ${host.cachedProjectDir}
-Project Config Path: ${config.projectFileExists("firebase.json") ? config.path("firebase.json") : "<NO CONFIG PRESENT>"}
-Active Project ID: ${projectId ? `${projectId}${aliases.length ? ` (alias: ${aliases.join(",")})` : ""}` : "<NONE>"}
+Project Config Path: ${projectConfigPathString}
+Active Project ID: ${activeProjectString}
+Gemini in Firebase Terms of Service: ${acceptedGeminiTosString}
 Authenticated User: ${accountEmail || "<NONE>"}
-Gemini in Firebase Terms of Service: ${geminiTosAccepted ? "Accepted" : "Not Accepted"}
-
-# Available Project Aliases (format: '[alias]: [projectId]')
-
-${(0, js_yaml_1.dump)(rc.projects).trim()}
-
-# Available Accounts:
-
-${(0, js_yaml_1.dump)((0, auth_1.getAllAccounts)().map((account) => account.user.email)).trim()}
-${config.projectFileExists("firebase.json")
-        ? `
-# firebase.json contents:
+Detected App IDs: ${detectedAppsMap.size > 0 ? `\n\n${(0, js_yaml_1.dump)(Object.fromEntries(detectedAppsMap)).trim()}\n` : "<NONE>"}
+Available Project Aliases (format: '[alias]: [projectId]'): ${Object.entries(rc.projects).length > 0 ? `\n\n${(0, js_yaml_1.dump)(rc.projects).trim()}\n` : "<NONE>"}${hasOtherAccounts ? `\nAvailable Accounts: \n\n${(0, js_yaml_1.dump)(allAccounts).trim()}` : ""}
+${projectFileExists
+        ? `\nfirebase.json contents:
 
 \`\`\`json
 ${config.readProjectFile("firebase.json")}
 \`\`\``
-        : `\n# Empty Environment
+        : `\nNo firebase.json file was found.
+      
+If this project does not use Firebase services that require a firebase.json file, no action is necessary.
 
-It looks like the current directory is not initialized as a Firebase project. The user will most likely want to:
+If this project uses Firebase services that require a firebase.json file, the user will most likely want to:
 
 a) Change the project directory using the 'firebase_update_environment' tool to select a directory with a 'firebase.json' file in it, or
-b) Initialize a new Firebase project directory using the 'firebase_init' tool.`}`);
+b) Initialize a new Firebase project directory using the 'firebase_init' tool.
+
+Confirm with the user before taking action.`}`);
 });

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

@@ -11,6 +11,7 @@ const errors_1 = require("../../errors");
 const error_1 = require("../../../error");
 const utils_1 = require("../../../init/features/ailogic/utils");
 const projects_1 = require("../../../management/projects");
+const dataconnect_1 = require("../../../init/features/dataconnect");
 exports.init = (0, tool_1.tool)({
     name: "init",
     description: "Use this to initialize selected Firebase services in the workspace (Cloud Firestore database, Firebase Data Connect, Firebase Realtime Database, Firebase AI Logic). All services are optional; specify only the products you want to set up. " +
@@ -70,7 +71,7 @@ exports.init = (0, tool_1.tool)({
                 location_id: zod_1.z
                     .string()
                     .optional()
-                    .default("us-central1")
+                    .default(dataconnect_1.FDC_DEFAULT_REGION)
                     .describe("The GCP region ID to set up the Firebase Data Connect service."),
                 cloudsql_instance_id: zod_1.z
                     .string()

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

@@ -2,7 +2,6 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.logout = void 0;
 const zod_1 = require("zod");
-const clc = require("colorette");
 const tool_1 = require("../../tool");
 const util_1 = require("../../util");
 const auth_1 = require("../../../auth");
@@ -44,7 +43,7 @@ exports.logout = (0, tool_1.tool)({
         if (token) {
             try {
                 await (0, auth_1.logout)(token);
-                logoutMessages.push(`Logged out from ${clc.bold(account.user.email)}`);
+                logoutMessages.push(`Logged out from ${account.user.email}`);
             }
             catch (e) {
                 if (e instanceof Error) {

package/lib/mcp/tools/functions/get_logs.js

@@ -6,6 +6,7 @@ const tool_1 = require("../../tool");
 const util_1 = require("../../util");
 const functionslog_1 = require("../../../functions/functionslog");
 const cloudlogging_1 = require("../../../gcp/cloudlogging");
+const error_1 = require("../../../error");
 const SEVERITY_LEVELS = [
     "DEFAULT",
     "DEBUG",
@@ -39,12 +40,13 @@ function validateTimestamp(label, value) {
 }
 exports.get_logs = (0, tool_1.tool)({
     name: "get_logs",
-    description: "Retrieves a page of Cloud Functions log entries using Google Cloud Logging advanced filters.",
+    description: "Use this to retrieve a page of Cloud Functions log entries using Google Cloud Logging advanced filters.",
     inputSchema: zod_1.z.object({
         function_names: zod_1.z
-            .union([zod_1.z.string(), zod_1.z.array(zod_1.z.string()).min(1)])
+            .array(zod_1.z.string())
+            .min(1)
             .optional()
-            .describe("Optional list of deployed Cloud Function names to filter logs (string or array)."),
+            .describe("Optional list of deployed Cloud Function IDs to filter logs (e.g. ['fnA','fnB'])."),
         page_size: zod_1.z
             .number()
             .int()
@@ -84,8 +86,8 @@ exports.get_logs = (0, tool_1.tool)({
         requiresProject: true,
     },
 }, async ({ function_names, page_size, order, page_token, min_severity, start_time, end_time, filter }, { projectId }) => {
-    const resolvedOrder = order;
-    const resolvedPageSize = page_size;
+    const resolvedOrder = (order === null || order === void 0 ? void 0 : order.toLowerCase()) === "asc" ? "asc" : "desc";
+    const resolvedPageSize = page_size !== null && page_size !== void 0 ? page_size : 50;
     const normalizedSelectors = normalizeFunctionSelectors(function_names);
     const filterParts = [(0, functionslog_1.getApiFilter)(normalizedSelectors)];
     if (min_severity) {
@@ -143,7 +145,7 @@ exports.get_logs = (0, tool_1.tool)({
         return (0, util_1.toContent)(response);
     }
     catch (err) {
-        const message = err instanceof Error ? err.message : "Failed to retrieve Cloud Logging entries.";
-        return (0, util_1.mcpError)(message);
+        const errMsg = (0, error_1.getErrMsg)((err === null || err === void 0 ? void 0 : err.original) || err, "Failed to retrieve Cloud Logging entries.");
+        return (0, util_1.mcpError)(errMsg);
     }
 });

package/lib/mcp/tools/index.js

@@ -18,7 +18,7 @@ function availableTools(activeFeatures) {
         activeFeatures = Object.keys(tools);
     }
     if (!activeFeatures.includes("core")) {
-        activeFeatures.unshift("core");
+        activeFeatures = ["core", ...activeFeatures];
     }
     for (const key of activeFeatures) {
         toolDefs.push(...tools[key]);
@@ -53,8 +53,9 @@ function markdownDocsOfTools() {
         if (feature === "firebase") {
             feature = "core";
         }
+        const description = (((_c = tool.mcp) === null || _c === void 0 ? void 0 : _c.description) || "").replaceAll("\n", "<br>");
         doc += `
-| ${tool.mcp.name} | ${feature} | ${((_c = tool.mcp) === null || _c === void 0 ? void 0 : _c.description) || ""} |`;
+| ${tool.mcp.name} | ${feature} | ${description} |`;
     }
     return doc;
 }

package/lib/remoteconfig/deleteExperiment.js

@@ -0,0 +1,32 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.deleteExperiment = void 0;
+const clc = require("colorette");
+const api_1 = require("../api");
+const apiv2_1 = require("../apiv2");
+const error_1 = require("../error");
+const utils_1 = require("../utils");
+const TIMEOUT = 30000;
+const apiClient = new apiv2_1.Client({
+    urlPrefix: (0, api_1.remoteConfigApiOrigin)(),
+    apiVersion: "v1",
+});
+async function deleteExperiment(projectId, namespace, experimentId) {
+    try {
+        await apiClient.request({
+            method: "DELETE",
+            path: `projects/${projectId}/namespaces/${namespace}/experiments/${experimentId}`,
+            timeout: TIMEOUT,
+        });
+        return clc.bold(`Successfully deleted experiment ${clc.yellow(experimentId)}`);
+    }
+    catch (err) {
+        const error = (0, error_1.getError)(err);
+        if (error.message.includes("is running and cannot be deleted")) {
+            const rcConsoleUrl = (0, utils_1.consoleUrl)(projectId, `/config/experiment/results/${experimentId}`);
+            throw new error_1.FirebaseError(`Experiment ${experimentId} is currently running and cannot be deleted. If you want to delete this experiment, stop it at ${rcConsoleUrl}`, { original: error });
+        }
+        throw new error_1.FirebaseError(`Failed to delete Remote Config experiment with ID ${experimentId} for project ${projectId}. Error: ${(0, error_1.getErrMsg)(err)}`, { original: error });
+    }
+}
+exports.deleteExperiment = deleteExperiment;

package/lib/remoteconfig/deleteRollout.js

@@ -0,0 +1,33 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.deleteRollout = void 0;
+const api_1 = require("../api");
+const apiv2_1 = require("../apiv2");
+const error_1 = require("../error");
+const utils_1 = require("../utils");
+const clc = require("colorette");
+const TIMEOUT = 30000;
+const apiClient = new apiv2_1.Client({
+    urlPrefix: (0, api_1.remoteConfigApiOrigin)(),
+    apiVersion: "v1",
+});
+async function deleteRollout(projectId, namespace, rolloutId) {
+    try {
+        await apiClient.request({
+            method: "DELETE",
+            path: `/projects/${projectId}/namespaces/${namespace}/rollouts/${rolloutId}`,
+            timeout: TIMEOUT,
+        });
+        return clc.bold(`Successfully deleted rollout ${clc.yellow(rolloutId)}`);
+    }
+    catch (err) {
+        const originalError = (0, error_1.getError)(err);
+        const errorMessage = (0, error_1.getErrMsg)(err);
+        if (errorMessage.includes("is running and cannot be deleted")) {
+            const rcConsoleUrl = (0, utils_1.consoleUrl)(projectId, `/config/env/firebase/rollout/${rolloutId}`);
+            throw new error_1.FirebaseError(`Rollout '${rolloutId}' is currently running and cannot be deleted. If you want to delete this rollout, stop it at ${rcConsoleUrl}`, { original: originalError });
+        }
+        throw new error_1.FirebaseError(`Failed to delete Remote Config rollout with ID ${rolloutId} for project ${projectId}. Error: ${errorMessage}`, { original: originalError });
+    }
+}
+exports.deleteRollout = deleteRollout;

package/lib/remoteconfig/getExperiment.js

@@ -0,0 +1,52 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.getExperiment = exports.parseExperiment = void 0;
+const Table = require("cli-table3");
+const util = require("util");
+const api_1 = require("../api");
+const apiv2_1 = require("../apiv2");
+const logger_1 = require("../logger");
+const error_1 = require("../error");
+const TIMEOUT = 30000;
+const TABLE_HEAD = ["Entry Name", "Value"];
+const apiClient = new apiv2_1.Client({
+    urlPrefix: (0, api_1.remoteConfigApiOrigin)(),
+    apiVersion: "v1",
+});
+const parseExperiment = (experiment) => {
+    const table = new Table({ head: TABLE_HEAD, style: { head: ["green"] } });
+    table.push(["Name", experiment.name]);
+    table.push(["Display Name", experiment.definition.displayName]);
+    table.push(["Service", experiment.definition.service]);
+    table.push([
+        "Objectives",
+        util.inspect(experiment.definition.objectives, { showHidden: false, depth: null }),
+    ]);
+    table.push([
+        "Variants",
+        util.inspect(experiment.definition.variants, { showHidden: false, depth: null }),
+    ]);
+    table.push(["State", experiment.state]);
+    table.push(["Start Time", experiment.startTime]);
+    table.push(["End Time", experiment.endTime]);
+    table.push(["Last Update Time", experiment.lastUpdateTime]);
+    table.push(["etag", experiment.etag]);
+    return table.toString();
+};
+exports.parseExperiment = parseExperiment;
+async function getExperiment(projectId, namespace, experimentId) {
+    try {
+        const res = await apiClient.request({
+            method: "GET",
+            path: `projects/${projectId}/namespaces/${namespace}/experiments/${experimentId}`,
+            timeout: TIMEOUT,
+        });
+        return res.body;
+    }
+    catch (err) {
+        const error = (0, error_1.getError)(err);
+        logger_1.logger.debug(error.message);
+        throw new error_1.FirebaseError(`Failed to get Remote Config experiment with ID ${experimentId} for project ${projectId}. Error: ${error.message}`, { original: error });
+    }
+}
+exports.getExperiment = getExperiment;

package/lib/remoteconfig/getRollout.js

@@ -0,0 +1,43 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.getRollout = exports.parseRolloutIntoTable = void 0;
+const api_1 = require("../api");
+const apiv2_1 = require("../apiv2");
+const logger_1 = require("../logger");
+const error_1 = require("../error");
+const Table = require("cli-table3");
+const util = require("util");
+const TIMEOUT = 30000;
+const TABLE_HEAD = ["Entry Name", "Value"];
+const apiClient = new apiv2_1.Client({
+    urlPrefix: (0, api_1.remoteConfigApiOrigin)(),
+    apiVersion: "v1",
+});
+const parseRolloutIntoTable = (rollout) => {
+    const table = new Table({ head: TABLE_HEAD, style: { head: ["green"] } });
+    table.push(["Name", rollout.name], ["Display Name", rollout.definition.displayName], ["Description", rollout.definition.description], ["State", rollout.state], ["Create Time", rollout.createTime], ["Start Time", rollout.startTime], ["End Time", rollout.endTime], ["Last Update Time", rollout.lastUpdateTime], [
+        "Control Variant",
+        util.inspect(rollout.definition.controlVariant, { showHidden: false, depth: null }),
+    ], [
+        "Enabled Variant",
+        util.inspect(rollout.definition.enabledVariant, { showHidden: false, depth: null }),
+    ], ["ETag", rollout.etag]);
+    return table.toString();
+};
+exports.parseRolloutIntoTable = parseRolloutIntoTable;
+async function getRollout(projectId, namespace, rolloutId) {
+    try {
+        const res = await apiClient.request({
+            method: "GET",
+            path: `/projects/${projectId}/namespaces/${namespace}/rollouts/${rolloutId}`,
+            timeout: TIMEOUT,
+        });
+        return res.body;
+    }
+    catch (err) {
+        const error = (0, error_1.getError)(err);
+        logger_1.logger.debug(error.message);
+        throw new error_1.FirebaseError(`Failed to get Remote Config Rollout with ID ${rolloutId} for project ${projectId}. Error: ${error.message}`, { original: error });
+    }
+}
+exports.getRollout = getRollout;

package/lib/remoteconfig/interfaces.js

@@ -1,6 +1,8 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.TagColor = void 0;
+exports.TagColor = exports.DEFAULT_PAGE_SIZE = exports.NAMESPACE_FIREBASE = void 0;
+exports.NAMESPACE_FIREBASE = "firebase";
+exports.DEFAULT_PAGE_SIZE = "10";
 var TagColor;
 (function (TagColor) {
     TagColor["BLUE"] = "Blue";