mcp
Provides read access to your GKE and Kubernetes resources.
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Provides read access to your GKE and Kubernetes resources.
How to connect
How to connect mcp to Claude
The server address to paste into Claude settings:
https://container.googleapis.com/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect mcp to ChatGPT
The server address to paste into ChatGPT settings:
https://container.googleapis.com/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect mcp to Cursor
The server address to paste into Cursor settings:
https://container.googleapis.com/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (23)
Raw names from tools/list. Only developers need these.
| list_k8s_api_resources | Retrieves the available API groups and resources from a Kubernetes cluster. This is similar to running `kubectl api-resources`. |
| check_k8s_auth | Checks whether an action is allowed on a Kubernetes resource. This is similar to running `kubectl auth can-i`. |
| describe_k8s_resource | Shows the details of a specific Kubernetes resource. This is similar to running `kubectl describe`. |
| list_k8s_events | Retrieves events from a Kubernetes cluster. This is similar to running `kubectl events`. |
| get_k8s_resource | 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`. |
| get_k8s_cluster_info | Gets cluster endpoint information. This is similar to running `kubectl cluster-info`. |
| get_k8s_version | Retrieves Kubernetes client and server versions for a given cluster. This is similar to running `kubectl version`. |
| get_k8s_rollout_status | Checks the current rollout status of a Kubernetes resource. This is similar to running `kubectl rollout status`. |
| list_clusters | Lists GKE clusters in a given project and location. Location can be a region, zone, or '-' for all locations. |
| create_cluster | 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 autopilot.enabled=false in the cluster configuration. This is similar to running `gcloud container clusters create-auto` or `gcloud container clusters create`. |
| update_cluster | Updates a specific GKE cluster. |
| get_cluster | Gets the details of a specific GKE cluster. |
| list_operations | Lists GKE operations in a given project and location. Location can be a region, zone, or '-' for all locations. |
| get_operation | Gets the details of a specific GKE operation. |
| cancel_operation | Cancels a specific GKE operation. |
| create_node_pool | Creates a node pool for a specific GKE cluster. |
| list_node_pools | Lists the node pools for a specific GKE cluster. |
| get_node_pool | Gets the details of a specific node pool within a GKE cluster. |
| update_node_pool | Updates a specific node pool within a GKE cluster. |
| get_k8s_logs | Gets logs from a Kubernetes container in a pod. This is similar to running `kubectl logs`. |
| apply_k8s_manifest | Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running `kubectl apply --server-side`. |
| delete_k8s_resource | Deletes a Kubernetes resource from a cluster. This is similar to running `kubectl delete`. |
| patch_k8s_resource | Patches a Kubernetes resource. This is similar to running `kubectl patch`. |