原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Helm MCP

作者:SCGIS-Wales版本 0.5.0i★ –i在你的电脑上运行
注册名称io.github.SCGIS-Wales/helm-mcp

安装

概览

作者提供的说明(英文原文)

The full Helm CLI surface as 46 MCP tools, backed by the Helm v3 and v4 Go SDKs.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: KUBECONFIG, HELM_MCP_BINARY

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "helm": {
      "command": "uvx",
      "args": [
        "helm-mcp"
      ],
      "env": {
        "KUBECONFIG": "your-value",
        "HELM_MCP_BINARY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add helm --env KUBECONFIG=your-value --env HELM_MCP_BINARY=your-value -- uvx helm-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "helm": {
      "command": "uvx",
      "args": [
        "helm-mcp"
      ],
      "env": {
        "KUBECONFIG": "your-value",
        "HELM_MCP_BINARY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "helm": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "helm-mcp"
      ],
      "env": {
        "KUBECONFIG": "your-value",
        "HELM_MCP_BINARY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • KUBECONFIG env
    Path to the kubeconfig file. Defaults to ~/.kube/config.
  • HELM_MCP_BINARY env
    Explicit path to the helm-mcp Go binary. Auto-detected when unset.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 SCGIS-Wales 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 5569 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 5569 个服务器的 52% 更新
  • 基础检查结果等于或优于此分类中其他 5569 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Helm MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.5.0)于29天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv), Docker。

有什么可以替代它?

同一分类中有:GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

作者:github广泛使用★ 3.4万5天前更新

电脑或云端

Desktop Commander

MCP server for terminal commands, file operations, and process management

作者:wonderwhy-er广泛使用↓ 71万/周★ 1万18天前更新

在你的电脑上运行

Cloudflare MCP

Cloudflare MCP servers

作者:cloudflare广泛使用★ 444614个月前更新

在云端运行✓ mcp.cloudflare.com

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

An open-source MCP (Model Context Protocol) server that gives AI assistants full access to Helm — the Kubernetes package manager. Built with the native Helm Go SDK, supporting both Helm 3.x and 4.x in a single binary.

Use natural language to manage your Kubernetes deployments.

Connect helm-mcp to Claude, Cursor, VS Code, or any MCP-compatible client to install charts, manage releases, search repositories, and more — all through conversation.


Table of Contents

  • Why helm-mcp?
  • Installation
  • Quick Start
  • MCP Client Configuration
  • MCP Protocol Support
  • Available Tools
  • Tool Annotations
  • Structured Output
  • Helm CLI Coverage
  • Kubernetes Authentication
  • Helm Version Selection
  • Python Package
  • Resilience Configuration (Python)
  • Response Payload Management
  • Known Limitations
  • Security
  • Authentication (OIDC/OAuth2)
  • On-Behalf-Of (OBO) Token Exchange
  • Development
  • Architecture
  • Contributing
  • Community
  • License

Why helm-mcp?

  • 46 MCP tools covering every Helm CLI command (minus shell completion and help)
  • Dual Helm SDK support — Helm v3 and v4 via native Go SDK (not CLI wrappers)
  • Two transport modes — stdio (default) and Streamable HTTP, stateless by default
  • Cloud provider ready — EKS, GKE, AKS kubeconfig formats work out of the box
  • Security first — Linux process hardening, credential memory zeroing, input validation, path traversal prevention
  • Python wrapper — FastMCP-based proxy that auto-discovers all tools
  • Forward proxy support — respects HTTP_PROXY, HTTPS_PROXY, NO_PROXY

Installation

Pre-built Binaries

Download the latest release for your platform from GitHub Releases:

# macOS (Apple Silicon)

curl -LO https://github.com/SCGIS-Wales/helm-mcp/releases/latest/download/helm-mcp-darwin-arm64 chmod +x helm-mcp-darwin-arm64 sudo mv helm-mcp-darwin-arm64 /usr/local/bin/helm-mcp

macOS (Intel)

curl -LO https://github.com/SCGIS-Wales/helm-mcp/releases/latest/download/helm-mcp-darwin-amd64 chmod +x helm-mcp-darwin-amd64 sudo mv helm-mcp-darwin-amd64 /usr/local/bin/helm-mcp

Linux (amd64)

curl -LO https://github.com/SCGIS-Wales/helm-mcp/releases/latest/download/helm-mcp-linux-amd64 chmod +x helm-mcp-linux-amd64 sudo mv helm-mcp-linux-amd64 /usr/local/bin/helm-mcp

Linux (arm64)

curl -LO https://github.com/SCGIS-Wales/helm-mcp/releases/latest/download/helm-mcp-linux-arm64 chmod +x helm-mcp-linux-arm64 sudo mv helm-mcp-linux-arm64 /usr/local/bin/helm-mcp

Build from Source

Requires Go 1.27.2+.

git clone https://github.com/SCGIS-Wales/helm-mcp.git

cd helm-mcp make build

Docker
docker build -t helm-mcp .

docker run -v ~/.kube:/home/helmuser/.kube:ro helm-mcp --mode stdio

Python Package
pip install helm-mcp

See Python Package below for full details.

Quick Start

stdio mode (for Claude Code, Cursor, etc.)
helm-mcp --mode stdio
HTTP mode (Streamable HTTP)
helm-mcp --mode http

HTTP mode listens on 127.0.0.1:8080 by default. To accept remote clients, configure authentication (see Authentication) and bind explicitly, for example --addr 0.0.0.0:8080.

HTTP mode is stateless by default (MCP 2026-07-28): there is no initialize handshake and no Mcp-Session-Id header, so the server can sit behind a plain round-robin load balancer with no sticky sessions and no shared session store. Clients speaking an older protocol revision still work — the SDK negotiates down automatically.

If a client needs the legacy per-session behaviour:

helm-mcp --mode http --stateless=false

Removed in v0.2.0: `--mode sse`. The HTTP+SSE transport has been

deprecated by the MCP specification since 2025-03-26 and is formally

Deprecated under the 2026-07-28 feature lifecycle policy. Use

--mode http, which serves Streamable HTTP on the same address.

MCP Client Configuration

Claude Desktop

Add to ~/.claude/claude_desktop_config.json:

{

"mcpServers": { "helm": { "command": "helm-mcp", "args": ["--mode", "stdio"] } } }

Claude Code
claude mcp add helm -- helm-mcp --mode stdio
Cursor / Windsurf / VS Code

Add to your MCP server configuration:

{

"helm-mcp": { "command": "helm-mcp", "args": ["--mode", "stdio"] } }

Remote / HTTP Clients

Start the server in HTTP mode, then connect any MCP-compatible client to the endpoint:

helm-mcp --mode http

MCP endpoint: http://localhost:8080/mcp

MCP Protocol Support

helm-mcp implements MCP `2026-07-28` and negotiates down to earlier revisions (2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05) for older clients, so upgrading the server does not require upgrading your client.

FeatureStatus
ToolsSupported: 46 tools, each with a top level title, annotations and (where the result has a stable shape) an output schema
ProgressSupported. helm_install, helm_upgrade, helm_uninstall, helm_rollback and helm_test send notifications/progress heartbeats every 10 seconds when the request carries a progress token, so clients that reset their timeout on progress keep waiting for long wait operations
CancellationSupported. In HTTP mode a dropped request cancels the running tool call, as Ctrl+C cancels the helm CLI (--propagate-cancellation=false to let it finish)
Stateless transportSupported and the default for --mode http (--stateless=false to opt out)
server/discoverSupported
Deterministic tools/list orderSupported — tools are returned sorted by name so clients and prompt caches keep hitting
Server instructionsSupported — the server explains version selection, cluster targeting and destructive-tool safety
Resources / PromptsNot applicable — every Helm operation is a tool call
Tasks extensionNot implemented. Attractive for long helm install --wait runs, but client support is still thin. Tracked as a follow-up.
MRTR / ElicitationNot implemented, deliberately. Helm tools take all their input as arguments, so there is no mid-call question to ask.
Roots / Sampling / LoggingNot implemented. All three are deprecated as of 2026-07-28 (SEP-2577).
HTTP+SSE transportRemoved in v0.2.0 — deprecated by the specification. Use --mode http.

Available Tools (46)

Release Management (14)
ToolDescription
helm_installInstall a Helm chart as a new release
helm_upgradeUpgrade a release to a new chart version or values
helm_uninstallUninstall a release and remove associated resources
helm_rollbackRollback a release to a previous revision
helm_listList releases (supports filters, sorting, pagination)
helm_statusDisplay release status, revision, chart, and values
helm_historyShow revision history of a release
helm_testRun the test suite for a release
helm_get_allGet all info (values, manifest, hooks, notes) for a release
helm_get_hooksGet hooks for a release
helm_get_manifestGet the Kubernetes manifest for a release
helm_get_metadataGet metadata for a release
helm_get_notesGet notes for a release
helm_get_valuesGet values for a release (user-supplied or computed)
Chart Management (14)
ToolDescription
helm_createCreate a new chart, optionally from a starter
helm_lintLint a chart for issues and best practices
helm_templateRender templates and hooks locally without installing
helm_packagePackage a chart directory into an archive (.tgz)
helm_pullDownload a chart from a repository or OCI registry
helm_pushPush a chart archive to an OCI registry
helm_verifyVerify a chart has a valid provenance file
helm_show_allShow all chart info (Chart.yaml, values, README, CRDs)
helm_show_chartShow Chart.yaml of a chart
helm_show_crdsShow CRDs of a chart
helm_show_readmeShow README of a chart
helm_show_valuesShow default values of a chart
helm_dependency_buildBuild charts/ directory from Chart.lock
helm_dependency_listList dependencies for a chart
Repository Management (5)
ToolDescription
helm_repo_addAdd a chart repository
helm_repo_listList configured chart repositories
helm_repo_updateUpdate chart repository indexes
helm_repo_removeRemove chart repositories
helm_repo_indexGenerate an index file for chart archives
Registry / OCI (2)
ToolDescription
helm_registry_loginLogin to an OCI registry
helm_registry_logoutLogout from an OCI registry
Search (2)
ToolDescription
helm_search_hubSearch Artifact Hub for charts
helm_search_repoSearch locally configured repositories
Plugin Management (6)
ToolDescription
helm_plugin_installInstall a Helm plugin
helm_plugin_listList installed plugins
helm_plugin_uninstallUninstall a plugin
helm_plugin_updateUpdate a plugin
helm_plugin_packagePackage a plugin directory into a signed archive (v4 only)
helm_plugin_verifyVerify a packaged plugin's signature and provenance (v4 only)
Environment (2)
ToolDescription
helm_envPrint Helm environment information
helm_versionPrint Helm SDK version information
Dependency Update (1)
ToolDescription
helm_dependency_updateUpdate charts/ based on Chart.yaml

Tool Annotations

Every tool carries MCP annotations so a client — or an agent deciding what to call — can tell a read at a glance from a change to your cluster.

AnnotationMeaningTools

| readOnlyHint: true | Only reads state; safe to call freely | helm_list, helm_status, helm_history, all helm_get_*, all helm_show_*, helm_repo_list, helm_plugin_list, helm_dependency_list, helm_env,

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx