MCP Helm MCP Server

An MCP (Model Context Protocol) server that provides tools for interacting with Helm repositories and charts. This server enables AI assistants to

Local serverstdioGo

What is the MCP Helm MCP server?

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. That is what the mcp helm mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

  • list_repository_charts — - Lists all charts available in a Helm repository (or chart name for OCI registries)
  • list_chart_versions — - Lists all available versions/tags for a chart
  • get_latest_version_of_chart — - Retrieves the latest version of a specific chart
  • get_chart_values — - Retrieves the values file for a chart (latest version or specific version)
  • get_chart_contents — - Retrieves the contents of a chart (including templates, values, and metadata)
  • get_chart_dependencies — - Retrieves the dependencies of a chart as defined in its Chart.yaml file

The tools it exposes

The server publishes 9 tools. What each one is for:

  • list_repository_charts — Lists all charts available in a Helm repository (or chart name for OCI registries)
  • list_chart_versions — Lists all available versions/tags for a chart
  • get_latest_version_of_chart — Retrieves the latest version of a specific chart
  • get_chart_values — Retrieves the values file for a chart (latest version or specific version)
  • get_chart_contents — Retrieves the contents of a chart (including templates, values, and metadata)
  • get_chart_dependencies — Retrieves the dependencies of a chart as defined in its Chart.yaml file
  • get_chart_images — Extracts container images used in a Helm chart by rendering templates and parsing Kubernetes
  • Flag — Description
  • Authentication — The server supports authentication for both OCI registries and HTTP Helm repositories

Getting it running

The server ships on a container image as ghcr.io/zekker6/mcp-helm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: GITHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Helm's toolset — list_repository_charts, list_chart_versions, get_latest_version_of_chart and 6 more — is a fair guide to whether it matches your workflow. It is maintained by zekker6; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Helm's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Helm.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
list_repository_chartsLists all charts available in a Helm repository (or chart name for OCI registries)
list_chart_versionsLists all available versions/tags for a chart
get_latest_version_of_chartRetrieves the latest version of a specific chart
get_chart_valuesRetrieves the values file for a chart (latest version or specific version)
get_chart_contentsRetrieves the contents of a chart (including templates, values, and metadata)
get_chart_dependenciesRetrieves the dependencies of a chart as defined in its Chart.yaml file
get_chart_imagesExtracts container images used in a Helm chart by rendering templates and parsing Kubernetes
FlagDescription
AuthenticationThe server supports authentication for both OCI registries and HTTP Helm repositories.

How to install the MCP Helm MCP server

{
  "mcpServers": {
    "helm": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/zekker6/mcp-helm"],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Helm to list repository charts.
  • Use MCP Helm to list chart versions.
  • Use MCP Helm to get latest version of chart.

Frequently asked questions

It connects MCP Helm to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (list_repository_charts, list_chart_versions, get_latest_version_of_chart, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Helm directly.