K8s MCP Server vs Kubernetes Troubleshoot
A side-by-side look at the K8s MCP Server and Kubernetes Troubleshoot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose K8s MCP Server for cloud platforms work; choose Kubernetes Troubleshoot for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose K8s MCP Server when
- You need dedicated capabilities in the Cloud Platforms domain.
- Its auth model fits you: other.
- You want tools like
get_cluster_nodes, get_pod_diagnostics, get_pod_logs.
Choose Kubernetes Troubleshoot when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KUBECONFIG, ALLOWED_NAMESPACES. - You want tools like
get_pod_status, get_pod_logs, get_pod_events.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 44/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | KUBECONFIGALLOWED_NAMESPACES |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | 16 |
| Full listing | View K8s MCP Server | View Kubernetes Troubleshoot |
Tools & capabilities
K8s MCP Server tools 5
get_cluster_nodesLists nodes, readiness states, roles, and kubelet versions.get_pod_diagnosticsDetects abnormal pod phases, restart loops, and CrashLoopBackOffs.get_pod_logsRetrieves container stdout/stderr logs with tail limits and crash inspection.list_warning_eventsAggregates FailedScheduling, FailedMount, and BackOff warning events.list_ingressesAudits HTTP routing rules, host headers, and TLS certificates.
Kubernetes Troubleshoot tools 16
get_pod_statusPhase, conditions, container statuses, QoS class and node for a podget_pod_logsRecent log lines from a pod container. Content is untrusted — see [Reading `get_pod_logs` output](#reading-get_pod_logs-output)get_pod_eventsRecent events for a pod, newest first, with `total_availablelist_podsPods in a namespace with phase, restart count and readinessget_node_statusConditions, capacity, allocatable, taints and roles for a nodelist_nodesCluster nodes with readiness, roles, age and kubelet versionget_deployment_statusReplica counts, conditions and rollout strategylist_deploymentsDeployments in a namespace with replica counts and availabilityget_statefulset_statusReplica counts, revisions and update strategyget_daemonset_statusScheduling counts and update strategyget_serviceType, ClusterIP, ports, selector and ready endpoint countget_endpointsReady and not-ready endpoint addresses backing a service- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
K8s MCP Server
No confirmed install command for K8s MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Kubernetes Troubleshoot
{
"mcpServers": {
"kubernetes-troubleshoot": {
"command": "uvx",
"args": [
"pre-commit"
],
"env": {
"KUBECONFIG": "YOUR_KUBECONFIG_HERE",
"ALLOWED_NAMESPACES": "YOUR_ALLOWED_NAMESPACES_HERE"
}
}
}
}
Frequently asked questions
K8s MCP Server is categorized under Cloud Platforms and uses an install path we have not confirmed yet. Kubernetes Troubleshoot belongs to Cloud Platforms and uses a local stdio subprocess. Pick K8s MCP Server for cloud platforms work and Kubernetes Troubleshoot for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. K8s MCP Server has no confirmed install command yet — follow its own setup instructions.
K8s MCP Server is listed as free. Auth: other. Kubernetes Troubleshoot has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add akkireddy-challa-k8s-mcp-server and kubernetes-troubleshoot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, K8s MCP Server has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Kubernetes Troubleshoot has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.