The stated reason this exists is that models invent chart values and template contents; reading them from the registry removes the guessing. Image extraction is the tool that is hardest to replace — it renders the templates and parses the manifests, so you get the images a release will actually pull rather than the ones the values file implies.
A Helm repository client. It lists the charts in a repository, their versions, the latest one, a chart's values file and full contents, the dependencies it declares, and the container images its templates render to.
- The charts in a repository, or the chart named in an OCI registry URL
- Every version or tag available for a chart, and the latest one on its own
- A chart's values file, at the latest version or at one you name
- A chart's full contents — templates, values and metadata
- The dependencies a chart declares
- The container images a chart pulls, extracted by rendering its templates and parsing the resulting manifests
- The same tools against both traditional HTTP repositories and OCI registries
- Private repositories reached with basic credentials, and private registries with a Docker-style credentials file, routed per registry host
The compiled binary, the published container image, or a Go install — no local Helm needed. Private HTTP repositories take a username and a password file; private OCI registries take a Docker-style credentials file. A public instance exists if you only want to try it first.
One command — go install github.com/zekker6/mcp-helm/cmd/mcp-helm@latest