google-compute-engine

name

google-compute-engine

description

Google Compute Engine is an infrastructure-as-a-service platform that provides scalable virtual machines, networking, and storage for running workloads in the cloud, enabling developers and IT teams to deploy, manage, and automate applications with fine-grained control over compute resources. Read and write Google Compute Engine data through One: instances, instancegroupmanagers, securitypolicies, firewallpolicies, backendbuckets, disks and more, 977 actions with real parameter documentation. Use whenever the user asks to look something up in Google Compute Engine, create or update a record there, or build code against the Google Compute Engine API.

Google Compute Engine through One

Google Compute Engine is an infrastructure-as-a-service platform that provides scalable virtual machines, networking, and storage for running workloads in the cloud, enabling developers and IT teams to deploy, manage, and automate applications with fine-grained control over compute resources.

One exposes Google Compute Engine through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform google-compute-engine if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Google Compute Engine is connected. If it is missing, the user has not connected it: say so and point them at rather than reaching for raw HTTP.