list_repository_chartsLABSCO SUMMARY
The values file it gives you is the one that exists.
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.
What it is
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.
What you get
- 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
Requirements
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. To try it before installing, point a client at the public instance, https://mcp-helm.zekker.dev/mcp.
Setup effort
One command — go install github.com/zekker6/mcp-helm/cmd/mcp-helm@latest
USE CASES
01
Writing values for a chart you have not used before
Read the real values file at the version you intend to deploy, instead of working from a remembered example.
02
Finding out what a chart actually deploys
Read the templates and metadata, and the dependencies it will drag in with it.
03
Pre-pulling or mirroring images before a rollout
Extract the images from the rendered manifests, which is the list that matters for an air-gapped or throttled environment.
04
Pinning a version deliberately
List what versions exist and compare them against what the repository currently calls latest.
05
Seeing what a repository offers
List the charts in an HTTP repository, or read the chart named in an OCI registry URL.
7 tools
Listed in project docs. Your client may show a different list.
list_chart_versionsget_latest_version_of_chartget_chart_valuesget_chart_contentsget_chart_dependenciesget_chart_imagesBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
go on PATH
INSTALLATION
Connect your client
This project publishes no client configuration, so the entry for your client is yours to write.
Server setup
go install
TERMINAL
go install github.com/zekker6/mcp-helm/cmd/mcp-helm@latestHosted endpoint
ENDPOINT URL
https://mcp-helm.zekker.dev/mcpAdd this hosted endpoint to your MCP client.
