Provider-neutral MCP server for AgentDispatch.
Retrieves the available API groups and resources from a Kubernetes cluster. This is similar to running `kubectl api-resources`.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
What it does
Remote MCP server for GKE cluster and Kubernetes API resource discovery.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add google-kubernetes-engine-mcp
# 2 — ask your agent something
> Remote MCP server for GKE cluster and Kubernetes API resource discovery.
Google Kubernetes Engine is free: there is no plan to choose, no cap to set and nothing that can bill you.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --transport http google-kubernetes-engine-mcp https://container.googleapis.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Retrieves the available API groups and resources from a Kubernetes cluster. This is similar to running `kubectl api-resources`.
Takes no parameters.
Checks whether an action is allowed on a Kubernetes resource. This is similar to running `kubectl auth can-i`.
Takes no parameters.
Shows the details of a specific Kubernetes resource. This is similar to running `kubectl describe`.
Takes no parameters.
Retrieves events from a Kubernetes cluster. This is similar to running `kubectl events`.
Takes no parameters.
Gets one or more Kubernetes resources from a cluster. Resources can be filtered by type, name, namespace, and label selectors. Returns the resources in YAML format. This is similar to running `kubectl get`.
Takes no parameters.
Gets cluster endpoint information. This is similar to running `kubectl cluster-info`.
Takes no parameters.
Retrieves Kubernetes client and server versions for a given cluster. This is similar to running `kubectl version`.
Takes no parameters.
Checks the current rollout status of a Kubernetes resource. This is similar to running `kubectl rollout status`.
Takes no parameters.
Lists GKE clusters in a given project and location. Location can be a region, zone, or '-' for all locations.
Takes no parameters.
Creates a new GKE cluster in a given project and location. It's recommended to read the [GKE documentation](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/configuration-overview) to understand cluster configuration options. Cluster creation will default to Autopilot mode, as recommended by GKE best practices. If the user explicitly wants to create a Standard cluster, you need to set
Takes no parameters.
Updates a specific GKE cluster.
Takes no parameters.
Gets the details of a specific GKE cluster.
Takes no parameters.
Lists GKE operations in a given project and location. Location can be a region, zone, or '-' for all locations.
Takes no parameters.
Gets the details of a specific GKE operation.
Takes no parameters.
Cancels a specific GKE operation.
Takes no parameters.
Creates a node pool for a specific GKE cluster.
Takes no parameters.
Lists the node pools for a specific GKE cluster.
Takes no parameters.
Gets the details of a specific node pool within a GKE cluster.
Takes no parameters.
Updates a specific node pool within a GKE cluster.
Takes no parameters.
Gets logs from a Kubernetes container in a pod. This is similar to running `kubectl logs`.
Takes no parameters.
Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running `kubectl apply --server-side`.
Takes no parameters.
Deletes a Kubernetes resource from a cluster. This is similar to running `kubectl delete`.
Takes no parameters.
Patches a Kubernetes resource. This is similar to running `kubectl patch`.
Takes no parameters.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Google Kubernetes Engine costs nothing to install and nothing to call, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
No release history has been published for this listing yet.
This listing has published no versions to the marketplace yet.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against Google Kubernetes Engine in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.