What it does
Safe Kubernetes access for AI agents via MCP. Read-only by default, with explicit permission modes.
- Connects 在你的电脑上运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 6/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 3/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 9/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
双击文件,然后在电脑版 Claude 应用中点击 Install
试一试
用 K8s MCP Server (Go) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 K8s MCP Server (Go),或回答中出现 K8s MCP Server (Go) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 K8s MCP Server (Go)
K8s MCP Server (Go) 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 K8s MCP Server (Go) 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code 暂时无法连接 K8s MCP Server (Go)
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 K8s MCP Server (Go) 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
Cursor 暂时无法连接 K8s MCP Server (Go)
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 K8s MCP Server (Go) 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
VS Code 暂时无法连接 K8s MCP Server (Go)
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 K8s MCP Server (Go) 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 kaneg 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于5个月前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/kaneg-k8s-mcp-go)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6116 个服务器的 77%
- 发布到注册中心的时间比此分类中其他 6116 个服务器的 16% 更新
- 基础检查结果等于或优于此分类中其他 6116 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
K8s MCP Server (Go) 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于5个月前,最新版本(0.4.6)于5个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 K8s MCP Server (Go) | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
k8s-mcp-go
Safe, read-only-by-default Kubernetes access for AI agents.
A Kubernetes MCP server that lets AI assistants inspect your cluster safely — without giving them unrestricted kubectl.
What makes it different
- Read-only by default: useful for diagnosis without giving AI permission to mutate the cluster.
- Explicit permission modes: choose
readonly,readwrite, ordangerousbefore the assistant starts. - No Docker required: install via MCPB bundles or a single native binary.
- Kubernetes-native visibility: inspect pods, deployments, services, logs, events, nodes, and live CPU/memory usage.
- Registry-ready distribution: published as
io.github.kaneg/k8s-mcp-gofor MCP Registry consumers and packaged clients.
Distribution
- MCP Registry: published as
io.github.kaneg/k8s-mcp-go. - PulseMCP: indexed from the MCP ecosystem with the official
server.json. - Claude Code Marketplaces: listed with MCPB installation metadata.
Why
Most AI agents can use Kubernetes tools. The real problem is how to stop them from changing the wrong thing.
Giving an AI raw kubectl access is risky. Even a capable model can:
- delete the wrong resource
- restart the wrong workload
- apply a dangerous change
- turn a debugging session into a production incident
k8s-mcp-go gives AI agents a guardrailed interface to Kubernetes instead of unrestricted shell access.
It is built for the real-world question:
How can I let AI help with Kubernetes, without letting it break my cluster?
Permission Modes
You choose the boundary up front:
| What you want | Mode |
|---|---|
| "Let AI inspect and diagnose, but change nothing" | readonly |
| "Allow safe operational actions like scale and restart" | readwrite |
| "Give it full cluster power" | dangerous |
readonly (default)
For diagnosis, inspection, and safe exploration.
AI can do things like:
- list pods, deployments, services, nodes, and namespaces
- read logs and events
- inspect cluster state
- check resource usage
It cannot modify workloads or delete resources.
readwrite
For controlled operational workflows.
AI can do things like:
- scale deployments
- restart deployments
- restart statefulsets
- update images
- patch deployments
- create namespaces
It still cannot perform the most destructive operations.
dangerous
Full access.
Use this only when you explicitly want AI to be able to:
- delete resources
- delete namespaces
- apply arbitrary YAML
If you are unsure, use readonly.
Quick Start
Option 1: MCPB Install (Recommended)
Download the .mcpb bundle for your platform from Releases. MCPB-compatible clients (Claude Desktop, Cursor, etc.) can install it directly — no Docker, no Go, no manual setup.
| OS | Arch | File |
|---|---|---|
| Linux | x86_64 | k8s-mcp-go_*_linux_amd64.mcpb |
| Linux | ARM64 | k8s-mcp-go_*_linux_arm64.mcpb |
| macOS | Intel | k8s-mcp-go_*_darwin_amd64.mcpb |
| macOS | Apple Silicon | k8s-mcp-go_*_darwin_arm64.mcpb |
| Windows | x86_64 | k8s-mcp-go_*_windows_amd64.mcpb |
| Windows | ARM64 | k8s-mcp-go_*_windows_arm64.mcpb |
Option 2: Manual Binary Install
Grab the binary archive from Releases and extract it:
# Example: Linux x86_64
tar xzf k8s-mcp-go_*_linux_amd64.tar.gz chmod +x k8s-mcp-go sudo mv k8s-mcp-go /usr/local/bin/
Then add it to your MCP client.
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": { "k8s": { "command": "k8s-mcp-go", "args": ["-mode=readonly"] } } }
Cursor (.cursor/mcp.json):
{
"mcpServers": { "k8s": { "command": "k8s-mcp-go", "args": ["-mode=readonly"] } } }
Restart your client and start asking questions about your cluster.
Example prompts
Once installed, ask your AI assistant things like:
- "Show me unhealthy pods in all namespaces."
- "Which pods are using the most memory?"
- "Summarize recent warning events."
- "Inspect this deployment and explain why it is not ready."
- "Check rollout status for this deployment."
In readonly mode, the assistant can investigate but cannot change the cluster.
Why not just use kubectl?
Because the problem is not whether AI can talk to Kubernetes. The problem is whether it can do so safely.
kubectl is powerful, but it does not give you a product-level permission mode for AI behavior. With k8s-mcp-go, you decide whether the assistant can:
- inspect only
- perform limited operational actions
- or get full control
The permission boundary is the product.
Available Tools (35 total)
Tools are grouped by permission level. Names start with an action verb such as get, list, or delete; top_nodes and top_pods retain Kubernetes' established kubectl top terminology.
Readonly (24)
| Tool | Description |
|---|---|
get_server_info | Show server version, mode, Kubernetes config source, and runtime details |
resolve_workload | Resolve an app/workload name to matching resources and suggested next tools |
list_pods | List pods; supports all_namespaces=true |
get_pod | Get pod details |
get_pod_logs | Get pod logs |
list_deployments | List deployments; supports all_namespaces=true |
get_deployment | Get deployment details |
list_statefulsets | List StatefulSets; supports all_namespaces=true |
get_statefulset | Get StatefulSet details |
list_services | List services; supports all_namespaces=true |
get_service | Get service details |
list_configmaps | List ConfigMaps; supports all_namespaces=true |
get_configmap | Get ConfigMap data |
list_secrets | List Secrets (keys only); supports all_namespaces=true |
get_secret | Get Secret metadata and keys |
list_pvc | List PersistentVolumeClaims; supports all_namespaces=true |
list_ingress | List Ingress resources; supports all_namespaces=true |
list_jobs | List Jobs; supports all_namespaces=true |
top_nodes | Current node CPU and memory usage |
top_pods | Current pod CPU and memory usage |
list_nodes | List cluster nodes |
list_namespaces | List namespaces |
get_cluster_overview | Cluster health summary |
list_events | List events |
Readwrite (7)
| Tool | Description |
|---|---|
scale_deployment | Scale deployment replicas |
restart_deployment | Rolling restart a deployment |
restart_statefulset | Rolling restart a statefulset |
set_image | Update container image |
get_rollout_status | Check rollout progress |
create_namespace | Create a new namespace |
patch_deployment | Apply strategic merge patch |
Dangerous (7)
| Tool | Description |
|---|---|
delete_pod | Delete a pod |
delete_deployment | Delete a deployment |
delete_statefulset | Delete a StatefulSet and its pods |
delete_daemonset | Delete a DaemonSet and its pods |
delete_resource | Delete a resource without a dedicated delete tool |
delete_namespace | Delete a namespace and all resources |
apply_yaml | Apply arbitrary YAML manifest |
Prefer the dedicated delete tools above when one exists. Use delete_resource as the fallback for other kinds. It resolves namespaced versus cluster-scoped resources through Kubernetes discovery.
{"api_version":"v1","kind":"ServiceAccount","namespace":"apps","name":"builder"}
{"api_version":"rbac.authorization.k8s.io/v1","kind":"ClusterRole","name":"auditor"}
Kubernetes Configuration
Configuration is selected in this order:
- The file specified by
KUBECONFIG, when set. - The Pod's in-cluster ServiceAccount configuration.
~/.kube/configwhen running outside a cluster.
An explicit KUBECONFIG is authoritative. If it cannot be loaded, the server returns an error instead of silently switching to the Pod's ServiceAccount. In-cluster configuration uses Kubernetes' mounted token file so projected ServiceAccount token rotation continues to work without copying tokens into a kubeconfig.
Environment Variables
| Variable | Description |
|---|---|
KUBECONFIG | Explicit kubeconfig path. When unset, use in-cluster configuration or fall back to ~/.kube/config. |
Build from Source
git clone https://github.com/kaneg/k8s-mcp-go.git
cd k8s-mcp-go go build -o k8s-mcp-go .
License
MIT