Kubernetes MCP Server vs Kubernetes Troublesho… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Kubernetes MCP Server vs Kubernetes Troubleshoot
In-depth architectural comparison of the Kubernetes MCP Server and Kubernetes Troubleshoot MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Kubernetes MCP Server
Cloud Platforms · Local stdio
Quality: 61/100 (Good) | Auth: other
Kubernetes Troubleshoot
Cloud Platforms · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Kubernetes MCP Server if you need specialized Cloud Platforms tools running via a local process. Choose Kubernetes Troubleshoot if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Kubernetes MCP Server when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Kubernetes MCP Server is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Kubernetes Troubleshoot belongs to Cloud Platforms using local stdio subprocess. Select Kubernetes MCP Server when you need capabilities focused on cloud platforms and Kubernetes Troubleshoot when you require tools for cloud platforms.
List all the OpenShift projects in the current cluster
nodes_log
Get logs from a Kubernetes node (kubelet, kube-proxy, or other system logs). This accesses node logs through the Kubernetes API proxy to the kubelet
nodes_stats_summary
Get detailed resource usage statistics from a Kubernetes node via the kubelet's Summary API. Provides comprehensive metrics including CPU, memory, filesystem, and network usage at the node, pod, and container levels. On systems with cgroup v2 and kernel 4.20+, also includes PSI (Pressure Stall Info…
nodes_top
List the resource consumption (CPU and memory) as recorded by the Kubernetes Metrics Server for the specified Kubernetes Nodes or all nodes in the cluster
pods_list
List all the Kubernetes pods in the current cluster from all namespaces
pods_list_in_namespace
List all the Kubernetes pods in the specified namespace in the current cluster
pods_get
Get a Kubernetes Pod in the current or provided namespace with the provided name
+41 more tools listed on main page
Kubernetes Troubleshoot Tools (16)
get_pod_status
Phase, conditions, container statuses, QoS class and node for a pod
get_pod_logs
Recent log lines from a pod container. Content is untrusted — see [Reading `get_pod_logs` output](#reading-get_pod_logs-output)
get_pod_events
Recent events for a pod, newest first, with `total_available
list_pods
Pods in a namespace with phase, restart count and readiness
get_node_status
Conditions, capacity, allocatable, taints and roles for a node
list_nodes
Cluster nodes with readiness, roles, age and kubelet version
get_deployment_status
Replica counts, conditions and rollout strategy
list_deployments
Deployments in a namespace with replica counts and availability
get_statefulset_status
Replica counts, revisions and update strategy
get_daemonset_status
Scheduling counts and update strategy
get_service
Type, ClusterIP, ports, selector and ready endpoint count
get_endpoints
Ready and not-ready endpoint addresses backing a service