Helm MCP

io.github.Kubedoll-Heavy-IndustriesPublished by GitHub account Kubedoll-Heavy-Industriesv0.1.4Updated Oct 24, 2026

Give your AI assistant access to real Helm chart data. No more hallucinated values.yaml files.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A remote MCP server that gives an AI assistant real Helm chart data — chart search, versions, values.yaml, dependencies and notes — instead of guessed values.

What you can do
Search and list charts in a Helm repository by keyword, with a result limit, and fetch a chart's available versions newest first, optionally just the latest one. Retrieve a chart's values.yaml, either whole or as a focused subsection by path and depth, with optional schema and examples. Look up a chart's sub-charts and their repository URLs, and read a chart's NOTES.txt post-install instructions.
When to use it
Useful when an assistant helps write or review Kubernetes deployments and Helm values, and you want it to work from actual chart schemas and versions rather than plausible-looking guesses or stale versions.
Requirements
A remote endpoint at helm-mcp.kubedoll.com over streamable HTTP; the README's public instance is rate limited and needs no install. Alternatively, self-host via the Docker image or a binary and connect over stdio or HTTP. Network access to Helm repositories is needed for chart data.
Before you install
The public instance is rate limited and third-party hosted, so chart queries pass through that service; self-host if that matters. OCI registries cannot be browsed, so a chart name must already be known. The tools are read-only lookups of chart data.

Installation

In SourceWeft

  1. Open Helm MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Kubedoll-Heavy-Industries%2Fhelm-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "helm": {
      "type": "http",
      "url": "https://helm-mcp.kubedoll.com/mcp"
    }
  }
}

README

mcp-helm

[CI] [codecov] [Go Report Card] [Release] [License: MIT]

Give your AI assistant access to real Helm chart data. No more hallucinated values.yaml files.

What is this?

When you ask Claude, Cursor, or other AI assistants to help with Kubernetes deployments, they don't have access to Helm chart schemas. So they guess — and the guesses look plausible but don't match reality.

Without mcp-helm:

  • :x: Hallucinates field names that look right but don't exist
  • :x: Suggests stale or deprecated chart versions
  • :x: Wastes tokens on web fetches and guesswork

With mcp-helm:

  • :white_check_mark: Queries actual Helm repositories for real chart data
  • :white_check_mark: Gets the latest chart version automatically
  • :white_check_mark: Correct configurations the first time

mcp-helm implements the Model Context Protocol (MCP) — a standard way for AI assistants to access external data sources.

Try It Now

Add this to your editor's MCP config to use our public instance (rate limited, no install required):

json
{  "mcpServers": {    "helm": {      "type": "http",      "url": "https://helm-mcp.kubedoll.com/mcp"    }  }}

Then ask your AI: "What values can I configure for the bitnami/postgresql chart?"

Editor Setup

Claude Code

Edit ~/.claude/mcp.json:

json
{  "mcpServers": {    "helm": {      "command": "docker",      "args": ["run", "--rm", "-i", "ghcr.io/kubedoll-heavy-industries/mcp-helm", "--transport=stdio"]    }  }}
Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "helm": {      "command": "docker",      "args": ["run", "--rm", "-i", "ghcr.io/kubedoll-heavy-industries/mcp-helm", "--transport=stdio"]    }  }}
Cursor

Edit MCP settings in Cursor's configuration:

json
{  "mcpServers": {    "helm": {      "command": "docker",      "args": ["run", "--rm", "-i", "ghcr.io/kubedoll-heavy-industries/mcp-helm", "--transport=stdio"]    }  }}
VS Code + Continue

Add to your Continue config (~/.continue/config.json):

json
{  "experimental": {    "modelContextProtocolServers": [      {        "transport": {          "type": "stdio",          "command": "docker",          "args": ["run", "--rm", "-i", "ghcr.io/kubedoll-heavy-industries/mcp-helm", "--transport=stdio"]        }      }    ]  }}
Without Docker

If you prefer to run the binary directly, install mcp-helm and replace the Docker config with:

json
{  "mcpServers": {    "helm": {      "command": "mcp-helm"    }  }}

Available Tools

ToolWhat it doesUseful parameters
search_chartsList or search charts in a Helm repokeyword (substring filter), limit
get_versionsGet available versions of a chart (newest first)limit=1 for the latest only
get_valuesGet chart values.yaml, optionally as a focused subsectionpath (e.g. .ingress), depth (default 2, 0 for full YAML), include_schema=true, include_examples=true (requires path)
get_dependenciesGet a chart's sub-charts (with their repo URLs, which can be fed back into the other tools)—
get_notesGet chart NOTES.txt (post-install instructions)—

OCI registries (oci://...) do not support browsing — for OCI you must already know the chart name, then call get_versions or get_values directly with that name.

Install

Docker (recommended — no install required, used in Editor Setup above):

bash
docker pull ghcr.io/kubedoll-heavy-industries/mcp-helm:latest

Binary:

bash
curl -fsSL https://github.com/kubedoll-heavy-industries/helm-mcp/releases/latest/download/mcp-helm_$(uname -s)_$(uname -m).tar.gz | tar xzsudo mv mcp-helm /usr/local/bin/

Go:

bash
go install github.com/kubedoll-heavy-industries/helm-mcp/cmd/mcp-helm@latest

Self-Hosting

For shared deployments or when you need an HTTP endpoint:

bash
docker run -p 8012:8012 ghcr.io/kubedoll-heavy-industries/mcp-helm:latest \  --transport=http --listen=:8012# Connect to http://localhost:8012/mcp

See docs/self-hosting.md for health endpoints and production recommendations.

Documentation

License

MIT — see LICENSE.

Source: README.md at commit ce996af

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts