mcp-kubernetes
Related Servers
Alternatives to mcp-kubernetes
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables inspecting and managing Kubernetes clusters through MCP, including listing deployments and pods, retrieving logs and events, and scaling or restarting deployments.-
- FlicenseNot gradedqualityDmaintenanceEnables Kubernetes cluster introspection via MCP tools, such as listing pods, namespaces, nodes, and events.4-
- AlicenseNot gradedqualityBmaintenanceSafe, read-only-by-default Kubernetes access for AI agents via MCP. Provides explicit readonly, readwrite, and dangerous permission modes, plus MCPB bundles for desktop clients.2MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for generating Kubernetes manifests (deployments, services, configmaps, secrets, ingresses, namespaces) and performing kubectl operations like apply, delete, get, describe, logs, and exec.MIT
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade MCP server for Kubernetes operations, supporting local kubeconfig and AWS EKS authentication, with read, write, and destructive operations protected by multi-layer safety guards.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with multiple Kubernetes clusters simultaneously, providing comprehensive tools for cluster management, resource operations, and diagnostics across different environments.-
TDQS
Scored across 10 tools
Each tool targets a distinct resource or action: list contexts, namespaces, pods, deployments, services, nodes, events, and specific getters for pod details, logs, and arbitrary resources. No two tools have overlapping purposes; get_resource is clearly defined as a generic read that complements the specific ones.
All tools follow a consistent verb_resource pattern: list_* for enumerations and get_* for single-object retrieval. Names use lowercase snake_case consistently, with clear pluralization for list operations and singular for get operations, including a mixed get_pod_logs that still fits the pattern.
Ten tools is well-scoped for a Kubernetes read-only server, covering core resource types (pods, deployments, services, nodes, events) plus generic access. Each tool has a clear purpose and the count is neither overwhelming nor too thin.
The server provides comprehensive read coverage for common Kubernetes resources, including list/get operations, logs, events, and arbitrary object retrieval via get_resource. It lacks write operations (create/update/delete), but this appears intentional for a diagnostic-focused tool, leaving only minor gaps like lack of pod exec or resource watches.