Googleapis MCP

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 开发者工具

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://container.googleapis.com/mcp

claude mcp add --transport http container https://container.googleapis.com/mcp

{
  "mcpServers": {
    "container": {
      "url": "https://container.googleapis.com/mcp"
    }
  }
}

{
  "servers": {
    "container": {
      "type": "http",
      "url": "https://container.googleapis.com/mcp"
    }
  }
}

https://container.googleapis.com/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月10日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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. For regional locations, cluster creation

• 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`.

• diagnose_k8s_workload

  Collects a correlated incident snapshot for a Kubernetes workload (Deployment, StatefulSet, DaemonSet), verifying referenced ConfigMaps, Secrets, and PVCs, warning events, and automatically deduplicating container error logs.

• get_k8s_cluster_health

  Computes a high-level health scorecard across nodes, workloads, system pods, and control-plane components (GKE cluster state, admission webhooks, and API Priority and Fairness).

• get_k8s_log_summary

  Fetches and deduplicates container logs using pattern fingerprinting to reduce token usage. Prefer this over get_k8s_logs when triaging crashes or noisy logs.

• list_k8s_cluster_issues

  Scans a cluster or namespace for abnormal pods (CrashLoopBackOff, OOMKilled, ImagePullBackOff), node pressure, stalled rollouts, quota exhaustion, PDB blocks, admission webhook risks, and API Priority and Fairness issues.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（container.googleapis.com）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 212 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 27 个工具描述，未发现针对 AI 的隐藏指令

与“开发者工具”中的其他服务器比较i

• 星标数多于此分类中其他 5714 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 5714 个服务器的 10% 更新
• 基础检查结果等于或优于此分类中其他 5714 个服务器的 23%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README