
K8scortex Mcp
io.github.apatilgtn由 GitHub 账号 apatilgtn 发布v1.1.3更新于 Oct 29, 2026
Kubernetes MCP server: 75 tools for GKE, AKS, EKS, RBAC, audit logging, GitOps, multi-cluster.
概览
受治理的 Kubernetes MCP 网关,提供 75 个工具,用于在 GKE、EKS、AKS、OpenShift 和本地集群上查看并安全变更工作负载。
- 可以做什么
- 列出并查看工作负载、节点、StatefulSet、DaemonSet 和 Deployment,并获取 Pod 日志
- 读取配置与诊断信息:ConfigMap、配额、事件、PVC、告警事件、HPA 状态、节点压力和有效权限
- 执行受控写操作,例如扩缩 Deployment 或重启 Pod,默认以 dry-run 模拟方式运行
- 通过通用读取工具列出和获取任意资源类型
- 列出已注册集群,并跨 kubeconfig、EKS、GKE 和 Key Vault 来源比较或查看集群信息
- 适用场景
- 当助手需要排查或运维 Kubernetes 集群,而你希望用角色分级、按集群策略、默认 dry-run 和审计记录来替代直接交出 kubeconfig 时适用。适合管理多云多集群的平台团队。
- 运行要求
- 通过 npx 或已发布容器镜像以 stdio 在本地运行;需要 Node.js 22+ 和可用的 kubeconfig(KUBECONFIG,默认 ~/.kube/config)。可选 CLUSTERS_CONFIG 注册文件以接入 EKS、GKE 和 Key Vault 集群,并需要相应云凭据,如 AWS 默认凭据链、Google 应用默认凭据或 Azure 托管标识。K8SCORTEX_STDIO_ROLES 设定会话角色,默认为 platform-engineer。
安装
在 SourceWeft 中
- 打开 控制台中的 K8scortex Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
K8sCortex — Kubernetes MCP Server
[CI] [npm version] [smithery badge] [License: MIT]
Give your AI agents Kubernetes access your security team will sign off on. K8sCortex is one governed MCP gateway for GKE, EKS, AKS, OpenShift and local clusters: SSO on every request, role tiers, per-cluster policies, dry-run by default, and an audit log of who asked for what.
Most Kubernetes MCP servers hand an agent your kubeconfig. K8sCortex sits in between: it decides, per person and per cluster, which of its 75 tools may run, and records every call. Clusters from different clouds live in one registry, with credentials minted on demand.
A real Claude Code session with K8sCortex as its only tool, on a throwaway prod cluster: the developer is denied the rollback, the release manager is blocked by the prod policy, the SRE fixes it. Watch all five scenarios (97 s): incident, release drift, flash-sale scaling, password rotation, node maintenance. How it was recorded.
Features
- Curated multi-domain toolset across workload, deployment, configuration, observability, jobs, networking, GitOps, cluster admin, and generic read paths
- Multi-cloud cluster providers — kubeconfig contexts, Amazon EKS (IAM/IRSA), Google GKE (Workload Identity) and Azure Key Vault, mixed in one registry
- Multi-cluster routing — target any registered cluster with a single
clusterparameter; writes require an explicit cluster when several are registered - Any OIDC identity provider (Entra ID, Okta, Cognito, Keycloak, Google) with per-tool RBAC (5-tier role hierarchy) and per-cluster policies
- Structured audit logging — every tool call recorded with caller identity, arguments, and outcome
- Dual transport — SSE/HTTP for programmatic clients + stdio for Claude Desktop
- Short-lived credentials — EKS and GKE tokens are minted on demand and cached only until they expire
- Dry-run safety — destructive tools default to simulation mode
- Generic read coverage — list/get support for resources outside curated write paths to avoid troubleshooting dead-ends
Install
Claude Desktop, Claude Code, Cursor and other MCP clients (stdio)
Requires Node.js 22+ and a working kubeconfig. Add to your client's MCP configuration (Claude Desktop: claude_desktop_config.json):
developer gives a read-only session; remove it for the full toolset. With Claude Code: claude mcp add k8scortex -- npx -y k8scortex-mcp.
As a shared service for a team (HTTP + OIDC)
With the Helm chart (read-only RBAC by default; see the chart README for writes and more clouds):
Plain manifests rendered from the chart are in kubernetes/. Or run the image directly:
Run it in a management cluster with Workload Identity / IRSA / managed identity for the cloud providers, expose /mcp internally, and ship the audit log to your SIEM. See Multi-cloud setup and Authentication.
Develop
Prerequisites
- Node.js ≥ 22 (the GKE provider's
google-auth-libraryand thejosedependency ofjwks-rsaneed it) - A Kubernetes cluster (minikube, kind, GKE, EKS, AKS or OpenShift)
kubectlconfigured with a valid context
Install & Run
Connect with MCP Inspector
Connect Claude Desktop to a local build
Point the client at your build instead of the npm package:
Restart Claude Desktop. Ask: "List all pods in the default namespace".
Every context in your kubeconfig is available as a cluster, so you can ask "Compare the web app's ArgoCD revision between kind-dev and prod-eks". Set K8SCORTEX_STDIO_ROLES=developer to give the local session read-only tools.
Multi-cloud setup
K8sCortex picks its cluster source from the environment:
DEFAULT_CLUSTER chooses the cluster used when a tool call names none. Read-only tools fall back to it; mutating tools require an explicit cluster whenever more than one cluster is registered.
Cluster registry file
The EKS and GKE providers use optional dependencies (@aws-sdk/client-eks, @aws-sdk/credential-providers, @smithy/signature-v4, @aws-crypto/sha256-js, google-auth-library) that npm installs by default. The identity needs eks:DescribeCluster plus an EKS access entry, or container.clusters.get plus Kubernetes RBAC on GKE.
Per-cluster policies
Policies match clusters by name glob (match) and/or labels, and can only tighten the global role table:
minRoleraises the role required on matching clusters (appliesTo: "mutating"limits it to write tools)denyToolsdisables tools for everyone on matching clusters
compare_clusters is checked against both clusters it reads.
Authentication
HTTP mode refuses to start unless an identity provider is configured (or DISABLE_AUTH=true):
Tools
K8sCortex intentionally keeps writes curated and governed, while allowing flexible read access for diagnostics.
For the evolving full catalog, see docs/developer-guide.md.
Managed Risk
The largest functional risk in Kubernetes MCP is dead-end visibility on non-curated resources (for example StatefulSets, DaemonSets, PVCs, or CRDs). K8sCortex addresses this by combining:
- Governed writes: high-impact operations remain explicit, role-gated, and often dry-run by default.
- Flexible reads: generic read tools cover arbitrary resource kinds for diagnostics.
This keeps the governance posture strong while preserving practical troubleshooting coverage.
Scope Boundaries (v1)
K8sCortex is designed as a governed platform interface, not an unrestricted Kubernetes super-client.
- Generic write for any resource: intentionally out of scope in v1. Writes are curated and role-gated by design.
- Pod exec interactive sessions: intentionally out of scope in v1. This requires stronger session controls and command-level auditing that are planned for a later version.
Architecture
Security
- Authentication: OIDC tokens (issuer, audience and signature) validated on every request; sessions are bound to the user that created them
- Authorization: Role-based tool access (
developer→platform-engineer), tightened per cluster by policies - Audit: JSON-structured log per invocation with user, tool, cluster, provider and outcome; secret values are redacted
- Network: ClusterIP only — no public endpoint
- Credentials: Short-lived EKS/GKE tokens or Key Vault kubeconfigs, cached only until expiry
Project Structure
Testing
Every push runs lint, typecheck, unit tests, auth/audit integration tests and a 164-scenario end-to-end matrix on two KWOK clusters (GKE-like and EKS-like). Releases are also checked against a real GKE cluster with npm run test:e2e:gke: v1.1.1 passed 100/100 on GKE 1.36, and that run found the three GKE-specific bugs fixed in the changelog.
Documentation
- Developer Guide — How to connect, available tools, example queries
- Operator Runbook — Deploy, upgrade, rotate credentials, incident response
- SLOs — Availability, latency, and alerting targets
- Changelog
Contributing
Issues and pull requests are welcome. Run npm run release:gate before opening a PR; new tools need a role in src/roles.ts and a case in the KWOK matrix.
License
来源:README.md,提交 68782ec
工具
0版本历史
2- v1.1.3最新Oct 29, 2026
- v1.0.2Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分