You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add emulator configuration to firebase_init tool
This change enhances the firebase_init MCP tool to allow for the configuration of Firebase emulators. It refactors the emulators setup logic in `src/init/features/emulators.ts` into `askQuestions` and `actuate` functions. The `firebase_init` tool now calls the `actuate` function to programmatically configure emulators, passing settings through the `featureInfo` object. A new `emulators` field has been added to the input schema to support this functionality.
host: z.string().optional().describe("The host to use for the emulator."),
12
+
port: z.number().optional().describe("The port to use for the emulator."),
13
+
});
8
14
9
15
exportconstinit=tool(
10
16
{
11
17
name: "init",
12
18
description:
13
-
"Initializes selected Firebase features in the workspace (Firestore, Data Connect, Realtime Database). All features are optional; provide only the products you wish to set up. "+
19
+
"Initializes selected Firebase features in the workspace (Firestore, Data Connect, Realtime Database, Emulators). All features are optional; provide only the products you wish to set up. "+
14
20
"You can initialize new features into an existing project directory, but re-initializing an existing feature may overwrite configuration. "+
15
21
"To deploy the initialized features, run the `firebase deploy` command after `firebase_init` tool.",
16
22
inputSchema: z.object({
@@ -121,6 +127,31 @@ export const init = tool(
121
127
.describe(
122
128
"Provide this object to initialize Firebase Storage in this project directory.",
0 commit comments