zekker6/mcp-helm

An MCP (Model Context Protocol) server that provides tools for interacting with Helm repositories and charts. This
server enables AI assistants to query Helm repositories, retrieve chart information, and access chart values without
requiring local Helm installation.
The purpose of using MCP for Helm is to avoid making up format of values.yaml and contents of the charts when working
with LLMs.
Instead, the server provides a standardized way to access this information, making it easier for AI assistants to
interact with Helm charts and repositories.
This MCP server is and will be providing tools for working with Helm repositories only. If you need to work with other
Kubernetes resources, consider using a separate MCP server that provides tools for Kubernetes resources.
## Features
The MCP Helm server provides the following tools:
listrepositorycharts - Lists all charts available in a Helm repository (or chart name for OCI registries)
listchartversions - Lists all available versions/tags for a chart
getlatestversionofchart - Retrieves the latest stable (non-prerelease) version of a specific chart
getchartvalues - Retrieves the values file for a chart (latest version or specific version)
getchartcontents - Retrieves the contents of a chart (including templates, values, and metadata), optionally
filtered by file path glob patterns (for example, templates/)
getchartdependencies - Retrieves the dependencies of a chart as defined in its Chart.yaml file
getchartimages - Extracts container images used in a Helm chart by rendering templates and parsing Kubernetes
manifests
### Repository Types
All tools support both traditional HTTP Helm repositories and OCI registries:
| Repository Type | Example URL |
| HTTP Repository | https://charts.example.com |
| OCI Registry | oci://ghcr.io/org/charts/mychart |
| OCI (Docker Hub) | oci://docker.io/library/mysql |
### OCI Registry Support
OCI (Open Container Initiative) registries store Helm charts as OCI artifacts. Unlike HTTP repositories where multiple
charts share an index, OCI registries typically contain one chart per repository with multiple version tags.
Example usage with OCI:
repositoryurl: oci://ghcr.io/nginxinc/charts/nginx-ingress
chartname: (empty - chart name is in the URL)
## Try without installation
There is a publicly available instance of the MCP Helm server that you can use to test the features without installing
it: https://mcp-helm.zekker.dev/mcp
## Installation
### Run with docker
You can run the MCP Helm server using Docker. This is the easiest way to get started without needing to install Go or
build from source.
bash
docker run -d --name mcp-helm -p 8012:8012 ghcr.io/zekker6/mcp-helm:v1.3.0 -mode=sse
Note that the --mode=sse flag is used to enable Server-Sent Events mode, which used by MCP clients to connect.
Alternatively, you can use -mode=http to enable Streamable HTTP mode.
### Via pre-build binary
Download binary from the releases page.
Example for Linux x8664 (note that other architectures and platforms are also available):
bash
latest=$(curl -s https://api.github.com/repos/zekker6/mcp-helm/releases/latest | grep 'tagname' | cut -d\" -f4)
wget https://github.com/zekker6/mcp-helm/releases/download/$latest/mcp-helmLinuxx8664.tar.gz