v1.15.0 - Multi-Cluster Support

Multi-Cluster Support with Context Parameter

This release adds comprehensive multi-cluster support by introducing an optional context parameter to all cluster-interacting tools. Target any Kubernetes cluster without switching contexts!

New Features

• Context Parameter for All Tools: All 131 tools now accept an optional context parameter to target specific clusters
• Cross-Cluster Operations: Run commands against any cluster in your kubeconfig without switching contexts
• Response Enrichment: Every response now includes "context": "production" or "context": "current" for clarity

Usage Examples

# Target a specific cluster context
kubectl-mcp-server call get_pods '{"namespace": "default", "context": "production"}'

# Get deployments from staging
kubectl-mcp-server call get_deployments '{"namespace": "app", "context": "staging"}'

# Install Helm chart to production cluster
kubectl-mcp-server call install_helm_chart '{"name": "redis", "chart": "bitnami/redis", "namespace": "cache", "context": "production"}'

Natural language with AI assistants:

• "List pods in the production cluster"
• "Get deployments from staging context"
• "Show logs from the api-pod in the dev cluster"

Technical Details

• Enhanced k8s_config.py with context-aware client creation (get_k8s_client(context), get_apps_client(context))
• Helper functions: _get_kubectl_context_args(context), _get_helm_context_args(context)
• If context is omitted, tools use the current kubectl context (backward compatible)

Stats

• 131 Core Tools (up from 127)
• 216 Tests Passing
• 26 Browser Tools (optional)
• 6 UI Tools (optional)

Installation

# npm (recommended)
npx kubectl-mcp-server@1.15.0

# pip
pip install kubectl-mcp-server==1.15.0

# Docker
docker pull rohitghumare64/kubectl-mcp-server:1.15.0

Full Changelog: v1.14.0...v1.15.0