Kubernetes Troubleshoot
Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.Similar tools
Listed for the same task: automate CI/CD pipelinesReviews
No review yet. Used Kubernetes Troubleshoot? Be the first to help others choose.What it does
Kubernetes Troubleshoot is an MCP server, a connector that lets an AI assistant use it as a tool. It is installed locally as a package and runs on your machine.
From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · not tested by Electra IndexInstall package
- DOCKER
docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0· runs locally (stdio)
Required: KUBECONFIG, ALLOWED_NAMESPACES (get them from the publisher)
No ready-made settings: the registry entry does not contain everything needed. Follow the publisher's instructions.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Package registries | oci | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://github.com/NanaGyamfiPrempeh30/k8s-troubleshoot-mcp#readme | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/NanaGyamfiPrempeh30/k8s-troubleshoot-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Kubernetes Troubleshoot still online?
Free alerts · no account▲ 0Do you publish Kubernetes Troubleshoot? Get it seen by people choosing a tool
For publishers · optionalLaunch Spotlight: 60 days of clearly labelled Sponsored visibility on the use-case pages where Kubernetes Troubleshoot already appears, plus the weekly Pulse. No click in 60 days? The next 60 days are free.
Sponsored placements never change a score or a rank.
Questions about Kubernetes Troubleshoot
How do I connect Kubernetes Troubleshoot?
Install the Docker package docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does Kubernetes Troubleshoot need an API key or token?
Yes. The registry entry lists required values: KUBECONFIG, ALLOWED_NAMESPACES. Get them from the publisher.
What can I use Kubernetes Troubleshoot for?
Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.