No user-submitted related servers found.
Scored across 17 tools
Most tools target clearly distinct Kubernetes actions and resources, such as get vs describe, scale vs rollout, and port_forward vs stop_port_forward. The main overlap is kubectl_create vs kubectl_apply, since both can create or update resources from manifests, but their descriptions give enough guidance to distinguish typical use.
The set is readable and mostly uses snake_case action-oriented names, but the kubectl_ prefix is inconsistently applied across otherwise Kubernetes-related tools. For example, kubectl_get and kubectl_apply coexist with explain_resource, install_helm_chart, port_forward, and list_api_resources.
Seventeen tools is reasonable for a Kubernetes management server covering core resource, rollout, Helm, and connectivity workflows. A few tools like ping and kubectl_reconnect are auxiliary, but they support operational reliability rather than bloating the surface excessively.
The server covers create/apply, read, describe, patch, logs, scale, rollout, contexts, Helm install/upgrade, and port forwarding. However, there is no delete tool for Kubernetes resources, which is a notable lifecycle gap, and Helm coverage lacks list/uninstall operations.