MCP Server Kubernetes connects to a Kubernetes cluster and provides a unified MCP-based interface to manage cluster resources. It supports loading kubeconfig from multiple sources in priority order, enabling connections to contexts across environments. The server exposes a single, unified kubectl API for common operations such as Get/List/Describe, Create/Apply/Delete, Get Logs, Context management, Explain, List API resources, Scale, Patch, and Rollout, plus a generic kubectl command path (kubectl_generic) and a health check (ping). Beyond basic resource management, the server offers advanced capabilities: scaling deployments, port forwarding to pods or services, and Helm operations (install, upgrade, uninstall) with support for custom values, repositories, and versions; includes template-based installation (helm_template_apply) and uninstall (helm_template_uninstall) to bypass authentication issues. It also provides pod cleanup (cleanup_pods) for pods in problematic states and node management (cordon, drain, uncordon) for maintenance and scaling. A non-destructive mode can be enabled to disable destructive actions, with explicit command controls and an environment variable to enforce it. It includes security features like secrets masking and a dedicated troubleshooting prompt (k8s-diagnose) to guide autonomous Kubernetes diagnostics.