Connectors · Developer & infrastructure
Google Kubernetes Engine MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Kubernetes Engine and the rest of your systems. It gives your agent 71 Google Kubernetes Engine actions (22 reads, 43 writes and 6 that wait for a confirmation) and holds the Google Kubernetes Engine credential itself, so the agent never does. It paces Google Kubernetes Engine's limits and records every call. Connecting Google Kubernetes Engine needs your own Google Kubernetes 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_gke.projects_aggregated_usable_subnetworks.list", intent: "check which Google Kubernetes Engine account is connected"}# Projects aggregated usable subnetworks: list · read · 1 upstream call- 71actionsin one signed file
- 22readlook, never change
- 43writecreate and update
- 6wait for a yesdestructive, confirmed first
Set up
Connect Google Kubernetes 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 Kubernetes Engine.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Kubernetes 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 Kubernetes Engine needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Kubernetes 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 Kubernetes Engine API on…client_secretGoogle OAuth client secret
account { op: "connections.requirements", service: "gcp_gke" } # 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_gke.projects_aggregated_usable_subnetworks.list" }# projects aggregated usable subnetworks: list · read · 1 upstream callcheck { action: "gcp_gke.projects_locations_clusters.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Google Kubernetes Engine at a glance
- Sign-in
- OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Kubernetes 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
- 600 calls a minute, per connection
- API covered
- Google Kubernetes Engine (clusters, node pools, upgrades, operations, server config) API container v1 (Discovery revision 20260922)
container.googleapis.com - Built from
- Google Kubernetes Engine's documentation, read 23 October 2026container.googleapis.comcloud.google.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 18 of 22 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 1, so ask can line Google Kubernetes 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 Kubernetes Engine.
71 actions in 10 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 22readlook, never change
- 43writecreate and update
- 6destructivewait for a confirmation
Projects locations clusters
215 read · 15 write · 1 destructive
Projects locations clusters: list · Projects locations clusters: create · Projects locations clusters: get · Projects locations clusters: update
Projects zones clusters
193 read · 15 write · 1 destructive
Projects zones clusters: create · Projects zones clusters: list · Projects zones clusters: addons · Projects zones clusters: complete control plane upgrade
Projects locations clusters node pools
113 read · 7 write · 1 destructive
Projects locations clusters node pools: create · Projects locations clusters node pools: list · Projects locations clusters node pools: complete upgrade · Projects locations clusters node pools: fetch node pool upgrade info
Projects zones clusters node pools
103 read · 6 write · 1 destructive
Projects zones clusters node pools: create · Projects zones clusters node pools: list · Projects zones clusters node pools: autoscaling · Projects zones clusters node pools: fetch node pool upgrade info
Projects locations operations
32 read · 0 write · 1 destructive
Projects locations operations: list · Projects locations operations: get · Projects locations operations: cancel
Projects zones operations
32 read · 0 write · 1 destructive
Projects zones operations: list · Projects zones operations: get · Projects zones operations: cancel
Projects aggregated usable subnetworks
11 read · 0 write · 0 destructive
Projects aggregated usable subnetworks: list
Projects locations
11 read · 0 write · 0 destructive
Projects locations: get server config
2 more areas · 2 actions
- Projects locations clusters well known 1
- Projects zones 1
Top actions
The Google Kubernetes Engine API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 6 of Google Kubernetes Engine's 6 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_gke.projects_locations_clusters.listProjects locations clusters: list | Lists all clusters owned by a project in either the specified zone or all zones. | read | infra.container_cluster.list6 connectors |
gcp_gke.projects_locations_clusters.createProjects locations clusters: create | Creates a cluster, consisting of the specified number and type of Google Compute Engine instances. | write | infra.container_cluster.create6 connectors |
gcp_gke.projects_locations_clusters.updateProjects locations clusters: update | Updates the settings of a specific cluster. | write | infra.container_cluster.update6 connectors |
gcp_gke.projects_locations_clusters.deleteProjects locations clusters: delete | Deletes the cluster, including the Kubernetes endpoint and all worker nodes. | destructive | infra.container_cluster.delete7 connectors |
gcp_gke.projects_locations_clusters_node_pools.createProjects locations clusters node pools: create | Creates a node pool for a cluster. | write | this connector |
Try it
Prompts to paste into Claude.
Each one names the Google Kubernetes Engine actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Projects aggregated usable subnetworks: list in Google Kubernetes Engine and tell me what stands out.
calls
gcp_gke.projects_aggregated_usable_subnetworks.list - Writewrite
Projects locations clusters: create in Google Kubernetes Engine. Show me exactly what you will send before you save it.
calls
gcp_gke.projects_locations_clusters.create
Governance for Google Kubernetes Engine
Destructive actions wait for a yes.
6 Google Kubernetes Engine actions are destructive. These are all of them:
- Projects locations clusters: delete
gcp_gke.projects_locations_clusters.delete - Projects locations operations: cancel
gcp_gke.projects_locations_operations.cancel - Projects locations clusters node pools: delete
gcp_gke.projects_locations_clusters_node_pools.delete - Projects zones clusters: delete
gcp_gke.projects_zones_clusters.delete - Projects zones operations: cancel
gcp_gke.projects_zones_operations.cancel - Projects zones clusters node pools: delete
gcp_gke.projects_zones_clusters_node_pools.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.
Projects locations clusters: delete?
intent: the user asked me to projects locations clusters: delete
account { op: "keys.create", name: "gcp-gke-agent", allowed_actions: ["gcp_gke.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "gcp_gke.projects_locations_clusters.delete", approver: "[email protected]" }, { match: "gcp_gke.projects_locations_operations.cancel", approver: "[email protected]" }, { match: "gcp_gke.projects_locations_clusters_node_pools.delete", approver: "[email protected]" } ]}Cost
What Google Kubernetes Engine costs on actionlake.
Every Google Kubernetes Engine action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Kubernetes 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 71 Google Kubernetes Engine actions
- 1actions pageeach page of a long list is one call
- 18reads 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 Kubernetes Engine action.
71 actions by area: the id your agent calls, what it does, and its effect.
Projects locations clusters21
gcp_gke.projects_locations_clusters.check_autopilot_compatibilityProjects locations clusters: check autopilot compatibilityreadgcp_gke.projects_locations_clusters.complete_control_plane_upgradeProjects locations clusters: complete control plane upgradewritegcp_gke.projects_locations_clusters.complete_ip_rotationProjects locations clusters: complete ip rotationwritegcp_gke.projects_locations_clusters.createProjects locations clusters: createwritegcp_gke.projects_locations_clusters.deleteProjects locations clusters: deletedestructivegcp_gke.projects_locations_clusters.fetch_cluster_upgrade_infoProjects locations clusters: fetch cluster upgrade inforeadgcp_gke.projects_locations_clusters.getProjects locations clusters: getreadgcp_gke.projects_locations_clusters.get_jwksProjects locations clusters: get jwksreadgcp_gke.projects_locations_clusters.listProjects locations clusters: listreadgcp_gke.projects_locations_clusters.set_addonsProjects locations clusters: set addonswritegcp_gke.projects_locations_clusters.set_legacy_abacProjects locations clusters: set legacy abacwritegcp_gke.projects_locations_clusters.set_locationsProjects locations clusters: set locationswritegcp_gke.projects_locations_clusters.set_loggingProjects locations clusters: set loggingwritegcp_gke.projects_locations_clusters.set_maintenance_policyProjects locations clusters: set maintenance policywritegcp_gke.projects_locations_clusters.set_master_authProjects locations clusters: set master authwritegcp_gke.projects_locations_clusters.set_monitoringProjects locations clusters: set monitoringwritegcp_gke.projects_locations_clusters.set_network_policyProjects locations clusters: set network policywritegcp_gke.projects_locations_clusters.set_resource_labelsProjects locations clusters: set resource labelswritegcp_gke.projects_locations_clusters.start_ip_rotationProjects locations clusters: start ip rotationwritegcp_gke.projects_locations_clusters.updateProjects locations clusters: updatewritegcp_gke.projects_locations_clusters.update_masterProjects locations clusters: update masterwrite
Projects zones clusters19
gcp_gke.projects_zones_clusters.addonsProjects zones clusters: addonswritegcp_gke.projects_zones_clusters.complete_control_plane_upgradeProjects zones clusters: complete control plane upgradewritegcp_gke.projects_zones_clusters.complete_ip_rotationProjects zones clusters: complete ip rotationwritegcp_gke.projects_zones_clusters.createProjects zones clusters: createwritegcp_gke.projects_zones_clusters.deleteProjects zones clusters: deletedestructivegcp_gke.projects_zones_clusters.fetch_cluster_upgrade_infoProjects zones clusters: fetch cluster upgrade inforeadgcp_gke.projects_zones_clusters.getProjects zones clusters: getreadgcp_gke.projects_zones_clusters.legacy_abacProjects zones clusters: legacy abacwritegcp_gke.projects_zones_clusters.listProjects zones clusters: listreadgcp_gke.projects_zones_clusters.locationsProjects zones clusters: locationswritegcp_gke.projects_zones_clusters.loggingProjects zones clusters: loggingwritegcp_gke.projects_zones_clusters.masterProjects zones clusters: masterwritegcp_gke.projects_zones_clusters.monitoringProjects zones clusters: monitoringwritegcp_gke.projects_zones_clusters.resource_labelsProjects zones clusters: resource labelswritegcp_gke.projects_zones_clusters.set_maintenance_policyProjects zones clusters: set maintenance policywritegcp_gke.projects_zones_clusters.set_master_authProjects zones clusters: set master authwritegcp_gke.projects_zones_clusters.set_network_policyProjects zones clusters: set network policywritegcp_gke.projects_zones_clusters.start_ip_rotationProjects zones clusters: start ip rotationwritegcp_gke.projects_zones_clusters.updateProjects zones clusters: updatewrite
Projects locations clusters node pools11
gcp_gke.projects_locations_clusters_node_pools.complete_upgradeProjects locations clusters node pools: complete upgradewritegcp_gke.projects_locations_clusters_node_pools.createProjects locations clusters node pools: createwritegcp_gke.projects_locations_clusters_node_pools.deleteProjects locations clusters node pools: deletedestructivegcp_gke.projects_locations_clusters_node_pools.fetch_node_pool_upgrade_infoProjects locations clusters node pools: fetch node pool upgrade inforeadgcp_gke.projects_locations_clusters_node_pools.getProjects locations clusters node pools: getreadgcp_gke.projects_locations_clusters_node_pools.listProjects locations clusters node pools: listreadgcp_gke.projects_locations_clusters_node_pools.rollbackProjects locations clusters node pools: rollbackwritegcp_gke.projects_locations_clusters_node_pools.set_autoscalingProjects locations clusters node pools: set autoscalingwritegcp_gke.projects_locations_clusters_node_pools.set_managementProjects locations clusters node pools: set managementwritegcp_gke.projects_locations_clusters_node_pools.set_sizeProjects locations clusters node pools: set sizewritegcp_gke.projects_locations_clusters_node_pools.updateProjects locations clusters node pools: updatewrite
Projects zones clusters node pools10
gcp_gke.projects_zones_clusters_node_pools.autoscalingProjects zones clusters node pools: autoscalingwritegcp_gke.projects_zones_clusters_node_pools.createProjects zones clusters node pools: createwritegcp_gke.projects_zones_clusters_node_pools.deleteProjects zones clusters node pools: deletedestructivegcp_gke.projects_zones_clusters_node_pools.fetch_node_pool_upgrade_infoProjects zones clusters node pools: fetch node pool upgrade inforeadgcp_gke.projects_zones_clusters_node_pools.getProjects zones clusters node pools: getreadgcp_gke.projects_zones_clusters_node_pools.listProjects zones clusters node pools: listreadgcp_gke.projects_zones_clusters_node_pools.rollbackProjects zones clusters node pools: rollbackwritegcp_gke.projects_zones_clusters_node_pools.set_managementProjects zones clusters node pools: set managementwritegcp_gke.projects_zones_clusters_node_pools.set_sizeProjects zones clusters node pools: set sizewritegcp_gke.projects_zones_clusters_node_pools.updateProjects zones clusters node pools: updatewrite
Projects locations operations3
gcp_gke.projects_locations_operations.cancelProjects locations operations: canceldestructivegcp_gke.projects_locations_operations.getProjects locations operations: getreadgcp_gke.projects_locations_operations.listProjects locations operations: listread
Projects zones operations3
gcp_gke.projects_zones_operations.cancelProjects zones operations: canceldestructivegcp_gke.projects_zones_operations.getProjects zones operations: getreadgcp_gke.projects_zones_operations.listProjects zones operations: listread
Projects aggregated usable subnetworks1
gcp_gke.projects_aggregated_usable_subnetworks.listProjects aggregated usable subnetworks: listread
Projects locations1
gcp_gke.projects_locations.get_server_configProjects locations: get server configread
Projects locations clusters well known1
gcp_gke.projects_locations_clusters_well_known.get_openid_configurationProjects locations clusters well known: get openid configurationread
Projects zones1
gcp_gke.projects_zones.get_serverconfigProjects zones: get serverconfigread
Questions
The Google Kubernetes Engine MCP server, answered.
Is there a Google Kubernetes Engine MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 71 Google Kubernetes Engine actions across projects locations clusters, projects zones clusters, projects locations clusters node pools and projects zones clusters node pools, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Kubernetes Engine.
What do I need to connect Google Kubernetes Engine?
Your own Google Kubernetes Engine OAuth app, registered with Google Kubernetes Engine (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Kubernetes 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_gke" } lists exactly what to paste.
Can an AI agent delete or change things in Google Kubernetes Engine?
Only if its key allows it, and only with an explicit confirmation. 6 Google Kubernetes Engine actions are destructive, including projects locations clusters: delete, projects locations operations: cancel and projects locations clusters node pools: 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 Kubernetes Engine API limit?
actionlake paces every call to the limits in the Google Kubernetes Engine service file: 600 calls a minute per connection. Repeated reads are answered from cache (18 Google Kubernetes Engine actions can be), which never reaches Google Kubernetes Engine.
What does a Google Kubernetes Engine action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (1 Google Kubernetes Engine actions page). Cache hits, searches, dry runs and calls Google Kubernetes 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 Kubernetes Engine API does it cover?
The Google Kubernetes Engine (clusters, node pools, upgrades, operations, server config) API container v1 (Discovery revision 20260922) at container.googleapis.com. It is built from Google Kubernetes Engine's documentation as read on 23 October 2026. 71 actions in 10 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my Google Kubernetes 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 Kubernetes 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 Kubernetes Engine today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.
