helm-mcp (Python)
A Python MCP wrapper for the helm-mcp Go server.
Uses FastMCP to create a transparent proxy around the helm-mcp Go binary, exposing all Helm tools via the Model Context Protocol. New tools added to the Go binary are automatically available without any Python code changes.
Removed in 0.2.0:
--transport sse. The MCP specification deprecates the HTTP+SSE transport and the Go server no longer serves it. Use--transport http.
Requirements
- Python 3.12+
- The
helm-mcpGo binary is automatically downloaded on first use (with SHA256 checksum verification)
Installation
pip install helm-mcp
Quick Start
As a server
from helm_mcp import create_server
server = create_server()
server.run() # stdio mode (default)
As a client
import asyncio
from helm_mcp import create_client
async def main():
async with create_client() as client:
tools = await client.list_tools()
print(f"Available tools: {len(tools)}")
result = await client.call_tool("helm_list", {"namespace": "default"})
print(result)
asyncio.run(main())
CLI
# stdio mode (default, for MCP clients like Claude Code)
helm-mcp-python
# HTTP mode (Streamable HTTP)
helm-mcp-python --transport http --host 0.0.0.0 --port 8080
# Pre-download binary
helm-mcp-python --setup
# Explicit binary path
helm-mcp-python --binary /usr/local/bin/helm-mcp
Binary Discovery
Both the helm-mcp and helm-mcp-python commands locate the Go binary the
same way, via helm_mcp.discovery:
HELM_MCP_BINARYenvironment variable- Bundled binary in the package
bin/directory (platform wheels) helm-mcponPATH— pip console-script wrappers are skipped, so ago installor Homebrew build wins over a network fetch- Auto-download from GitHub Releases (with SHA256 checksum verification)
Environment Variables
The proxy forwards these environment variables to the Go binary:
| Category | Variables |
|---|---|
| Proxy | HTTP_PROXY, HTTPS_PROXY, NO_PROXY (and lowercase variants) |
| Kubernetes | KUBECONFIG, KUBERNETES_SERVICE_HOST, KUBERNETES_SERVICE_PORT |
| Helm | HELM_CACHE_HOME, HELM_CONFIG_HOME, HELM_DATA_HOME, HELM_DRIVER, HELM_PLUGINS, HELM_DEBUG, HELM_REGISTRY_CONFIG, HELM_REPOSITORY_CACHE, HELM_REPOSITORY_CONFIG |
| AWS | AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_REGION, AWS_DEFAULT_REGION, AWS_PROFILE, AWS_SHARED_CREDENTIALS_FILE, AWS_CONFIG_FILE |
| GCP | GOOGLE_APPLICATION_CREDENTIALS, CLOUDSDK_COMPUTE_ZONE, CLOUDSDK_COMPUTE_REGION, CLOUDSDK_CORE_PROJECT |
| Azure | AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_SUBSCRIPTION_ID, AZURE_AUTHORITY_HOST |
| TLS | SSL_CERT_FILE, SSL_CERT_DIR, REQUESTS_CA_BUNDLE |
The full list is helm_mcp.server.PASSTHROUGH_ENV_VARS.
Resilience
HelmClient and the proxy server wrap every call in a configurable resilience
stack — timeouts, retries with exponential backoff and jitter, a circuit
breaker, a concurrency bulkhead, optional rate limiting and response caching,
and optional OpenTelemetry tracing. Everything is configurable in code via
ResilienceConfig, or from the environment:
| Variable | Default | Effect |
|---|---|---|
HELM_MCP_TIMEOUT |
300 |
Per-call timeout in seconds |
HELM_MCP_RETRY_ENABLED |
true |
Retry transient connection failures |
HELM_MCP_RETRY_MAX_ATTEMPTS |
3 |
Attempts before giving up |
HELM_MCP_CIRCUIT_BREAKER_ENABLED |
true |
Trip after repeated connection failures |
HELM_MCP_BULKHEAD_MAX_CONCURRENT |
10 |
Concurrent in-flight tool calls |
HELM_MCP_RATE_LIMIT_ENABLED |
false |
Client-side rate limiting |
HELM_MCP_CACHE_ENABLED |
false |
Cache responses |
HELM_MCP_OTEL_ENABLED |
false |
Export traces (needs the otel extra) |
The corresponding CLI flags are --no-retry, --no-circuit-breaker,
--rate-limit, --cache, --bulkhead-max and --otel.
Scalability
This package uses the MCP proxy pattern: the Python layer never needs to know about individual Helm tools. All tool discovery, input schemas, and invocations are forwarded to the Go binary via the MCP protocol at runtime. When new capabilities are added to the Go server, they are immediately available through the Python wrapper.
License
MIT
1 maintainer
Release files for helm-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| helm_mcp-0.2.0.tar.gz | 38.5 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| helm_mcp-0.2.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| helm_mcp-0.2.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| helm_mcp-0.2.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| helm_mcp-0.2.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| helm_mcp-0.2.0-py3-none-macosx_10_15_x86_64.whl | Python 3 | none | macOS 10.15+ x86-64 | Details |
Total release size: 105.6 MB
Release files / helm_mcp-0.2.0.tar.gz
| Download URL | helm_mcp-0.2.0.tar.gz |
|---|---|
| Size | 38.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5123975400a287cc7d80636c13291cb16f4753bc7b230462ca47a52a0a818bc
|
|
BLAKE2b-256 checksum How to use checksums |
03fd97150d283328ef7a9d47cd33d69cab19dd532791d32dec69fb599b1fc4f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / helm_mcp-0.2.0-py3-none-win_amd64.whl
| Download URL | helm_mcp-0.2.0-py3-none-win_amd64.whl |
|---|---|
| Size | 20.9 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a4b997b90649e48e7c1f9e9bb2c33d089ec1b321f2fb32fc543afb51a4252c3f
|
|
BLAKE2b-256 checksum How to use checksums |
f79d571dc753bddac47fb8bb437aa1d716af6a5c9c281479e2b48cacf0ada4cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / helm_mcp-0.2.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | helm_mcp-0.2.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 26.9 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
cdee1f4859f2405ab1808da286a060bb698b62fd05aab8f8c7fbefab04e1af9a
|
|
BLAKE2b-256 checksum How to use checksums |
d38ba388c6acdd64d90a9e1f25b11dce2ecd6470ef0b7c91badf932b87c7b848
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / helm_mcp-0.2.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | helm_mcp-0.2.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 18.0 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
c81f393ca3fae64e9938d989a43881d26345e2dce4693ceb653da8d5e15fdd98
|
|
BLAKE2b-256 checksum How to use checksums |
260d50d1ce46c91d213eaba7205961fdebd07363381b4e6e081419cb8234c620
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / helm_mcp-0.2.0-py3-none-macosx_11_0_arm64.whl
| Download URL | helm_mcp-0.2.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 18.9 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d0be540891f9b982b69bcee98db099e9960cd4af65783d58a63cce5fb6fd7a9a
|
|
BLAKE2b-256 checksum How to use checksums |
58c6d9106c71996950fced8cee9677b8103428a790c1ff3a287682223aeeb963
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / helm_mcp-0.2.0-py3-none-macosx_10_15_x86_64.whl
| Download URL | helm_mcp-0.2.0-py3-none-macosx_10_15_x86_64.whl |
|---|---|
| Size | 20.8 MB |
| Tags | Python 3 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
08f8aea97681863cefcb28b440dabc8cca58ada03cfc923ad0c4ee66165c2b0e
|
|
BLAKE2b-256 checksum How to use checksums |
0ae152117596b3c31be60dcf49cbbb9b0d134a21a27f57121c4528736ab5b357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency log
