kubernetes -helmchart

This MCP server Helm chart deploys a Kubernetes MCP Server into your cluster. The server exposes an MCP API endpoint over HTTP (default port 8080) and can be configured to manage Kubernetes resources via the MCP protocol. By enabling the optional write permissions (enableWriteDelete) you can grant Create, Patch, Update, and Delete capabilities to the MCP server, allowing it to apply changes to resources in your cluster. The Helm chart is designed to be customized via standard Helm values (such as image, serviceAccount, port settings, and labels) to fit your deployment needs. Once deployed, you can interact with the MCP API to fetch, apply, or stream resource configurations just as you would with other MCP-compatible clients.

Prerequisites:

• Kubernetes cluster (version 1.24 or newer)
• Helm v3.9 or newer
• kubectl configured to access your cluster

Installation steps:

1. Clone the Helm chart repository: git clone git@github.com:frenoid/kubernetes-mcp-server-helmchart.git
2. Navigate to the chart directory: cd kubernetes-mcp-server
3. (Optional) Customize values using a values.yaml file or via --set overrides. A typical values.yaml exists in the chart and controls image, ports, RBAC, and various MCP server options.
4. Install the chart into the cluster (replace myrelease with your release name): helm install myrelease . -f values.yaml
5. Verify the deployment and get the service details: kubectl get pods kubectl get svc
6. To uninstall later: helm uninstall myrelease

Notes:

• The chart exposes an HTTP MCP server on port 8080 by default (containerPort http).
• You can enable write/delete permissions with the enableWriteDelete flag to allow full MCP CRUD operations.
• Ensure your cluster's networking and RBAC policies permit the MCP server to manage the resources you intend to control.

Tips and common considerations:

• The image used is docker.io/frenoid/kubernetes-mcp-server with tag v0.0.53 by default; you can override this in values.yaml to pin a specific version.
• Service type is ClusterIP by default; change service.type to LoadBalancer or NodePort if you need external access.
• Review securityContext and serviceAccount settings in values.yaml to align with your cluster's security requirements.
• If you need to grant Create, Patch, Update, and Delete permissions to the MCP server, enable enableWriteDelete in the values.
• If you encounter port conflicts, adjust the containerPorts.http and corresponding service port in values.yaml.
• The Helm chart supports additional deployment resources via extraDeploy if you need to deploy auxiliary objects alongside the MCP server.