io.github.mikhae1/kubeview

编码与调试

by mikhae1

只读型Model Context Protocol服务器,安全呈现Kubernetes、Helm与Argo的关键洞察。

什么是 io.github.mikhae1/kubeview

只读型Model Context Protocol服务器,安全呈现Kubernetes、Helm与Argo的关键洞察。

README

KubeView MCP

npm version License: MIT Node.js MCP

Read-only Model Context Protocol server for Kubernetes diagnostics. Instead of exposing dozens of tools, it gives the agent a sandboxed TypeScript runtime: a single run_code call can query Kubernetes, Helm, Argo Workflows, and Argo CD, correlate the results, and return only the answer. Intermediate payloads never pass through the model's context window. Based on the code execution with MCP pattern.

Background: Evicting MCP tool calls from your Kubernetes cluster

How it works

v2 publishes exactly two public tools: run_code and an approval-gated kube_pod_exec. Everything else is discovered inside the sandbox via tools.list(), tools.search(), and tools.help(), following the MCP progressive discovery and programmatic calling guidance.

run_code executes bounded TypeScript with top-level await. One call can list workloads, correlate events, fetch logs, and diff Helm state without shipping intermediate payloads back through the model:

ts
const pods = await tools.kubernetes.list({ namespace: 'payments' });
const unhealthy = pods.items.filter((p) => p.status?.phase !== 'Running');

return Promise.all(
  unhealthy.map(async (pod) => ({
    pod: pod.metadata?.name,
    logs: await tools.kubernetes.logs({
      namespace: 'payments',
      podName: pod.metadata?.name,
      tailLines: 100,
    }),
  })),
);
  • Sensitive isolationkube_pod_exec is unreachable from sandboxed code. Top-level exec requires MCP elicitation, is bound to the argument digest, expires after 10 minutes, and fails closed. kube_port_forward is never a top-level tool and is denied inside code mode by default. tools.disabled() reports which policy blocked a capability and whether that denial is configurable.
  • API-driven discovery — Argo Workflows and Argo CD are detected from the Kubernetes API, scoped to the active kube context, cached for 60 s. An unavailable optional API never blocks startup.
  • Native reads — resources, metrics, logs, events, and network probes go through the Kubernetes API. Helm releases are parsed from cluster Secrets or ConfigMaps; a local helm binary is a fallback, not a prerequisite.

Quick start

Prerequisites: Node.js ≥ 22 and access to a cluster (KUBECONFIG or in-cluster service account).

bash
npx -y kubeview-mcp

# Claude Code
claude mcp add kubernetes -- npx kubeview-mcp
json
{
  "mcpServers": {
    "kubeview": {
      "command": "npx",
      "args": ["-y", "kubeview-mcp"]
    }
  }
}

In Cursor, /kubeview/code-mode injects the typed API into context.

Configuration

Cluster

VariableDescriptionDefault
KUBECONFIGKubeconfig path~/.kube/config
MCP_KUBE_CONTEXTKubernetes context; defaults to the active contextunset
MCP_K8S_SKIP_TLS_VERIFYSkip TLS verification for the Kubernetes API (true/1)false
MCP_TIMEOUTDefault operation timeout in msplugin default
MCP_HIDE_SENSITIVEMask sensitive data globallyfalse
MCP_DISABLE_KUBERNETES_PLUGINDisable the Kubernetes plugin (true/1)unset
MCP_DISABLE_HELM_PLUGINDisable the Helm plugin (true/1)unset

Mode and capabilities

VariableDescriptionDefault
MCP_MODEcode (default), all (alias), or toolscode
MCP_CODE_MODE_DISABLED_TOOLSComma-separated code-mode denials; empty enables allJSON/default
MCP_ARGO_TOOLSArgo override: auto, on, offauto
MCP_ARGOCD_TOOLSArgo CD override: auto, on, offauto
MCP_LOG_LEVELerror, warn, info, debuginfo
KUBE_MCP_FORCE_VM_SANDBOXForce node:vm in the standalone runtimeunset

HTTP transport

VariableDescriptionDefault
MCP_TRANSPORTstdio or httpstdio
MCP_HTTP_HOST / _PORTHTTP bind (when MCP_TRANSPORT=http)127.0.0.1:3000
MCP_HTTP_PATHStreamable HTTP endpoint path/mcp
MCP_HTTP_JSON_RESPONSEPrefer JSON over SSE (drops mid-call notifications)false
MCP_ALLOWED_HOSTSHost allowlist (required when binding to 0.0.0.0/::)local defaults
MCP_ALLOWED_ORIGINSOrigin allowlist for HTTPunset
MCP_APPROVAL_STATE_SECRETShared 32+ byte signing secret; required for HTTP approvalsephemeral (stdio)
MCP_APPROVAL_REPLAY_DIRAbsolute shared-volume directory for one-time HTTP approvalsunset
bash
mkdir -p /tmp/kubeview-mcp-approvals
MCP_APPROVAL_STATE_SECRET='replace-with-at-least-32-random-bytes' \
MCP_APPROVAL_REPLAY_DIR=/tmp/kubeview-mcp-approvals \
MCP_TRANSPORT=http MCP_HTTP_HOST=127.0.0.1 MCP_HTTP_PORT=3000 npx -y kubeview-mcp

Endpoint: http://127.0.0.1:3000/mcp. HTTP follows the MCP 2026-07-28 stateless core: a fresh server per request, no initialize, no Mcp-Session-Id. Each request carries protocol version, client identity, and capabilities in _meta; modern requests add Mcp-Method/Mcp-Name for gateway routing. 2025-era clients use the SDK's stateless fallback on the same endpoint. State that must survive across calls has to be passed as tool arguments or handles.

HTTP mode refuses to start without both approval variables. Multi-replica deployments need the same secret and a shared writable replay directory; the /tmp example is for a single process only. The published MCP registry entry still targets stdio.

Tool surfaces

MCP_MODEExposed tools
unset / code / allrun_code, kube_pod_exec
toolskube_list, kube_get, kube_logs, helm, kube_pod_exec, plus detected argo and argocd

Domain tools use an operation discriminator:

  • helmlist | get | debug
  • argolist | get | logs | cron_list (when Workflow or CronWorkflow is discoverable)
  • argocdlist | get | resources | logs | history | status (when Application is discoverable, or with ARGOCD_SERVER + ARGOCD_AUTH_TOKEN)

Discovery is cached per kube context for 60 s. Missing optional APIs are omitted, not fatal.

Code mode

Code mode is the default (MCP_MODE=code). The agent writes short TypeScript against a typed tools global instead of calling dozens of MCP tools.

Inside run_code:

  • Typed tools namespaces for Kubernetes, Helm, and any detected Argo capabilities, generated from live schemas so parameters cannot be hallucinated.
  • Progressive discovery: tools.list(), tools.search(), tools.help(), and tools.disabled() (the last reports why a capability was blocked).
  • A locked-down runtime with only console and tools in scope — no filesystem, no network, no process.
CapabilityInside run_codeTop-level tool
kube_pod_execNever availableRequires per-call user approval (10 min, argument-bound)
kube_port_forwardDenied by default (configurable)Never exposed
Everything elseAvailableOnly when MCP_MODE=tools

Pod exec approval uses MCP elicitation and fails closed. The standalone npm run code-mode launcher has no trusted approval UI, so it always denies pod exec.

Customizing denials

MCP_CODE_MODE_DISABLED_TOOLS (comma-separated) controls which capabilities are blocked inside run_code. Resolution order:

  1. MCP_CODE_MODE_DISABLED_TOOLS env var
  2. disabledTools in kube-mcp.code-mode.json
  3. Default: ["kube_port_forward"]

An empty env value clears the list. kube_pod_exec cannot be added — it is permanently blocked.

Protocol

MCP 2026-07-28:

  • JSON Schema 2020-12 in/out contracts with server-side validation
  • Machine-readable structuredContent with text fallback
  • Accurate read-only, destructive, idempotent, open-world annotations
  • Deterministic tool ordering with cache hints for fixed vs. discovery-dependent surfaces
  • Stateless HTTP with discovery and header-based routing (Mcp-Method, Mcp-Name)
  • Execution failures returned as tool errors; protocol errors reserved for malformed requests

Local development

bash
git clone https://github.com/mikhae1/kubeview-mcp.git
cd kubeview-mcp && npm install

npm run build      # compile
npm start          # build + run
npm test           # jest suite
npm run typecheck  # tsc --noEmit

# Invoke a tool directly
npm run command -- kube_list --namespace=default

Protocol tests pin the SDK v2 client to 2026-07-28 and route through the server handler in-process (no open ports):

bash
npm test -- --runInBand \
  tests/server/StreamableHttpTransport.integration.test.ts \
  tests/server/StreamableHttpRuntime.test.ts \
  tests/server/TransportConfig.test.ts \
  tests/compat/McpSdkCompatibility.test.ts

Contributing

Contributions are welcome! Please feel free to submit an issue or a pull request.

License

MIT © mikhae1

常见问题

io.github.mikhae1/kubeview 是什么?

只读型Model Context Protocol服务器,安全呈现Kubernetes、Helm与Argo的关键洞察。

相关 Skills

网页构建器

by anthropics

Universal
热门

面向复杂 claude.ai HTML artifact 开发,快速初始化 React + Tailwind CSS + shadcn/ui 项目并打包为单文件 HTML,适合需要状态管理、路由或多组件交互的页面。

在 claude.ai 里做复杂网页 Artifact 很省心,多组件、状态和路由都能顺手搭起来,React、Tailwind 与 shadcn/ui 组合效率高、成品也更精致。

编码与调试
未扫描176.4k

网页应用测试

by anthropics

Universal
热门

用 Playwright 为本地 Web 应用编写自动化测试,支持启动开发服务器、校验前端交互、排查 UI 异常、抓取截图与浏览器日志,适合调试动态页面和回归验证。

借助 Playwright 一站式验证本地 Web 应用前端功能,调 UI 时还能同步查看日志和截图,定位问题更快。

编码与调试
未扫描176.4k

前端设计

by anthropics

Universal
热门

面向组件、页面、海报和 Web 应用开发,按鲜明视觉方向生成可直接落地的前端代码与高质感 UI,适合做 landing page、Dashboard 或美化现有界面,避开千篇一律的 AI 审美。

想把页面做得既能上线又有设计感,就用前端设计:组件到整站都能产出,难得的是能避开千篇一律的 AI 味。

编码与调试
未扫描176.4k

相关 MCP Server

GitHub

编辑精选

by GitHub

热门

GitHub 是 MCP 官方参考服务器,让 Claude 直接读写你的代码仓库和 Issues。

这个参考服务器解决了开发者想让 AI 安全访问 GitHub 数据的问题,适合需要自动化代码审查或 Issue 管理的团队。但注意它只是参考实现,生产环境得自己加固安全。

编码与调试
89.7k

by Context7

热门

Context7 是实时拉取最新文档和代码示例的智能助手,让你告别过时资料。

它能解决开发者查找文档时信息滞后的问题,特别适合快速上手新库或跟进更新。不过,依赖外部源可能导致偶尔的数据延迟,建议结合官方文档使用。

编码与调试
60.2k

by tldraw

热门

tldraw 是让 AI 助手直接在无限画布上绘图和协作的 MCP 服务器。

这解决了 AI 只能输出文本、无法视觉化协作的痛点——想象让 Claude 帮你画流程图或白板讨论。最适合需要快速原型设计或头脑风暴的开发者。不过,目前它只是个基础连接器,你得自己搭建画布应用才能发挥全部潜力。

编码与调试
49.9k

评论