Helm MCP

Name: Helm MCP
Author: SCGIS-Wales

by SCGIS-Walesversion 0.5.0i★ –iRuns on your computer

Registry nameio.github.SCGIS-Wales/helm-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 1.7K/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: KUBECONFIG, HELM_MCP_BINARY

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

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.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account SCGIS-Wales, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 5564 servers in this category
Published to the registry more recently than 52% of the other 5564 servers in this category
Basic checks equal to or better than 100% of the other 5564 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Helm MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 29 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 5 days ago

Computer or cloud

Install

Desktop Commander

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

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 17 days ago

Runs on your computer

Install

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

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.

Feature	Status
Tools	Supported: 46 tools, each with a top level `title`, annotations and (where the result has a stable shape) an output schema
Progress	Supported. `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
Cancellation	Supported. 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 transport	Supported and the default for `--mode http` (`--stateless=false` to opt out)
`server/discover`	Supported
Deterministic `tools/list` order	Supported — tools are returned sorted by name so clients and prompt caches keep hitting
Server instructions	Supported — the server explains version selection, cluster targeting and destructive-tool safety
Resources / Prompts	Not applicable — every Helm operation is a tool call
Tasks extension	Not implemented. Attractive for long `helm install --wait` runs, but client support is still thin. Tracked as a follow-up.
MRTR / Elicitation	Not implemented, deliberately. Helm tools take all their input as arguments, so there is no mid-call question to ask.
Roots / Sampling / Logging	Not implemented. All three are deprecated as of `2026-07-28` (SEP-2577).
HTTP+SSE transport	Removed in v0.2.0 — deprecated by the specification. Use `--mode http`.

Available Tools (46)

Release Management (14)

Tool	Description
`helm_install`	Install a Helm chart as a new release
`helm_upgrade`	Upgrade a release to a new chart version or values
`helm_uninstall`	Uninstall a release and remove associated resources
`helm_rollback`	Rollback a release to a previous revision
`helm_list`	List releases (supports filters, sorting, pagination)
`helm_status`	Display release status, revision, chart, and values
`helm_history`	Show revision history of a release
`helm_test`	Run the test suite for a release
`helm_get_all`	Get all info (values, manifest, hooks, notes) for a release
`helm_get_hooks`	Get hooks for a release
`helm_get_manifest`	Get the Kubernetes manifest for a release
`helm_get_metadata`	Get metadata for a release
`helm_get_notes`	Get notes for a release
`helm_get_values`	Get values for a release (user-supplied or computed)

Chart Management (14)

Tool	Description
`helm_create`	Create a new chart, optionally from a starter
`helm_lint`	Lint a chart for issues and best practices
`helm_template`	Render templates and hooks locally without installing
`helm_package`	Package a chart directory into an archive (.tgz)
`helm_pull`	Download a chart from a repository or OCI registry
`helm_push`	Push a chart archive to an OCI registry
`helm_verify`	Verify a chart has a valid provenance file
`helm_show_all`	Show all chart info (Chart.yaml, values, README, CRDs)
`helm_show_chart`	Show Chart.yaml of a chart
`helm_show_crds`	Show CRDs of a chart
`helm_show_readme`	Show README of a chart
`helm_show_values`	Show default values of a chart
`helm_dependency_build`	Build charts/ directory from Chart.lock
`helm_dependency_list`	List dependencies for a chart

Repository Management (5)

Tool	Description
`helm_repo_add`	Add a chart repository
`helm_repo_list`	List configured chart repositories
`helm_repo_update`	Update chart repository indexes
`helm_repo_remove`	Remove chart repositories
`helm_repo_index`	Generate an index file for chart archives

Registry / OCI (2)

Tool	Description
`helm_registry_login`	Login to an OCI registry
`helm_registry_logout`	Logout from an OCI registry

Search (2)

Tool	Description
`helm_search_hub`	Search Artifact Hub for charts
`helm_search_repo`	Search locally configured repositories

Plugin Management (6)

Tool	Description
`helm_plugin_install`	Install a Helm plugin
`helm_plugin_list`	List installed plugins
`helm_plugin_uninstall`	Uninstall a plugin
`helm_plugin_update`	Update a plugin
`helm_plugin_package`	Package a plugin directory into a signed archive (v4 only)
`helm_plugin_verify`	Verify a packaged plugin's signature and provenance (v4 only)

Environment (2)

Tool	Description
`helm_env`	Print Helm environment information
`helm_version`	Print Helm SDK version information

Dependency Update (1)

Tool	Description
`helm_dependency_update`	Update 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.

Annotation	Meaning	Tools

| 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,

Only the beginning is shown; read the rest in the repo

Helm MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Table of Contents

Why helm-mcp?

Installation

Pre-built Binaries

macOS (Intel)

Linux (amd64)

Linux (arm64)

Build from Source

Docker

Python Package

Quick Start

stdio mode (for Claude Code, Cursor, etc.)

HTTP mode (Streamable HTTP)

MCP Client Configuration

Claude Desktop

Claude Code

Cursor / Windsurf / VS Code

Remote / HTTP Clients

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

MCP Protocol Support

Available Tools (46)

Release Management (14)

Chart Management (14)

Repository Management (5)

Registry / OCI (2)

Search (2)

Plugin Management (6)

Environment (2)

Dependency Update (1)

Tool Annotations