Gke (google Kubernetes Engine) Mcp

MCP运维云端

提供方 GoogleCloudPlatform

运维云端 未标注 会话登录 社区 / 第三方 CursorGemini CLICodexZed
查看接入方式

GKE MCP Server Enable MCP-compatible AI agents to interact with Google Kubernetes Engine. Installation Choose a way to install the MCP Server and then connect your AI to it. Install the MCP Server Quick Install (Linux & MacOS only) `sh curl -sSL https://raw.githubusercontent.com/GoogleCloudPlatform/gke-mcp/main/install.sh | bash ` Manual Install If you haven't already installe

一句话选型结论

按资料字段整理

Gke (google Kubernetes Engine) Mcp 属于运维云端类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Cursor、Gemini CLI、Codex 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

kubernetes mcp google cloud

支持客户端

适用场景

kubernetesmcpgoogle cloud

安装与配置

未标注 会话登录
上游未给出传输方式
go install github.com/GoogleCloudPlatform/gke-mcp@latest

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor、Gemini CLI、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Gemini CLI 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gke (google Kubernetes Engine) Mcp当前 未标注 未标注 未标注 有 未标注
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方GoogleCloudPlatform上游标注的维护方 GoogleCloudPlatform
分类运维云端本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.2 KB
来自项目仓库与上游目录的原文,未做删改

GKE MCP Server and Gemini CLI Extension

Enable MCP-compatible AI agents to interact with Google Kubernetes Engine.

Installation

Choose a way to install the MCP Server and then connect your AI to it.

Use as a Gemini CLI Extension

  1. Install Gemini CLI.

  2. Install the extension```sh
    gemini extensions install https://github.com/GoogleCloudPlatform/gke-mcp.git


### Use in MCP Clients / Other AIs

#### Quick Install (Linux & macOS only)```sh
curl -sSL https://raw.githubusercontent.com/GoogleCloudPlatform/gke-mcp/main/install.sh | bash

Manual Install

If you haven't already installed Go, follow these instructions.

Once Go is installed, run the following command to install gke-mcp:```sh
go install github.com/GoogleCloudPlatform/gke-mcp@latest


The `gke-mcp` binary will be installed in the directory specified by the `GOBIN` environment variable. If `GOBIN` is not set, it defaults to `$GOPATH/bin` and, if `GOPATH` is also not set, it falls back to `$HOME/go/bin`.

You can find the exact location by running `go env GOBIN`. If the command returns an empty value, run `go env GOPATH` to find the installation directory.

For additional help, refer to the troubleshoot section: gke-mcp: command not found.

### Add the MCP Server to your AI

For detailed instructions on how to connect the GKE MCP Server to various AI clients, including Cursor, Visual Studio Code, Claude Desktop, and Claude Code, please refer to our dedicated installation guide.

### Configuring the Developer Knowledge API

The manifest generation agent (`generate_manifest` tool) can retrieve official GKE documentation, required annotations, and best practices using the Developer Knowledge API.

To enable this capability:

1. **Enable the API:** Enable the **Developer Knowledge API** in your Google Cloud Project (refer to the Developer Knowledge API documentation for details).
2. **Generate an API Key:** Create an API key with permissions to call the Developer Knowledge API.
3. **Configure the Environment Variable:** Set the `DK_API_KEY` environment variable when starting the MCP server:
   - **Gemini CLI / Terminal:**```sh
     export DK_API_KEY="your-api-key-here"
     ```
   - **Cursor / Claude Desktop / Visual Studio Code:** Add the environment variable to your client's MCP configuration. For example, in `claude_desktop_config.json`:```json
     {
       "mcpServers": {
         "gke-mcp": {
           "command": "gke-mcp",
           "env": {
             "DK_API_KEY": "your-api-key-here"
           }
         }
       }
     }
     ```

Optional configuration:

- `DK_BASE_URL`: The base URL of the Developer Knowledge API (defaults to `https://knowledge.googleapis.com`).

## MCP Tools

- `cluster_toolkit_download`: Download the Cluster Toolkit Git repository.
- `list_clusters`: List GKE clusters.
- `get_cluster`: Get detailed information about a single GKE cluster.
- `create_cluster`: Create a new GKE cluster (defaults to Autopilot).
- `get_kubeconfig`: Configure kubeconfig for a GKE cluster.
- `update_cluster`: Update a GKE cluster.
- `get_node_sos_report`: Generate and download an SOS report from a GKE node.
- `delete_cluster`: Delete a GKE cluster (if enabled).
- `list_node_pools`: List node pools in a GKE cluster.
- `get_node_pool`: Get details for a GKE node pool.
- `create_node_pool`: Create a new node pool in a GKE cluster.
- `update_node_pool`: Update a GKE node pool.
- `delete_node_pool`: Delete a GKE node pool (if enabled).
- `gke_deploy`: Deploy a workload to a GKE cluster using a configuration file.
- `query_logs`: Query Google Cloud Platform logs using Logging Query Language (LQL).
- `get_log_schema`: Get the schema for a specific GKE log type.
- `list_monitored_resource_descriptors`: List monitored resource descriptors for GKE.
- `list_recommendations`: List recommendations for GKE clusters.
- `get_k8s_changelog`: Get Kubernetes changelog for upgrades.
- `get_gke_release_notes`: Get GKE release notes.
- `generate_manifest`: Generate a Kubernetes manifest using Vertex AI.
- `get_k8s_resource`: Gets one or more Kubernetes resources from a cluster.
- `list_k8s_events`: Retrieves events from a Kubernetes cluster.
- `get_k8s_version`: Retrieves the Kubernetes server version for a given cluster.
- `apply_k8s_manifest`: Applies a Kubernetes manifest to a cluster using server-side apply.
- `get_k8s_logs`: Gets logs from a Kubernetes container in a pod.
- `delete_k8s_resource`: Delete a Kubernetes resource from a cluster.

## MCP Prompts

Prompts provide guided workflows and expert knowledge templates.

- `gke:cost`: Answer natural language questions about GKE-related costs.
- `gke:deploy`: Deploys a workload to a GKE cluster using a configuration file.
- `gke:upgrade-risk-report`: GKE control plane upgrade risk report, analyzing the potential risks of upgrading from its current version to the target version. Performs pre-upgrade checks, API deprecations scans, and more.
- `gke:upgrades-best-practices-risk-report`: GKE control plane upgrade best practices, applied for the specified cluster. Helps making upgrades uneventful.

## MCP Context

In addition to the tools above, a lot of value is provided through the bundled context instructions.

- **Cost**: The provided instructions allows the AI to answer many questions related to GKE costs, including queries related to clusters, namespaces, and Kubernetes workloads.

- **GKE Known Issues**: The provided instructions allows the AI to fetch the latest GKE Known issues and check whether the cluster is affected by one of these known issues.

## Supported MCP Transports

By default, `gke-mcp` uses the stdio transport. Additionally, the Streamable HTTP transport is supported as well.

You can set the transport mode using the following options:

`--server-mode`: transport to use for the server: stdio (default) or http

`--server-host`: server host to use when server-mode is http; defaults to `127.0.0.1`

`--server-port`: server port to use when server-mode is http; defaults to 8080```sh
gke-mcp --server-mode http --server-host 127.0.0.1 --server-port 8080

> [!WARNING]
> By default, the HTTP server binds to 127.0.0.1, which limits access to the local machine.
> If you explicitly set --server-host 0.0.0.0 or another non-loopback address, the server may become reachable from other machines on your network.
> Please ensure you have a firewall and/or other security measures in place if the server is not intended to be private.

Connecting Gemini CLI to the HTTP Server

To connect Gemini CLI to the gke-mcp HTTP server, you need to configure the CLI to point to the correct endpoint. You can do this by updating your ~/.gemini/settings.json file. For a basic setup without authentication, the file should look like this:json { "mcpServers": { "gke": { "httpUrl": "http://127.0.0.1:8080/mcp" } } }

This configuration tells Gemini CLI how to reach the gke-mcp server running on your local machine at port 8080.

Development

To compile the binary and update the gemini-cli extension with your local changes, follow these steps:

  1. Remove the global gke-mcp configurationsh rm -rf ~/.gemini/extensions/gke-mcp

  2. Build the binary from the root of the project:sh go build -o gke-mcp .

  3. Run the installation command to update the extension manifest:sh ./gke-mcp install gemini-cli --developer

This will make gemini-cli use your locally compiled binary.

Disclaimers

  • The Google Cloud Platform Terms of Service (available at https://cloud.google.com/terms/) and the Data Processing and Security Terms (available at https://cloud.google.com/terms/data-processing-terms) do not apply to any component of the GKE MCP Server software.
  • This tool is provided for education and experimentation, and is not an officially supported Google product. It is maintained on a best-effort basis, and may change without notice.
  • This project interacts with Large Language Models and comes with inherent risks.
  • Use at Your Own Risk: This software is experimental, non-deterministic, and provided "AS IS" with NO GUARANTEES or warranties.
  • NOT FOR PRODUCTION USE.
  • Data Sensitivity: Avoid using untrusted data. NEVER input secrets, API keys, or sensitive information.
  • Verify Outputs: LLM responses can be unpredictable and may be inaccurate. Always verify results.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Gke (google Kubernetes Engine) Mcp 怎么安装?

在客户端按下面的安装命令接入:go install github.com/GoogleCloudPlatform/gke-mcp@latest。装完在客户端配置里引用同一个包或端点。

Gke (google Kubernetes Engine) Mcp 怎么在 Cursor、Gemini CLI、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Gke (google Kubernetes Engine) Mcp 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Gke (google Kubernetes Engine) Mcp 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Gke (google Kubernetes Engine) Mcp 支持哪些客户端?

资料标注支持 Cursor、Gemini CLI、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Gke (google Kubernetes Engine) Mcp 能提供哪些能力?

资料显示能力标签包括 kubernetes、mcp、google cloud。具体工具清单以官方文档为准。

Gke (google Kubernetes Engine) Mcp 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。