Skip to main content

helm-mcp (Python)

CI/CD Pipeline PyPI version Python versions Downloads License: MIT

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-mcp Go 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). Loopback only by default: the proxy has no
# authentication, so binding elsewhere needs --allow-remote
helm-mcp-python --transport http --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:

  1. HELM_MCP_BINARY environment variable
  2. Bundled binary in the package bin/ directory (platform wheels)
  3. helm-mcp on PATH — pip console-script wrappers are skipped, so a go install or Homebrew build wins over a network fetch
  4. 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

Release files for helm-mcp 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for helm-mcp 0.4.0
File Size Uploaded
helm_mcp-0.4.0.tar.gz 41.8 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for helm-mcp 0.4.0
File
helm_mcp-0.4.0-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details
helm_mcp-0.4.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.4.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl Python 3 none Linux glibc 2.17+ ARM64 Details
helm_mcp-0.4.0-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details
helm_mcp-0.4.0-py3-none-macosx_10_15_x86_64.whl Python 3 none macOS 10.15+ x86-64 Details

Total release size: 109.2 MB

Release files / helm_mcp-0.4.0.tar.gz

Download URL helm_mcp-0.4.0.tar.gz
Size 41.8 kB
Tags Source
SHA-256 checksum
How to use checksums
8d3aa33dcc2c07b8a4b08025f9b13ebcbd376780f703a431167ee60e1685cbb0
BLAKE2b-256 checksum
How to use checksums
8dcb68334532ffafed14d63741a3a1310f857405f3f21bcbc76e08ead3058bfc
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 Sep 25, 2026.

Transparency log

Release files / helm_mcp-0.4.0-py3-none-win_amd64.whl

Download URL helm_mcp-0.4.0-py3-none-win_amd64.whl
Size 21.7 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
0432f7abe9dfb3eac671b0cf9eda7dc2d1f19c4009ee6f3a1553b6a3f3c2e6a0
BLAKE2b-256 checksum
How to use checksums
cf9a78b4b0e03bc80609dfb9cea954180aa9b4908fc1101405d0945915a0ec92
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 Sep 25, 2026.

Transparency log

Release files / helm_mcp-0.4.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL helm_mcp-0.4.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 27.8 MB
Tags Linux glibc 2.17+ x86-64 Python 3
SHA-256 checksum
How to use checksums
56fdc959df973090c4685be6d540a96bd7844ceef1969bab3801ae8d4e6f27d0
BLAKE2b-256 checksum
How to use checksums
56b879e6fbf9edf1200d880104b4250e8aed179589f3689756f3855b2d53503f
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 Sep 25, 2026.

Transparency log

Release files / helm_mcp-0.4.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL helm_mcp-0.4.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 18.6 MB
Tags Linux glibc 2.17+ ARM64 Python 3
SHA-256 checksum
How to use checksums
42d91ef4487e215046aac9b00a3748d27040ec48df500a1b8f5b5426e88b02b6
BLAKE2b-256 checksum
How to use checksums
d88dc08e1871e571ebe908570720ead00bdfb4563952ff8c0a387db7e4daefa9
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 Sep 25, 2026.

Transparency log

Release files / helm_mcp-0.4.0-py3-none-macosx_11_0_arm64.whl

Download URL helm_mcp-0.4.0-py3-none-macosx_11_0_arm64.whl
Size 19.5 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
9117c68543b1eb3bc983b0a1c154054775ffa41a913ef2e336a7598476b98b75
BLAKE2b-256 checksum
How to use checksums
cd6afa9d1eaa717da1f8c6d28cfcf5e7bd159f564e3c8b22d0ea36f428107cf7
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 Sep 25, 2026.

Transparency log

Release files / helm_mcp-0.4.0-py3-none-macosx_10_15_x86_64.whl

Download URL helm_mcp-0.4.0-py3-none-macosx_10_15_x86_64.whl
Size 21.6 MB
Tags Python 3 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
cd08a1963b065fd2bc3c83c6e0c8ffdf314d519fab587066d3c59b9389388858
BLAKE2b-256 checksum
How to use checksums
5137885b2b93e562f02d5c9041472040542561b0a91e8d30b056dfdfac57bfdc
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 Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.2

6 release files

0.4.1

6 release files

This release

0.4.0 This release

6 release files

0.3.0

6 release files

0.2.1

6 release files

0.2.0

6 release files

0.1.35

6 release files

0.1.34

6 release files

0.1.33

6 release files

0.1.29

6 release files

0.1.28

6 release files

0.1.27

6 release files

0.1.26

6 release files

0.1.25

7 release files

0.1.24

7 release files

0.1.23

7 release files

0.1.22

7 release files

0.1.21

7 release files

0.1.20

7 release files

0.1.19

7 release files

0.1.18

7 release files

0.1.17

7 release files

0.1.16

7 release files

0.1.15

7 release files

0.1.14

7 release files

0.1.13

7 release files

0.1.12

7 release files

0.1.11

7 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page