Developer · Local MCP server
Helm MCP
The full Helm CLI surface as 46 MCP tools, backed by the Helm v3 and v4 Go SDKs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.SCGIS-Wales/helm-mcp- Version
- 0.4.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- SCGIS-Wales (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/SCGIS-Wales) · how
- Website
- github.com/SCGIS-Wales/helm-mcp
- Repository
- github.com/SCGIS-Wales/helm-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | helm-mcp | 0.4.2 | stdio |
| OCI image (Docker) | ghcr.io/scgis-wales/helm-mcp:0.4.2 | - | stdio |
How to connect Helm MCP
Helm MCP runs locally from a Python package published to PyPI: helm-mcp version 0.4.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx helm-mcp. It reads these environment variables: KUBECONFIG and HELM_MCP_BINARY; set them in the client's configuration for this server.
Helm MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/scgis-wales/helm-mcp:0.4.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/scgis-wales/helm-mcp:0.4.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"helm-mcp": {
"command": "uvx",
"args": [
"helm-mcp"
],
"env": {
"KUBECONFIG": "<value>",
"HELM_MCP_BINARY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| HeirmosPersistent memory shared across Claude, ChatGPT, Grok and other MCP clients. | Remote · HTTPLive check: sign-in required |
| Helena Good: Scientific Infrastructure SponsorshipFund or spread Helena's public scientific infrastructure to keep it free to use and independent. | Remote · HTTPLive check: ✓ handshake |
| HeliographRun commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled. | Local · stdio |
| Helixar SecuritySecurity tools for AI agents: scan MCP servers, validate HDP delegation chains, audit releases. | Remote · HTTPLive check: ✓ handshake |
| HelmdeckSelf-hosted MCP server: sandboxed browser, desktop, vision, code-edit packs for any agent. | Local · stdio |
| Hemrock MCPHemrock financial modeling prompts: context primers, task prompts, checks, and best practices. | Remote · HTTPLive check: ✓ handshake |
| hepcloud.netManage HepCloud (Turkish cloud) servers and managed PostgreSQL from your AI assistant. OAuth 2.1. | Remote · HTTPLive check: sign-in required |
| Hera FertilityFind male fertility testing at labs near a US ZIP code, with prices and a link to order. | Remote · HTTPLive check: ✓ handshake |