add simplified Firebase MCP Server README for Antigravity

[charlotteliang]

• Created a new streamlined README at src/mcp/antigravity/README.md
• Removed all installation instructions to keep the README concise and value-focused

[gemini-code-assist]

Summary of Changes

Hello @charlotteliang, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new, simplified README for the Firebase Model Context Protocol (MCP) Server within the Antigravity project. The primary goal is to provide AI-powered development tools with a clear and concise understanding of how to leverage Firebase projects and app codebases, effectively enabling AI agents to function as expert Firebase developers. By focusing on capabilities and usage and omitting installation specifics, the README aims to be more accessible and value-driven.

Highlights

• New README File Added: A new README.md file has been created at src/mcp/antigravity/README.md to document the Firebase Model Context Protocol (MCP) Server.
• Streamlined Content: The new README is designed to be concise and value-focused, providing an overview of the server's purpose, capabilities, and usage, while explicitly removing all installation instructions.
• Detailed Server Capabilities: The README includes comprehensive tables detailing the various tools (e.g., firebase_login, firestore_get_documents, auth_get_users, crashlytics_get_issue), prompts (e.g., firebase:deploy, firebase:consult), and resources (e.g., backend_init_guide, firestore_init_guide) offered by the Firebase MCP Server.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a new, streamlined README for the Firebase MCP Server in the antigravity directory. The new README is a good initiative to provide focused documentation. However, it duplicates the large 'Server Capabilities' tables from the main README, which introduces a significant maintenance challenge. My main feedback is to remove this duplicated section and instead link to the canonical list in the main src/mcp/README.md. This will make the new README more concise and much easier to maintain, aligning better with the PR's goal.

[gemini-code-assist]

This large 'Server Capabilities' section is duplicated from the main src/mcp/README.md. This creates a significant maintenance burden, as any changes to the tools will need to be updated in two places. The CONTRIBUTING.md file even mentions a script to auto-generate this list for the main README, which won't update this file.

To keep this README concise, avoid duplication, and improve maintainability, I suggest removing the 'Server Capabilities' section from this file and linking directly to the one in the main README.md. This also has the benefit of fixing several small typos and grammatical errors within the duplicated tables (e.g., 'conenct' on line 83).

The suggestion below replaces this entire block with a single, updated line that links to the main README.

Suggested change

	For a complete list of available tools and resources, see the [Server Capabilities](#server-capabilities) section below.
	## Documentation
	For more information, visit the [official Firebase MCP server documentation](https://firebase.google.com/docs/ai-assistance/mcp-server).
	## Server Capabilities
	The Firebase MCP server provides three types of capabilities: **Tools** (functions that perform actions), **Prompts** (reusable command templates), and **Resources** (documentation files for AI models).
	| Tool Name | Feature Group | Description |
	| ------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
	| firebase_login | core | Use this to sign the user into the Firebase CLI and Firebase MCP server. This requires a Google Account, and sign in is required to create and work with Firebase Projects. |
	| firebase_logout | core | Use this to sign the user out of the Firebase CLI and Firebase MCP server. |
	| firebase_validate_security_rules | core | Use this to check Firebase Security Rules for Firestore, Storage, or Realtime Database for syntax and validation errors. |
	| firebase_get_project | core | Use this to retrieve information about the currently active Firebase Project. |
	| firebase_list_apps | core | Use this to retrieve a list of the Firebase Apps registered in the currently active Firebase project. Firebase Apps can be iOS, Android, or Web. |
	| firebase_list_projects | core | Use this to retrieve a list of Firebase Projects that the signed-in user has access to. |
	| firebase_get_sdk_config | core | Use this to retrieve the Firebase configuration information for a Firebase App. You must specify EITHER a platform OR the Firebase App ID for a Firebase App registered in the currently active Firebase Project. |
	| firebase_create_project | core | Use this to create a new Firebase Project. |
	| firebase_create_app | core | Use this to create a new Firebase App in the currently active Firebase Project. Firebase Apps can be iOS, Android, or Web. |
	| firebase_create_android_sha | core | Use this to add the specified SHA certificate hash to the specified Firebase Android App. |
	| firebase_get_environment | core | 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. |
	| firebase_update_environment | core | Use this to update environment config for the Firebase CLI and Firebase MCP server, such as project directory, active project, active user account, accept terms of service, and more. Use `firebase_get_environment` to see the currently configured environment. |
	| firebase_init | core | 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. You can initialize new features into an existing project directory, but re-initializing an existing feature may overwrite configuration. To deploy the initialized features, run the `firebase deploy` command after `firebase_init` tool. |
	| firebase_get_security_rules | core | Use this to retrieve the security rules for a specified Firebase service. If there are multiple instances of that service in the product, the rules for the default instance are returned. |
	| firebase_read_resources | core | Use this to read the contents of `firebase://` resources or list available resources |
	| firestore_delete_document | firestore | Use this to delete a Firestore documents from a database in the current project by full document paths. Use this if you know the exact path of a document. |
	| firestore_get_documents | firestore | Use this to retrieve one or more Firestore documents from a database in the current project by full document paths. Use this if you know the exact path of a document. |
	| firestore_list_collections | firestore | Use this to retrieve a list of collections from a Firestore database in the current project. |
	| firestore_query_collection | firestore | Use this to retrieve one or more Firestore documents from a collection is a database in the current project by a collection with a full document path. Use this if you know the exact path of a collection and the filtering clause you would like for the document. |
	| auth_get_users | auth | Use this to retrieve one or more Firebase Auth users based on a list of UIDs or a list of emails. |
	| auth_update_user | auth | Use this to disable, enable, or set a custom claim on a specific user's account. |
	| auth_set_sms_region_policy | auth | Use this to set an SMS region policy for Firebase Authentication to restrict the regions which can receive text messages based on an ALLOW or DENY list of country codes. This policy will override any existing policies when set. |
	| dataconnect_build | dataconnect | Use this to compile Firebase Data Connect schema, operations, and/or connectors and check for build errors. |
	| dataconnect_generate_schema | dataconnect | Use this to generate a Firebase Data Connect Schema based on the users description of an app. |
	| dataconnect_generate_operation | dataconnect | Use this to generate a single Firebase Data Connect query or mutation based on the currently deployed schema and the provided prompt. |
	| dataconnect_list_services | dataconnect | Use this to list existing local and backend Firebase Data Connect services |
	| dataconnect_execute | dataconnect | Use this to execute a GraphQL operation against a Data Connect service or its emulator. |
	| storage_get_object_download_url | storage | Use this to retrieve the download URL for an object in a Cloud Storage for Firebase bucket. |
	| messaging_send_message | messaging | Use this to send a message to a Firebase Cloud Messaging registration token or topic. ONLY ONE of `registration_token` or `topic` may be supplied in a specific call. |
	| functions_get_logs | functions | Use this to retrieve a page of Cloud Functions log entries using Google Cloud Logging advanced filters. |
	| remoteconfig_get_template | remoteconfig | Use this to retrieve the specified Firebase Remote Config template from the currently active Firebase Project. |
	| remoteconfig_update_template | remoteconfig | Use this to publish a new remote config template or roll back to a specific version for the project |
	| crashlytics_create_note | crashlytics | Add a note to an issue from crashlytics. |
	| crashlytics_delete_note | crashlytics | Delete a note from a Crashlytics issue. |
	| crashlytics_get_issue | crashlytics | Gets data for a Crashlytics issue, which can be used as a starting point for debugging. |
	| crashlytics_list_events | crashlytics | Use this to list the most recent events matching the given filters.<br> Can be used to fetch sample crashes and exceptions for an issue,<br> which will include stack traces and other data useful for debugging. |
	| crashlytics_batch_get_events | crashlytics | Gets specific events by resource name.<br> Can be used to fetch sample crashes and exceptions for an issue,<br> which will include stack traces and other data useful for debugging. |
	| crashlytics_list_notes | crashlytics | Use this to list all notes for an issue in Crashlytics. |
	| crashlytics_get_top_issues | crashlytics | Use this to count events and distinct impacted users, grouped by _issue_.<br> Groups are sorted by event count, in descending order.<br> Only counts events matching the given filters. |
	| crashlytics_get_top_variants | crashlytics | Counts events and distinct impacted users, grouped by issue _variant_.<br> Groups are sorted by event count, in descending order.<br> Only counts events matching the given filters. |
	| crashlytics_get_top_versions | crashlytics | Counts events and distinct impacted users, grouped by _version_.<br> Groups are sorted by event count, in descending order.<br> Only counts events matching the given filters. |
	| crashlytics_get_top_apple_devices | crashlytics | Counts events and distinct impacted users, grouped by apple _device_.<br> Groups are sorted by event count, in descending order.<br> Only counts events matching the given filters.<br> Only relevant for iOS, iPadOS and MacOS applications. |
	| crashlytics_get_top_android_devices | crashlytics | Counts events and distinct impacted users, grouped by android _device_.<br> Groups are sorted by event count, in descending order.<br> Only counts events matching the given filters.<br> Only relevant for Android applications. |
	| crashlytics_get_top_operating_systems | crashlytics | Counts events and distinct impacted users, grouped by _operating system_.<br> Groups are sorted by event count, in descending order.<br> Only counts events matching the given filters. |
	| crashlytics_update_issue | crashlytics | Use this to update the state of Crashlytics issue. |
	| apphosting_fetch_logs | apphosting | Use this to fetch the most recent logs for a specified App Hosting backend. If `buildLogs` is specified, the logs from the build process for the latest build are returned. The most recent logs are listed first. |
	| apphosting_list_backends | apphosting | Use this to retrieve a list of App Hosting backends in the current project. An empty list means that there are no backends. The `uri` is the public URL of the backend. A working backend will have a `managed_resources` array that will contain a `run_service` entry. That `run_service.service` 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. If a custom domain is correctly set up, it will have statuses ending in `ACTIVE`. |
	| realtimedatabase_get_data | realtimedatabase | Use this to retrieve data from the specified location in a Firebase Realtime Database. |
	| realtimedatabase_set_data | realtimedatabase | Use this to write data to the specified location in a Firebase Realtime Database. |
	| Prompt Name | Feature Group | Description |
	| ------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
	| firebase:deploy | core | Use this command to deploy resources to Firebase. <br><br>Arguments: <br>&lt;prompt&gt; (optional): any specific instructions you wish to provide about deploying |
	| firebase:init | core | Use this command to set up Firebase services, like backend and AI features. |
	| firebase:consult | core | Use this command to consult the Firebase Assistant with access to detailed up-to-date documentation for the Firebase platform. <br><br>Arguments: <br>&lt;prompt&gt;: a question to pass to the Gemini in Firebase model |
	| crashlytics:connect | crashlytics | Access a Firebase application's Crashlytics data. |
	| Resource Name | Description |
	| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
	| backend_init_guide | Firebase Backend Init Guide: guides the coding agent through configuring Firebase backend services in the current project |
	| ai_init_guide | Firebase GenAI Init Guide: guides the coding agent through configuring GenAI capabilities in the current project utilizing Firebase |
	| data_connect_init_guide | Firebase Data Connect Init Guide: guides the coding agent through configuring Data Connect for PostgreSQL access in the current project |
	| firestore_init_guide | Firestore Init Guide: guides the coding agent through configuring Firestore in the current project |
	| firestore_rules_init_guide | Firestore Rules Init Guide: guides the coding agent through setting up Firestore security rules in the project |
	| rtdb_init_guide | Firebase Realtime Database Init Guide: guides the coding agent through configuring Realtime Database in the current project |
	| auth_init_guide | Firebase Authentication Init Guide: guides the coding agent through configuring Firebase Authentication in the current project |
	| hosting_init_guide | Firebase Hosting Deployment Guide: guides the coding agent through deploying to Firebase Hosting in the current project |
	| docs | Firebase Docs: loads plain text content from Firebase documentation, e.g. `https://firebase.google.com/docs/functions` becomes `firebase://docs/functions` |
	For a complete list of available tools and resources, see the [Server Capabilities section in the main README](../README.md#server-capabilities).