Kubently vs Kubernetes Troubleshoot
A side-by-side look at the Kubently 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 Kubently for cloud platforms work over a hosted endpoint; 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 Kubently when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
LLM_PROVIDER, ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY.
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 | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LLM_PROVIDERANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEY | KUBECONFIGALLOWED_NAMESPACES |
| Verified owner | Community listing | Community listing |
| GitHub stars | 46 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View Kubently | View Kubernetes Troubleshoot |
Tools & capabilities
Kubently tools
No tool names declared yet. Check the project README from the listing page.
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.
Kubently
{
"mcpServers": {
"kubently": {
"url": "http://localhost:8080/mcp/"
}
}
}
Kubernetes Troubleshoot
{
"mcpServers": {
"kubernetes-troubleshoot": {
"command": "uvx",
"args": [
"pre-commit"
],
"env": {
"KUBECONFIG": "YOUR_KUBECONFIG_HERE",
"ALLOWED_NAMESPACES": "YOUR_ALLOWED_NAMESPACES_HERE"
}
}
}
}
Frequently asked questions
Kubently is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Kubernetes Troubleshoot belongs to Cloud Platforms and uses a local stdio subprocess. Pick Kubently 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.
Kubently has no declared pricing — check the project's own site. 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 kubently and kubernetes-troubleshoot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kubently has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 46 GitHub stars. Kubernetes Troubleshoot has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.