No user-submitted related servers found.
Scored across 18 tools
Most tools map to clearly distinct operations, such as kubectl_get, kubectl_logs, kubectl_patch, and kubectl_rollout, so an agent can generally select the correct one. The only notable overlap is kubectl_apply vs kubectl_create, but their descriptions sufficiently differentiate manifest-based apply versus create subcommands.
All names consistently use snake_case, but there is an uneven pattern: most tools start with kubectl_, while others like explain_resource, list_api_resources, install_helm_chart, port_forward, and ping do not follow that prefix convention. The naming is readable, but the mixed style is noticeably inconsistent.
With 18 tools, the server is slightly above the typically well-scoped 3-15 range but still reasonable for the broad Kubernetes domain. Each tool covers a genuinely useful operation, so the count does not feel padded.
The tool surface covers create, apply, patch, scale, rollout, logs, exec, and port-forward, but it has a major gap: there is no delete or uninstall tool. This means an agent cannot remove Kubernetes resources or Helm releases, which is a critical dead end for lifecycle management.