Gemini Cloud Assist MCP

What gemini-cloud-assist-mcp does

gemini-cloud-assist-mcp connects MCP-compatible clients to the Gemini Cloud Assist APIs, specifically the Cloud Operator endpoint at https://geminicloudassist.googleapis.com/mcp/autocloud. The endpoint exposes an operator agent that can investigate incidents, review deployment readiness, assess Google Cloud architectures, generate or review Terraform and other infrastructure configuration, analyze spending, and answer documentation-grounded operational questions.

The operator works against a target Google Cloud project and can use project context such as resource inventory, application topology, logging, monitoring, service health, organization policies, and billing. It also has a sandbox for validating configurations against Google Cloud standards.

How it works

Call ask_cloud_operator with a project resource such as projects/my-service-prod and place the user’s request in userQuery. Requests should be forwarded verbatim. Since the operator cannot inspect the caller’s local filesystem, relevant Terraform files, Kubernetes manifests, configuration files, diffs, and logs should be included in the request with their relative paths and contents.

The tool returns a context identifier for continuing the conversation. Pass that contextId on follow-up calls, along with the same agentId when one was selected. New tasks omit the context identifier. When the operator produces code or file changes, write new files to the workspace and apply edits as reviewable diffs.

Sessions can be managed with the other two tools. search_operator_sessions lists sessions for a project, with pagination and session metadata. fetch_operator_session retrieves a session’s summary and conversation turns, using a context ID, session ID, or full session resource name. Session results are ordered oldest first, so finding the newest entries may require paging through the results.

Setup and configuration

Access requires a Google Cloud project, the Google Cloud SDK, and these IAM roles on the user account:

• roles/serviceusage.serviceUsageAdmin, to enable the Cloud Assist APIs
• roles/geminicloudassist.user, to call the Cloud Assist APIs

Authentication uses local Application Default Credentials. Configure them with gcloud auth login followed by gcloud auth application-default login.

The remote MCP endpoint can be configured in supported clients. Antigravity uses a serverUrl and Google credentials. Cursor requires a desktop OAuth client, the redirect URI URI://anysphere.cursor-mcp/oauth/callback, and the cloud-platform scope. The repository also provides a Cloud Operator plugin for Claude Code and ChatGPT Codex; the plugin configures the connection, applies a 30-minute tool timeout, and helps the agent choose when to delegate work.

Tools and capabilities

• ask_cloud_operator: Delegate troubleshooting, root-cause analysis, rollout checks, cost and resource analysis, architecture evaluation, Terraform generation or review, and Google Cloud how-to questions.
• search_operator_sessions: List a project’s Cloud Operator sessions with identifiers, titles, summaries, status, and timestamps.
• fetch_operator_session: Read the conversation and state of a selected session, including additional paginated turns.

The operator can review Terraform, IAM and network configuration, Kubernetes manifests, Helm-related infrastructure, deployment plans, diffs, and error logs when their contents are supplied in the request.

Limitations and notes

The Cloud Operator MCP tools are in Private Preview and restricted to allowlisted projects. Their parameters may change as Gemini Cloud Assist evolves. The configurations in this repository expose only the /mcp/autocloud tools; other Gemini Cloud Assist tools on /mcp, including ask_cloud_assist, design_infra, investigate_issue, invoke_operation, and optimize_costs, are not reachable through these configurations.

The older local Node.js architecture is being replaced by the Remote MCP Server architecture. Use the latest package line supporting the remote server; legacy local configurations are intended only for transition. Google Cloud authentication, project selection, and IAM permissions remain prerequisites for requests.