Each tool hands the work to Gemini Cloud Assist, which then makes its own Google Cloud calls, so a single investigate_issue or design_infra call can carry a whole workflow. Google's own guidance is that the capabilities stay stable while the tool names and parameters may change.
A Google Cloud MCP server at https://geminicloudassist.googleapis.com/mcp that exposes Gemini Cloud Assist as tools. It follows an agents-as-tools pattern: the agent behind each tool makes its own calls into Google Cloud rather than returning a raw API result.
- ask_cloud_assist — the primary interface, covering everything the other tools do
- investigate_issue — quick troubleshooting, or a deeper pass through an Investigation resource
- design_infra — designing and architecting infrastructure, working with the App Design Center tools
- invoke_operation — creating, updating and deleting resources; the only path for writes, and only when Agent Actions are enabled
- optimize_costs — spending breakdowns, plus the idle and underutilized resources behind them
- App Design Center tools for the design lifecycle: setup_adc, manage_application, manage_application_template, assess_best_practices, list_application_templates
An IAM role carrying the mcp.googleapis.com/tools.call permission — roles/geminicloudassist.user, roles/geminicloudassist.editor or roles/geminicloudassist.admin. Enable the service with gcloud beta services mcp enable geminicloudassist.googleapis.com and authenticate with Application Default Credentials. Integrating with third-party tools over MCP is in private preview; access is arranged through your Google Cloud account team.
One command plus a key — gemini extensions install https://github.com/GoogleCloudPlatform/gemini-cloud-assist-mcp, then supply credentials