Connectors · Developer & infrastructure
Google Compute Engine MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Compute Engine and the rest of your systems. It gives your agent 1,018 Google Compute Engine actions (466 reads, 402 writes and 150 that wait for a confirmation) and holds the Google Compute Engine credential itself, so the agent never does. It paces Google Compute Engine's limits and records every call. Connecting Google Compute Engine needs your own Google Compute Engine OAuth app and one admin sign-in.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "gcp_compute_engine.firewall_policies.list", intent: "check which Google Compute Engine account is connected"}# Firewall policies: list · read · 1 upstream call- 1,018actionsin one signed file
- 466readlook, never change
- 402writecreate and update
- 150wait for a yesdestructive, confirmed first
Set up
Connect Google Compute Engine in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Google Compute Engine.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Compute Engine, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
Before the first sign-in, Google Compute Engine needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Compute Engine app to lend you.
access_tokenAccess token from one sign-in with your own OAuth apprefresh_tokenRefresh token from the same sign-in; the access token is renewed from itclient_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Compute Engine API on the…client_secretGoogle OAuth client secret
account { op: "connections.requirements", service: "gcp_compute_engine" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "gcp_compute_engine.firewall_policies.list" }# firewall policies: list · read · 1 upstream callcheck { action: "gcp_compute_engine.instances.insert", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Google Compute Engine at a glance
- Sign-in
- OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Compute Engine, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
- You provide
access_tokenrefresh_tokenclient_idclient_secret- Limits we pace to
- 1,200 calls a minute, per connection
- API covered
- Google Compute Engine (VMs, disks, networks, load balancing) API compute v1 (Discovery revision 20261007)
compute.googleapis.com/compute/v1 - Built from
- Google Compute Engine's documentation, read 22 October 2026googleapis.comcloud.google.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 454 of 466 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 1, so ask can line Google Compute Engine up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Google Compute Engine.
1,018 actions in 131 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 466readlook, never change
- 402writecreate and update
- 150destructivewait for a confirmation
Instances
5111 read · 33 write · 7 destructive
Instances: list · Instances: insert · Instances: get · Instances: update
Instance group managers
246 read · 13 write · 5 destructive
Instance group managers: aggregated list · Instance group managers: create instances · Instance group managers: insert · Instance group managers: list
Region instance group managers
235 read · 13 write · 5 destructive
Region instance group managers: create instances · Region instance group managers: insert · Region instance group managers: list · Region instance group managers: list errors
Routers
2212 read · 7 write · 3 destructive
Routers: aggregated list · Routers: insert · Routers: list · Routers: list bgp routes
Network firewall policies
218 read · 9 write · 4 destructive
Network firewall policies: aggregated list · Network firewall policies: insert · Network firewall policies: list · Network firewall policies: test iam permissions
Disks
205 read · 11 write · 4 destructive
Disks: list · Disks: insert · Disks: get · Disks: delete
Firewall policies
187 read · 8 write · 3 destructive
Firewall policies: insert · Firewall policies: list · Firewall policies: list associations · Firewall policies: test iam permissions
Region disks
184 read · 10 write · 4 destructive
Region disks: bulk insert · Region disks: create snapshot · Region disks: insert · Region disks: list
123 more areas · 821 actions
- Region network firewall policies 18
- Backend services 17
- Organization security policies 16
- Node groups 15
- Backend buckets 14
- Projects 14
- Networks 13
- Target pools 13
- Region backend services 12
- Security policies 12
- Subnetworks 12
- Images 11
- Reservations 11
- Target https proxies 11
- Instance groups 10
- Interconnect groups 10
- Region security policies 10
- Storage pools 10
- Target SSL proxies 10
- URL maps 10
- Instant snapshots 9
- Interconnect attachment groups 9
- Network attachments 9
- Network endpoint groups 9
- Region backend buckets 9
- Region snapshots 9
- Resource policies 9
- Service attachments 9
- Snapshots 9
- Addresses 8
- Autoscalers 8
- Forwarding rules 8
- Health checks 8
- Instance templates 8
- Interconnects 8
- Licenses 8
- Machine images 8
- Node templates 8
- Public delegated prefixes 8
- Region composite health checks 8
- Region health sources 8
- Region instant snapshots 8
- Reservation sub blocks 8
- Target TCP proxies 8
- VPN gateways 8
- Firewalls 7
- Future reservations 7
- Global addresses 7
- Global forwarding rules 7
- Global network endpoint groups 7
- HTTP health checks 7
- Https health checks 7
- Instant snapshot groups 7
- Interconnect attachments 7
- Packet mirrorings 7
- Public advertised prefixes 7
- Region autoscalers 7
- Region health aggregation policies 7
- Region health check services 7
- Region health checks 7
- Region instant snapshot groups 7
- Region network endpoint groups 7
- Region target https proxies 7
- Region URL maps 7
- Rollouts 7
- SSL policies 7
- Target HTTP proxies 7
- Target instances 7
- External VPN gateways 6
- Global VM extension policies 6
- Region notification endpoints 6
- Region SSL policies 6
- Reservation blocks 6
- Target VPN gateways 6
- VPN tunnels 6
- Cross site networks 5
- Global operations 5
- Global public delegated prefixes 5
- Instance group manager resize requests 5
- Network edge security services 5
- Region commitments 5
- Region instance group manager resize requests 5
- Region instance groups 5
- Region target HTTP proxies 5
- Reservation slots 5
- Routes 5
- SSL certificates 5
- Target GRPC proxies 5
- Wire groups 5
- Zone VM extension policies 5
- License codes 4
- Region instance templates 4
- Region operations 4
- Region SSL certificates 4
- Region target TCP proxies 4
- Rollout plans 4
- Zone operations 4
- Accelerator types 3
- Advice 3
- Disk types 3
- Global organization operations 3
- Hosts 3
- Machine types 3
- Node types 3
- Preview features 3
- Storage pool types 3
- Global frontend settings 2
- Image views 2
- Instance settings 2
- Interconnect locations 2
- Interconnect remote locations 2
- Managed rulesets 2
- Network profiles 2
- Region disk types 2
- Region snapshot settings 2
- Regions 2
- Reliability risks 2
- Snapshot settings 2
- Zones 2
- Image family views 1
- Project views 1
- Region instances 1
- Region zones 1
Top actions
The Google Compute Engine API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 49 of Google Compute Engine's 56 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
gcp_compute_engine.instances.listInstances: list | Retrieves the list of instances contained within the specified zone. | read | infra.instance.list18 connectors |
gcp_compute_engine.instances.insertInstances: insert | Creates an instance resource in the specified project using the data included in the request. | write | infra.instance.create10 connectors |
gcp_compute_engine.instances.deleteInstances: delete | Deletes the specified Instance resource. | destructive | infra.instance.delete13 connectors |
gcp_compute_engine.regions.listRegions: list | Retrieves the list of region resources available to the specified project. | read | infra.region.list16 connectors |
gcp_compute_engine.snapshots.listSnapshots: list | Retrieves the list of Snapshot resources contained within the specified project. | read | infra.snapshot.list12 connectors |
gcp_compute_engine.disks.listDisks: list | Retrieves a list of persistent disks contained within the specified zone. | read | infra.volume.list10 connectors |
gcp_compute_engine.addresses.listAddresses: list | Retrieves a list of addresses contained within the specified region. | read | infra.ip_address.list9 connectors |
gcp_compute_engine.snapshots.insertSnapshots: insert | Creates a snapshot in the specified project using the data included in the request. | write | infra.snapshot.create9 connectors |
gcp_compute_engine.disks.insertDisks: insert | Creates a persistent disk in the specified project using the data in the request. | write | infra.volume.create8 connectors |
gcp_compute_engine.networks.listNetworks: list | Retrieves the list of networks available to the specified project. | read | infra.network.list6 connectors |
gcp_compute_engine.addresses.insertAddresses: insert | Creates an address resource in the specified project by using the data included in the request. | write | infra.ip_address.create6 connectors |
gcp_compute_engine.networks.insertNetworks: insert | Creates a network in the specified project using the data included in the request. | write | infra.network.create5 connectors |
Try it
Prompts to paste into Claude.
Each one names the Google Compute Engine actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Firewall policies: list in Google Compute Engine and tell me what stands out.
calls
gcp_compute_engine.firewall_policies.list - Writewrite
Instances: insert in Google Compute Engine. Show me exactly what you will send before you save it.
calls
gcp_compute_engine.instances.insert
Governance for Google Compute Engine
Destructive actions wait for a yes.
150 Google Compute Engine actions are destructive. The first 10:
- Instances: delete
gcp_compute_engine.instances.delete - Disks: delete
gcp_compute_engine.disks.delete - Snapshots: delete
gcp_compute_engine.snapshots.delete - Networks: delete
gcp_compute_engine.networks.delete - Addresses: delete
gcp_compute_engine.addresses.delete - Images: delete
gcp_compute_engine.images.delete - Subnetworks: delete
gcp_compute_engine.subnetworks.delete - Firewalls: delete
gcp_compute_engine.firewalls.delete - Reservations: delete
gcp_compute_engine.reservations.delete - Instance templates: delete
gcp_compute_engine.instance_templates.delete
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Instances: delete?
intent: the user asked me to instances: delete
account { op: "keys.create", name: "gcp-compute-engine-agent", allowed_actions: ["gcp_compute_engine.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "gcp_compute_engine.instances.delete", approver: "[email protected]" }, { match: "gcp_compute_engine.disks.delete", approver: "[email protected]" }, { match: "gcp_compute_engine.snapshots.delete", approver: "[email protected]" } ]}Cost
What Google Compute Engine costs on actionlake.
Every Google Compute Engine action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Compute Engine refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 1,018 Google Compute Engine actions
- 148actions pageeach page of a long list is one call
- 454reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Google Compute Engine action.
1,018 actions by area: the id your agent calls, what it does, and its effect.
Instances51
gcp_compute_engine.instances.getInstances: getreadgcp_compute_engine.instances.insertInstances: insertwritegcp_compute_engine.instances.listInstances: listreadgcp_compute_engine.instances.updateInstances: updatewritegcp_compute_engine.instances.add_access_configInstances: add access configwritegcp_compute_engine.instances.add_network_interfaceInstances: add network interfacewrite- and 45 more in this area
Instance group managers24
gcp_compute_engine.instance_group_managers.aggregated_listInstance group managers: aggregated listreadgcp_compute_engine.instance_group_managers.create_instancesInstance group managers: create instanceswritegcp_compute_engine.instance_group_managers.insertInstance group managers: insertwritegcp_compute_engine.instance_group_managers.listInstance group managers: listreadgcp_compute_engine.instance_group_managers.abandon_instancesInstance group managers: abandon instancesdestructivegcp_compute_engine.instance_group_managers.apply_updates_to_instancesInstance group managers: apply updates to instanceswrite- and 18 more in this area
Region instance group managers23
gcp_compute_engine.region_instance_group_managers.create_instancesRegion instance group managers: create instanceswritegcp_compute_engine.region_instance_group_managers.insertRegion instance group managers: insertwritegcp_compute_engine.region_instance_group_managers.listRegion instance group managers: listreadgcp_compute_engine.region_instance_group_managers.list_errorsRegion instance group managers: list errorsreadgcp_compute_engine.region_instance_group_managers.abandon_instancesRegion instance group managers: abandon instancesdestructivegcp_compute_engine.region_instance_group_managers.apply_updates_to_instancesRegion instance group managers: apply updates to instanceswrite- and 17 more in this area
Routers22
gcp_compute_engine.routers.aggregated_listRouters: aggregated listreadgcp_compute_engine.routers.insertRouters: insertwritegcp_compute_engine.routers.listRouters: listreadgcp_compute_engine.routers.list_bgp_routesRouters: list bgp routesreadgcp_compute_engine.routers.deleteRouters: deletedestructivegcp_compute_engine.routers.delete_named_setRouters: delete named setdestructive- and 16 more in this area
Network firewall policies21
gcp_compute_engine.network_firewall_policies.aggregated_listNetwork firewall policies: aggregated listreadgcp_compute_engine.network_firewall_policies.insertNetwork firewall policies: insertwritegcp_compute_engine.network_firewall_policies.listNetwork firewall policies: listreadgcp_compute_engine.network_firewall_policies.test_iam_permissionsNetwork firewall policies: test iam permissionsreadgcp_compute_engine.network_firewall_policies.add_associationNetwork firewall policies: add associationwritegcp_compute_engine.network_firewall_policies.add_packet_mirroring_ruleNetwork firewall policies: add packet mirroring rulewrite- and 15 more in this area
Disks20
gcp_compute_engine.disks.deleteDisks: deletedestructivegcp_compute_engine.disks.getDisks: getreadgcp_compute_engine.disks.insertDisks: insertwritegcp_compute_engine.disks.listDisks: listreadgcp_compute_engine.disks.add_resource_policiesDisks: add resource policieswritegcp_compute_engine.disks.aggregated_listDisks: aggregated listread- and 14 more in this area
Firewall policies18
gcp_compute_engine.firewall_policies.insertFirewall policies: insertwritegcp_compute_engine.firewall_policies.listFirewall policies: listreadgcp_compute_engine.firewall_policies.list_associationsFirewall policies: list associationsreadgcp_compute_engine.firewall_policies.test_iam_permissionsFirewall policies: test iam permissionsreadgcp_compute_engine.firewall_policies.add_associationFirewall policies: add associationwritegcp_compute_engine.firewall_policies.add_ruleFirewall policies: add rulewrite- and 12 more in this area
Region disks18
gcp_compute_engine.region_disks.bulk_insertRegion disks: bulk insertwritegcp_compute_engine.region_disks.create_snapshotRegion disks: create snapshotwritegcp_compute_engine.region_disks.insertRegion disks: insertwritegcp_compute_engine.region_disks.listRegion disks: listreadgcp_compute_engine.region_disks.add_resource_policiesRegion disks: add resource policieswritegcp_compute_engine.region_disks.deleteRegion disks: deletedestructive- and 12 more in this area
Region network firewall policies18
gcp_compute_engine.region_network_firewall_policies.add_associationRegion network firewall policies: add associationwritegcp_compute_engine.region_network_firewall_policies.insertRegion network firewall policies: insertwritegcp_compute_engine.region_network_firewall_policies.listRegion network firewall policies: listreadgcp_compute_engine.region_network_firewall_policies.test_iam_permissionsRegion network firewall policies: test iam permissionsreadgcp_compute_engine.region_network_firewall_policies.add_ruleRegion network firewall policies: add rulewritegcp_compute_engine.region_network_firewall_policies.clone_rulesRegion network firewall policies: clone ruleswrite- and 12 more in this area
Backend services17
gcp_compute_engine.backend_services.aggregated_listBackend services: aggregated listreadgcp_compute_engine.backend_services.insertBackend services: insertwritegcp_compute_engine.backend_services.listBackend services: listreadgcp_compute_engine.backend_services.list_usableBackend services: list usablereadgcp_compute_engine.backend_services.add_signed_url_keyBackend services: add signed url keywritegcp_compute_engine.backend_services.deleteBackend services: deletedestructive- and 11 more in this area
Organization security policies16
gcp_compute_engine.organization_security_policies.insertOrganization security policies: insertwritegcp_compute_engine.organization_security_policies.listOrganization security policies: listreadgcp_compute_engine.organization_security_policies.list_associationsOrganization security policies: list associationsreadgcp_compute_engine.organization_security_policies.list_preconfigured_expression_setsOrganization security policies: list preconfigured expression setsreadgcp_compute_engine.organization_security_policies.add_associationOrganization security policies: add associationwritegcp_compute_engine.organization_security_policies.add_ruleOrganization security policies: add rulewrite- and 10 more in this area
Node groups15
gcp_compute_engine.node_groups.aggregated_listNode groups: aggregated listreadgcp_compute_engine.node_groups.insertNode groups: insertwritegcp_compute_engine.node_groups.listNode groups: listreadgcp_compute_engine.node_groups.list_nodesNode groups: list nodesreadgcp_compute_engine.node_groups.add_nodesNode groups: add nodeswritegcp_compute_engine.node_groups.deleteNode groups: deletedestructive- and 9 more in this area
Backend buckets14
gcp_compute_engine.backend_buckets.aggregated_listBackend buckets: aggregated listreadgcp_compute_engine.backend_buckets.insertBackend buckets: insertwritegcp_compute_engine.backend_buckets.listBackend buckets: listreadgcp_compute_engine.backend_buckets.list_usableBackend buckets: list usablereadgcp_compute_engine.backend_buckets.add_signed_url_keyBackend buckets: add signed url keywritegcp_compute_engine.backend_buckets.deleteBackend buckets: deletedestructive- and 8 more in this area
Projects14
gcp_compute_engine.projects.disable_xpn_hostProjects: disable xpn hostwritegcp_compute_engine.projects.disable_xpn_resourceProjects: disable xpn resourcewritegcp_compute_engine.projects.enable_xpn_hostProjects: enable xpn hostwritegcp_compute_engine.projects.list_xpn_hostsProjects: list xpn hostsreadgcp_compute_engine.projects.enable_xpn_resourceProjects: enable xpn resourcewritegcp_compute_engine.projects.getProjects: getread- and 8 more in this area
Networks13
gcp_compute_engine.networks.getNetworks: getreadgcp_compute_engine.networks.insertNetworks: insertwritegcp_compute_engine.networks.listNetworks: listreadgcp_compute_engine.networks.patchNetworks: patchwritegcp_compute_engine.networks.add_peeringNetworks: add peeringwritegcp_compute_engine.networks.cancel_request_remove_peeringNetworks: cancel request remove peeringwrite- and 7 more in this area
Target pools13
gcp_compute_engine.target_pools.aggregated_listTarget pools: aggregated listreadgcp_compute_engine.target_pools.insertTarget pools: insertwritegcp_compute_engine.target_pools.listTarget pools: listreadgcp_compute_engine.target_pools.test_iam_permissionsTarget pools: test iam permissionsreadgcp_compute_engine.target_pools.add_health_checkTarget pools: add health checkwritegcp_compute_engine.target_pools.add_instanceTarget pools: add instancewrite- and 7 more in this area
Region backend services12
gcp_compute_engine.region_backend_services.insertRegion backend services: insertwritegcp_compute_engine.region_backend_services.listRegion backend services: listreadgcp_compute_engine.region_backend_services.list_usableRegion backend services: list usablereadgcp_compute_engine.region_backend_services.test_iam_permissionsRegion backend services: test iam permissionsreadgcp_compute_engine.region_backend_services.deleteRegion backend services: deletedestructivegcp_compute_engine.region_backend_services.getRegion backend services: getread- and 6 more in this area
Security policies12
gcp_compute_engine.security_policies.aggregated_listSecurity policies: aggregated listreadgcp_compute_engine.security_policies.insertSecurity policies: insertwritegcp_compute_engine.security_policies.listSecurity policies: listreadgcp_compute_engine.security_policies.list_preconfigured_expression_setsSecurity policies: list preconfigured expression setsreadgcp_compute_engine.security_policies.add_ruleSecurity policies: add rulewritegcp_compute_engine.security_policies.deleteSecurity policies: deletedestructive- and 6 more in this area
Subnetworks12
gcp_compute_engine.subnetworks.getSubnetworks: getreadgcp_compute_engine.subnetworks.insertSubnetworks: insertwritegcp_compute_engine.subnetworks.listSubnetworks: listreadgcp_compute_engine.subnetworks.patchSubnetworks: patchwritegcp_compute_engine.subnetworks.aggregated_listSubnetworks: aggregated listreadgcp_compute_engine.subnetworks.deleteSubnetworks: deletedestructive- and 6 more in this area
Images11
gcp_compute_engine.images.getImages: getreadgcp_compute_engine.images.insertImages: insertwritegcp_compute_engine.images.listImages: listreadgcp_compute_engine.images.patchImages: patchwritegcp_compute_engine.images.deleteImages: deletedestructivegcp_compute_engine.images.deprecateImages: deprecatewrite- and 5 more in this area
Reservations11
gcp_compute_engine.reservations.getReservations: getreadgcp_compute_engine.reservations.insertReservations: insertwritegcp_compute_engine.reservations.listReservations: listreadgcp_compute_engine.reservations.updateReservations: updatewritegcp_compute_engine.reservations.aggregated_listReservations: aggregated listreadgcp_compute_engine.reservations.deleteReservations: deletedestructive- and 5 more in this area
Target https proxies11
gcp_compute_engine.target_https_proxies.aggregated_listTarget https proxies: aggregated listreadgcp_compute_engine.target_https_proxies.getTarget https proxies: getreadgcp_compute_engine.target_https_proxies.insertTarget https proxies: insertwritegcp_compute_engine.target_https_proxies.listTarget https proxies: listreadgcp_compute_engine.target_https_proxies.deleteTarget https proxies: deletedestructivegcp_compute_engine.target_https_proxies.patchTarget https proxies: patchwrite- and 5 more in this area
Instance groups10
gcp_compute_engine.instance_groups.aggregated_listInstance groups: aggregated listreadgcp_compute_engine.instance_groups.insertInstance groups: insertwritegcp_compute_engine.instance_groups.listInstance groups: listreadgcp_compute_engine.instance_groups.list_instancesInstance groups: list instancesreadgcp_compute_engine.instance_groups.add_instancesInstance groups: add instanceswritegcp_compute_engine.instance_groups.deleteInstance groups: deletedestructive- and 4 more in this area
Interconnect groups10
gcp_compute_engine.interconnect_groups.create_membersInterconnect groups: create memberswritegcp_compute_engine.interconnect_groups.insertInterconnect groups: insertwritegcp_compute_engine.interconnect_groups.listInterconnect groups: listreadgcp_compute_engine.interconnect_groups.test_iam_permissionsInterconnect groups: test iam permissionsreadgcp_compute_engine.interconnect_groups.deleteInterconnect groups: deletedestructivegcp_compute_engine.interconnect_groups.getInterconnect groups: getread- and 4 more in this area
Region security policies10
gcp_compute_engine.region_security_policies.add_ruleRegion security policies: add rulewritegcp_compute_engine.region_security_policies.getRegion security policies: getreadgcp_compute_engine.region_security_policies.insertRegion security policies: insertwritegcp_compute_engine.region_security_policies.listRegion security policies: listreadgcp_compute_engine.region_security_policies.deleteRegion security policies: deletedestructivegcp_compute_engine.region_security_policies.get_ruleRegion security policies: get ruleread- and 4 more in this area
Storage pools10
gcp_compute_engine.storage_pools.aggregated_listStorage pools: aggregated listreadgcp_compute_engine.storage_pools.insertStorage pools: insertwritegcp_compute_engine.storage_pools.listStorage pools: listreadgcp_compute_engine.storage_pools.list_disksStorage pools: list disksreadgcp_compute_engine.storage_pools.deleteStorage pools: deletedestructivegcp_compute_engine.storage_pools.getStorage pools: getread- and 4 more in this area
Target SSL proxies10
gcp_compute_engine.target_ssl_proxies.getTarget ssl proxies: getreadgcp_compute_engine.target_ssl_proxies.insertTarget ssl proxies: insertwritegcp_compute_engine.target_ssl_proxies.listTarget ssl proxies: listreadgcp_compute_engine.target_ssl_proxies.test_iam_permissionsTarget ssl proxies: test iam permissionsreadgcp_compute_engine.target_ssl_proxies.deleteTarget ssl proxies: deletedestructivegcp_compute_engine.target_ssl_proxies.set_backend_serviceTarget ssl proxies: set backend servicewrite- and 4 more in this area
URL maps10
gcp_compute_engine.url_maps.aggregated_listUrl maps: aggregated listreadgcp_compute_engine.url_maps.insertUrl maps: insertwritegcp_compute_engine.url_maps.listUrl maps: listreadgcp_compute_engine.url_maps.test_iam_permissionsUrl maps: test iam permissionsreadgcp_compute_engine.url_maps.deleteUrl maps: deletedestructivegcp_compute_engine.url_maps.getUrl maps: getread- and 4 more in this area
Instant snapshots9
gcp_compute_engine.instant_snapshots.aggregated_listInstant snapshots: aggregated listreadgcp_compute_engine.instant_snapshots.insertInstant snapshots: insertwritegcp_compute_engine.instant_snapshots.listInstant snapshots: listreadgcp_compute_engine.instant_snapshots.test_iam_permissionsInstant snapshots: test iam permissionsreadgcp_compute_engine.instant_snapshots.deleteInstant snapshots: deletedestructivegcp_compute_engine.instant_snapshots.getInstant snapshots: getread- and 3 more in this area
Interconnect attachment groups9
gcp_compute_engine.interconnect_attachment_groups.getInterconnect attachment groups: getreadgcp_compute_engine.interconnect_attachment_groups.insertInterconnect attachment groups: insertwritegcp_compute_engine.interconnect_attachment_groups.listInterconnect attachment groups: listreadgcp_compute_engine.interconnect_attachment_groups.test_iam_permissionsInterconnect attachment groups: test iam permissionsreadgcp_compute_engine.interconnect_attachment_groups.deleteInterconnect attachment groups: deletedestructivegcp_compute_engine.interconnect_attachment_groups.get_iam_policyInterconnect attachment groups: get iam policyread- and 3 more in this area
Network attachments 9Network endpoint groups 9Region backend buckets 9Region snapshots 9Resource policies 9Service attachments 9Snapshots 9Addresses 8Autoscalers 8Forwarding rules 8Health checks 8Instance templates 8Interconnects 8Licenses 8Machine images 8Node templates 8Public delegated prefixes 8Region composite health checks 8Region health sources 8Region instant snapshots 8Reservation sub blocks 8Target TCP proxies 8VPN gateways 8Firewalls 7Future reservations 7Global addresses 7Global forwarding rules 7Global network endpoint groups 7HTTP health checks 7Https health checks 7Instant snapshot groups 7Interconnect attachments 7Packet mirrorings 7Public advertised prefixes 7Region autoscalers 7Region health aggregation policies 7Region health check services 7Region health checks 7Region instant snapshot groups 7Region network endpoint groups 7Region target https proxies 7Region URL maps 7Rollouts 7SSL policies 7Target HTTP proxies 7Target instances 7External VPN gateways 6Global VM extension policies 6Region notification endpoints 6Region SSL policies 6Reservation blocks 6Target VPN gateways 6VPN tunnels 6Cross site networks 5Global operations 5Global public delegated prefixes 5Instance group manager resize requests 5Network edge security services 5Region commitments 5Region instance group manager resize requests 5Region instance groups 5Region target HTTP proxies 5Reservation slots 5Routes 5SSL certificates 5Target GRPC proxies 5Wire groups 5Zone VM extension policies 5License codes 4Region instance templates 4Region operations 4Region SSL certificates 4Region target TCP proxies 4Rollout plans 4Zone operations 4Accelerator types 3Advice 3Disk types 3Global organization operations 3Hosts 3Machine types 3Node types 3Preview features 3Storage pool types 3Global frontend settings 2Image views 2Instance settings 2Interconnect locations 2Interconnect remote locations 2Managed rulesets 2Network profiles 2Region disk types 2Region snapshot settings 2Regions 2Reliability risks 2Snapshot settings 2Zones 2Image family views 1Project views 1Region instances 1Region zones 1
This index shows a sample of each area. All 1,018 actions, with their inputs and prices, are in the catalogue, which a free sandbox key can search.
Questions
The Google Compute Engine MCP server, answered.
Is there a Google Compute Engine MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 1,018 Google Compute Engine actions across instances, instance group managers, region instance group managers and routers, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Compute Engine.
What do I need to connect Google Compute Engine?
Your own Google Compute Engine OAuth app, registered with Google Compute Engine (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Compute Engine app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gcp_compute_engine" } lists exactly what to paste.
Can an AI agent delete or change things in Google Compute Engine?
Only if its key allows it, and only with an explicit confirmation. 150 Google Compute Engine actions are destructive, including instances: delete, disks: delete and snapshots: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Google Compute Engine API limit?
actionlake paces every call to the limits in the Google Compute Engine service file: 1,200 calls a minute per connection. Repeated reads are answered from cache (454 Google Compute Engine actions can be), which never reaches Google Compute Engine.
What does a Google Compute Engine action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (148 Google Compute Engine actions page). Cache hits, searches, dry runs and calls Google Compute Engine refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Google Compute Engine API does it cover?
The Google Compute Engine (VMs, disks, networks, load balancing) API compute v1 (Discovery revision 20261007) at compute.googleapis.com/compute/v1. It is built from Google Compute Engine's documentation as read on 22 October 2026. 1,018 actions in 131 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my Google Compute Engine data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Compute Engine credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Google Compute Engine today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.
