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.
Copy file name to clipboardExpand all lines: CHANGELOG.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,5 +3,3 @@
3
3
-`firebase_update_environment` MCP tool supports accepting Gemini in Firebase Terms of Service.
4
4
- Fixed a bug when `firebase init dataconnect` failed to create a React app when launched from VS Code extension (#9171).
5
5
- Improved the clarity of the `firebase apptesting:execute` command when you have zero or multiple apps.
6
-
- Added 'emulators' to `firebase_init` MCP tool.
7
-
-`firebase dataconnect:sql:migrate` now supports Cloud SQL instances with only private IPs. The command must be run in the same VPC of the instance to work. (##9200)
0 commit comments