MCP Server Kubernetes 19122544

MCP运维云端

提供方 Flux159 · 包名 mcp-chat

运维云端 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

MCP Server Kubernetes是一个能够连接并管理Kubernetes集群的服务器,支持从多个源加载kubeconfig,并提供丰富的Kubernetes操作功能。

一句话选型结论

按资料字段整理

MCP Server Kubernetes 19122544 属于运维云端类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

Kubernetes管理TypeScript本地部署集群操作云原生工具DevOps工具容器编排

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx mcp-chat --server "npx mcp-server-kubernetes"

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

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后客户端会列出约 22 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

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

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

部署与发布

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

监控与告警

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

选择建议

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

值得选的地方

  • 资料标注 22 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。
  • 仓库有一定关注度(星标 1,393),遇到问题更容易搜到资料。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Server Kubernetes 19122544当前 22 stdio · 本地进程 本地部署 有 2026-05-17
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

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Flux159上游标注的维护方 Flux159
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时mcp-chat · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

MCP Server Kubernetes

MCP Server that can connect to a Kubernetes cluster and manage it. Supports loading kubeconfig from multiple sources in priority order.

https://github.com/user-attachments/assets/f25f8f4e-4d04-479b-9ae0-5dac452dd2ed

Installation & Usage

Prerequisites

Before using this MCP server with any tool, make sure you have:

  1. kubectl installed and in your PATH
  2. A valid kubeconfig file with contexts configured
  3. Access to a Kubernetes cluster configured for kubectl (e.g. minikube, Rancher Desktop, GKE, etc.)
  4. Helm v3 installed and in your PATH (no Tiller required). Optional if you don't plan to use Helm.

You can verify your connection by running kubectl get pods in a terminal to ensure you can connect to your cluster without credential issues.

By default, the server loads kubeconfig from ~/.kube/config. For additional authentication options (environment variables, custom paths, etc.), see ADVANCED_README.md.

Claude Code

Add the MCP server to Claude Code using the built-in command:```bash
claude mcp add kubernetes -- npx mcp-server-kubernetes


This will automatically configure the server in your Claude Code MCP settings.

### Codex

Add the MCP server to Codex CLI using the built-in command:```bash
codex mcp add kubernetes -- npx mcp-server-kubernetes

This registers the server globally in ~/.codex/config.toml and makes its tools available in all Codex sessions.

Claude Desktop

Add the following configuration to your Claude Desktop config file:```json
{
"mcpServers": {
"kubernetes": {
"command": "npx",
"args": ["mcp-server-kubernetes"]
}
}
}


### Claude Desktop Connector via mcpb

MCP Server Kubernetes is also available as a mcpb (formerly dxt) extension. In Claude Desktop, go to Settings (`Cmd+,` on Mac) -> Extensions -> Browse Extensions and scroll to find mcp-server-kubernetes in the modal. Install it & it will install & utilize kubectl via command line & your kubeconfig.

To manually install, you can also get the .mcpb by going to the latest Release and downloading it.

### VS Code

VS Code has built-in MCP support. Use the one-click install button above, or add the server to `.vscode/mcp.json` in your workspace (or to your user `mcp.json` via **MCP: Open User Configuration**):```json
{
  "servers": {
    "kubernetes": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-server-kubernetes"]
    }
  }
}

Cursor

Cursor supports MCP servers through its AI integration. Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):```json
{
"mcpServers": {
"kubernetes": {
"command": "npx",
"args": ["mcp-server-kubernetes"]
}
}
}


The server will automatically connect to your current kubectl context. You can verify the connection by asking the AI assistant to list your pods or create a test deployment.

### Muse Code

Muse Code reads MCP servers from the `mcp_servers` block of `~/.config/muse/settings.json`. The file must include `"schema_version": 1`:```json
{
  "schema_version": 1,
  "mcp_servers": {
    "kubernetes": {
      "transport": "stdio",
      "command": "npx",
      "args": ["mcp-server-kubernetes"]
    }
  }
}

To connect over Streamable HTTP instead, first start the server in HTTP mode (it serves /mcp on port 3000 by default; see Streamable HTTP Transport):```bash
ENABLE_UNSAFE_STREAMABLE_HTTP_TRANSPORT=1 npx mcp-server-kubernetes


Then point Muse Code at that endpoint with the `streamable_http` transport (`headers` is optional):```json
{
  "schema_version": 1,
  "mcp_servers": {
    "kubernetes": {
      "transport": "streamable_http",
      "url": "http://localhost:3000/mcp",
      "mode": "optional"
    }
  }
}

"mode": "optional" lets Muse Code start with a warning if the HTTP server isn't running, instead of aborting.

Start a new Muse Code session after editing the file, then run /mcp to confirm the kubernetes server and its tools are connected.

Usage with mcp-chat

mcp-chat is a CLI chat client for MCP servers. You can use it to interact with the Kubernetes server.```shell
npx mcp-chat --server "npx mcp-server-kubernetes"


Alternatively, pass it your existing Claude Desktop configuration file from above (Linux should pass the correct path to config):

Mac:```shell
npx mcp-chat --config "~/Library/Application Support/Claude/claude_desktop_config.json"

Windows:```shell
npx mcp-chat --config "%APPDATA%\Claude\claude_desktop_config.json"


## Features

- [x] Connect to a Kubernetes cluster
- [x] Unified kubectl API for managing resources
  - Get or list resources with `kubectl_get`
  - Describe resources with `kubectl_describe`
  - List resources with `kubectl_get`
  - Create resources with `kubectl_create`
  - Apply YAML manifests with `kubectl_apply`
  - Delete resources with `kubectl_delete`
  - Get logs with `kubectl_logs`
  - Manage kubectl contexts with `kubectl_context`
  - Explain Kubernetes resources with `explain_resource`
  - List API resources with `list_api_resources`
  - Scale resources with `kubectl_scale`
  - Update field(s) of a resource with `kubectl_patch`
  - Manage deployment rollouts with `kubectl_rollout`
  - Execute any kubectl command with `kubectl_generic`
  - Verify connection with `ping`
- [x] Advanced operations
  - Scale deployments with `kubectl_scale` (replaces legacy `scale_deployment`)
  - Port forward to pods and services with `port_forward`
  - Run Helm operations
    - Install, upgrade, and uninstall charts
    - Support for custom values, repositories, and versions
    - Template-based installation (`helm_template_apply`) to bypass authentication issues
    - Template-based uninstallation (`helm_template_uninstall`) to bypass authentication issues
  - Pod cleanup operations
    - Clean up problematic pods (`cleanup_pods`) in states: Evicted, ContainerStatusUnknown, Completed, Error, ImagePullBackOff, CrashLoopBackOff
  - Node management operations
    - Cordoning, draining, and uncordoning nodes (`node_management`) for maintenance and scaling operations
- [x] Troubleshooting Prompt (`k8s-diagnose`)
  - Guides through a systematic Kubernetes troubleshooting flow for pods based on a keyword and optional namespace.
- [x] Non-destructive mode for read and create/update-only access to clusters
- [x] Secrets masking for security (masks sensitive data in `kubectl get secrets` commands, does not affect logs)
- [x] **OpenTelemetry Observability** (opt-in)
  - Distributed tracing for all tool calls
  - Export to Jaeger, Tempo, Grafana, or any OTLP backend
  - Configurable sampling strategies
  - Rich span attributes (tool name, duration, K8s context, errors)
  - See docs/OBSERVABILITY.md for details

## Observability

The MCP Kubernetes server includes optional **OpenTelemetry integration** for comprehensive observability. This feature is disabled by default and can be enabled via environment variables or Helm configuration.

### Quick Start

Enable observability with environment variables:```bash
export ENABLE_TELEMETRY=true
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317

npx mcp-server-kubernetes

What Gets Traced

  • All tool calls: kubectl_get, kubectl_apply, kubectl_logs, etc.
  • Execution duration: How long each operation takes
  • Success/failure status: Automatic error tracking
  • Kubernetes context: Namespace, context, resource type
  • Rich metadata: Host, process, and custom attributes

Backends Supported

Works with any OTLP-compatible backend:
- Jaeger (open source)
- Grafana Tempo (open source)
- Grafana Cloud (commercial)
- Datadog, New Relic, Honeycomb, Lightstep, AWS X-Ray

Configuration

See docs/OBSERVABILITY.md for comprehensive documentation including:
- Configuration options
- Deployment examples (Kubernetes, Helm, Claude Code)
- Sampling strategies
- Production best practices
- Troubleshooting guide

Example with Jaeger```bash

Start Jaeger

docker run -d --name jaeger \
-e COLLECTOR_OTLP_ENABLED=true \
-p 16686:16686 \
-p 4317:4317 \
jaegertracing/all-in-one:latest

Enable telemetry

export ENABLE_TELEMETRY=true
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
export OTEL_TRACES_SAMPLER=always_on

Run server

npx mcp-server-kubernetes

View traces: http://localhost:16686


## Prompts

The MCP Kubernetes server includes specialized prompts to assist with common diagnostic operations.

### /k8s-diagnose Prompt

This prompt provides a systematic troubleshooting flow for Kubernetes pods. It accepts a `keyword` to identify relevant pods and an optional `namespace` to narrow the search.
The prompt's output will guide you through an autonomous troubleshooting flow, providing instructions for identifying issues, collecting evidence, and suggesting remediation steps.

## Local Development

Make sure that you have bun installed. Clone the repo & install dependencies:```bash
git clone https://github.com/Flux159/mcp-server-kubernetes.git
cd mcp-server-kubernetes
bun install

Development Workflow

  1. Start the server in development mode (watches for file changes):```bash
    bun run dev

2. Run unit tests:```bash
bun run test
  1. Build the project:```bash
    bun run build

4. Local Testing with Inspector```bash
npx @modelcontextprotocol/inspector node dist/index.js
# Follow further instructions on terminal for Inspector link
  1. Local testing with Claude Desktop```json
    {
    "mcpServers": {
    "mcp-server-kubernetes": {
    "command": "node",
    "args": ["/path/to/your/mcp-server-kubernetes/dist/index.js"]
    }
    }
    }

6. Local testing with mcp-chat```bash
bun run chat

Contributing

See the CONTRIBUTING.md file for details.

Advanced

Non-Destructive Mode

You can run the server in a non-destructive mode that disables all destructive operations (delete pods, delete deployments, delete namespaces, etc.):```shell
ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS=true npx mcp-server-kubernetes


For Claude Desktop configuration with non-destructive mode:```json
{
  "mcpServers": {
    "kubernetes-readonly": {
      "command": "npx",
      "args": ["mcp-server-kubernetes"],
      "env": {
        "ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS": "true"
      }
    }
  }
}

Commands Available in Non-Destructive Mode

All read-only and resource creation/update operations remain available:

  • Resource Information: kubectl_get, kubectl_describe, kubectl_logs, explain_resource, list_api_resources
  • Resource Creation/Modification: kubectl_apply, kubectl_create, kubectl_scale, kubectl_patch, kubectl_rollout
  • Helm Operations: install_helm_chart, upgrade_helm_chart, helm_template_apply, helm_template_uninstall
  • Connectivity: port_forward, stop_port_forward
  • Context Management: kubectl_context

Commands Disabled in Non-Destructive Mode

The following destructive operations are disabled:

  • kubectl_delete: Deleting any Kubernetes resources
  • uninstall_helm_chart: Uninstalling Helm charts
  • cleanup: Cleanup of managed resources
  • cleanup_pods: Cleaning up problematic pods
  • node_management: Node management operations (can drain nodes)
  • kubectl_generic: General kubectl command access (may include destructive operations)
  • exec_in_pod: Arbitrary command execution inside a pod (can read service-account tokens and change state)

For additional advanced features, see the ADVANCED_README.md and also the docs folder for specific information on helm_install, helm_template_apply, node management & pod cleanup.

Architecture

See this DeepWiki link for a more indepth architecture overview created by Devin.

This section describes the high-level architecture of the MCP Kubernetes server.

Request Flow

The sequence diagram below illustrates how requests flow through the system:```mermaid
sequenceDiagram
participant Client
participant Transport as Transport Layer
participant Server as MCP Server
participant Filter as Tool Filter
participant Handler as Request Handler
participant K8sManager as KubernetesManager
participant K8s as Kubernetes API

Note over Transport: StdioTransport or<br>SSE Transport

Client->>Transport: Send Request
Transport->>Server: Forward Request

alt Tools Request
    Server->>Filter: Filter available tools
    Note over Filter: Remove destructive tools<br>if in non-destructive mode
    Filter->>Handler: Route to tools handler

    alt kubectl operations
        Handler->>K8sManager: Execute kubectl operation
        K8sManager->>K8s: Make API call
    else Helm operations
        Handler->>K8sManager: Execute Helm operation
        K8sManager->>K8s: Make API call
    else Port Forward operations
        Handler->>K8sManager: Set up port forwarding
        K8sManager->>K8s: Make API call
    end

    K8s-->>K8sManager: Return result
    K8sManager-->>Handler: Process response
    Handler-->>Server: Return tool result
else Resource Request
    Server->>Handler: Route to resource handler
    Handler->>K8sManager: Get resource data
    K8sManager->>K8s: Query API
    K8s-->>K8sManager: Return data
    K8sManager-->>Handler: Format response
    Handler-->>Server: Return resource data
end

Server-->>Transport: Send Response
Transport-->>Client: Return Final Response

See this DeepWiki link for a more indepth architecture overview created by Devin.

## Publishing new release

Go to the releases page, click on "Draft New Release", click "Choose a tag" and create a new tag by typing out a new version number using "v{major}.{minor}.{patch}" semver format. Then, write a release title "Release v{major}.{minor}.{patch}" and description / changelog if necessary and click "Publish Release".

This will create a new tag which will trigger a new release build via the cd.yml workflow. Once successful, the new release will be published to npm. Note that there is no need to update the package.json version manually, as the workflow will automatically update the version number in the package.json file & push a commit to main.

## Not planned

Adding clusters to kubectx.

## Star History

## 🖊️ Cite

If you find this repo useful, please cite:```
@software{Patel_MCP_Server_Kubernetes_2024,
author = {Patel, Paras and Sonwalkar, Suyog},
month = jul,
title = {{MCP Server Kubernetes}},
url = {https://github.com/Flux159/mcp-server-kubernetes},
version = {2.5.0},
year = {2024}
}

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP Server Kubernetes 19122544 怎么安装?

在客户端按下面的安装命令接入:npx mcp-chat --server "npx mcp-server-kubernetes"。对应的包名是 mcp-chat。装完在客户端配置里引用同一个包或端点。

MCP Server Kubernetes 19122544 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Server Kubernetes 19122544 收费吗?

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

MCP Server Kubernetes 19122544 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

MCP Server Kubernetes 19122544 支持哪些客户端?

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

MCP Server Kubernetes 19122544 能提供哪些能力?

资料显示约 22 个工具;能力标签包括 Kubernetes管理、容器编排、TypeScript、Claude。具体工具清单以官方文档为准。

MCP Server Kubernetes 19122544 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

MCP Server Kubernetes 19122544 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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