Kubernetes Troubleshoot
Rank #86,239io.github.NanaGyamfiPrempeh30/k8s-troubleshoot-mcp
Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes.
What you can do with Kubernetes Troubleshoot
Kubernetes Troubleshoot is a Model Context Protocol (MCP) server published by NanaGyamfiPrempeh30. It ranks #86,239 of 168,415 active servers on MCP Toplist. Kubernetes Troubleshoot is listed across 2 registries — Official MCP and Glama, with 1 tracked version. It was first listed on Aug 24, 2026 and most recently updated on Aug 24, 2026.
Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.
What Kubernetes Troubleshoot can and cannot do
Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.
What you need before using Kubernetes Troubleshoot
The registry listing declares required configuration before first use — typically an API key, token or connection string set via environment variables.
Declared by Glama, last synced Nov 4, 2026. Not independently verified by MCP Toplist.
- KUBECONFIG · required
- ALLOWED_NAMESPACES · required
- LOG_LEVEL · optional
- API_TIMEOUT_SECONDS · optional
- MAX_LOG_LINES · optional
Connect Kubernetes Troubleshoot and confirm it works
claude mcp add k8s-troubleshoot-mcp -e "KUBECONFIG=<your KUBECONFIG>" -e "ALLOWED_NAMESPACES=<your ALLOWED_NAMESPACES>" -e "LOG_LEVEL=<your LOG_LEVEL>" -e "API_TIMEOUT_SECONDS=<your API_TIMEOUT_SECONDS>" -e "MAX_LOG_LINES=<your MAX_LOG_LINES>" -- docker run -i --rm --mount "type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly" docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0Replace each placeholder with your own value before saving.
[mcp_servers.k8s-troubleshoot-mcp]
command = "docker"
args = ["run", "-i", "--rm", "--mount", "type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly", "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"]
[mcp_servers.k8s-troubleshoot-mcp.env]
KUBECONFIG = "<your KUBECONFIG>"
ALLOWED_NAMESPACES = "<your ALLOWED_NAMESPACES>"
LOG_LEVEL = "<your LOG_LEVEL>"
API_TIMEOUT_SECONDS = "<your API_TIMEOUT_SECONDS>"
MAX_LOG_LINES = "<your MAX_LOG_LINES>"Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"k8s-troubleshoot-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly",
"docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
],
"env": {
"KUBECONFIG": "<your KUBECONFIG>",
"ALLOWED_NAMESPACES": "<your ALLOWED_NAMESPACES>",
"LOG_LEVEL": "<your LOG_LEVEL>",
"API_TIMEOUT_SECONDS": "<your API_TIMEOUT_SECONDS>",
"MAX_LOG_LINES": "<your MAX_LOG_LINES>"
}
}
}
}Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.
{
"mcpServers": {
"k8s-troubleshoot-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly",
"docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
],
"env": {
"KUBECONFIG": "<your KUBECONFIG>",
"ALLOWED_NAMESPACES": "<your ALLOWED_NAMESPACES>",
"LOG_LEVEL": "<your LOG_LEVEL>",
"API_TIMEOUT_SECONDS": "<your API_TIMEOUT_SECONDS>",
"MAX_LOG_LINES": "<your MAX_LOG_LINES>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.
{
"servers": {
"k8s-troubleshoot-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly",
"docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
],
"env": {
"KUBECONFIG": "<your KUBECONFIG>",
"ALLOWED_NAMESPACES": "<your ALLOWED_NAMESPACES>",
"LOG_LEVEL": "<your LOG_LEVEL>",
"API_TIMEOUT_SECONDS": "<your API_TIMEOUT_SECONDS>",
"MAX_LOG_LINES": "<your MAX_LOG_LINES>"
}
}
}
}Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"k8s-troubleshoot-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly",
"docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
],
"env": {
"KUBECONFIG": "<your KUBECONFIG>",
"ALLOWED_NAMESPACES": "<your ALLOWED_NAMESPACES>",
"LOG_LEVEL": "<your LOG_LEVEL>",
"API_TIMEOUT_SECONDS": "<your API_TIMEOUT_SECONDS>",
"MAX_LOG_LINES": "<your MAX_LOG_LINES>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"k8s-troubleshoot-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly",
"docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
],
"env": {
"KUBECONFIG": "<your KUBECONFIG>",
"ALLOWED_NAMESPACES": "<your ALLOWED_NAMESPACES>",
"LOG_LEVEL": "<your LOG_LEVEL>",
"API_TIMEOUT_SECONDS": "<your API_TIMEOUT_SECONDS>",
"MAX_LOG_LINES": "<your MAX_LOG_LINES>"
}
}
}
}Replace each placeholder with your own value before saving.
After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.
When to choose another server
No task-specific alternatives are catalogued for Kubernetes Troubleshootyet; the list above is its publisher's other servers.
What changed, and when this was checked
- First listed
- Aug 24, 2026
- Latest version published
- Aug 24, 2026
- Version history
- 1 version tracked (below)
- Requirements evidence
- Declared by Glama, last synced Nov 4, 2026. Not independently verified by MCP Toplist.
- Profile checked
- Not yet — purpose, capabilities and requirements above come from registry data only
- Ranking data as of
- Nov 4, 2026
- Official MCP ↗listed since Aug 25, 2026 · still listed
- Glama ↗listed since Sep 24, 2026 · still listed
Do you maintain Kubernetes Troubleshoot? to correct or enrich this profile.
Available versions (1)
| Version | Published |
|---|---|
| 1.0.0 | Aug 24, 2026 |
Ranks ahead of 82,176 of 168,415 servers on MCP Toplist.
Show your rank
Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.
[](https://mcptoplist.com/server/io.github.NanaGyamfiPrempeh30%2Fk8s-troubleshoot-mcp)<a href="https://mcptoplist.com/server/io.github.NanaGyamfiPrempeh30%2Fk8s-troubleshoot-mcp"><img src="https://mcptoplist.com/badge/io.github.NanaGyamfiPrempeh30%2Fk8s-troubleshoot-mcp.svg" alt="MCP Toplist: #86,239 of 168,415" /></a>Variants: append ?metric=score or ?metric=stars to the image URL.
Frequently asked questions
- Who maintains Kubernetes Troubleshoot?
- Kubernetes Troubleshoot is maintained by NanaGyamfiPrempeh30, which publishes 2 MCP servers (2 total versions) tracked on MCP Toplist.
- Is Kubernetes Troubleshoot listed on the Official MCP Registry?
- Yes — Kubernetes Troubleshoot is listed on the Official MCP Registry, alongside Glama.
- How many versions does Kubernetes Troubleshoot have?
- MCP Toplist tracks 1 version of Kubernetes Troubleshoot, most recently published on Aug 24, 2026.
- Where can I find the source code for Kubernetes Troubleshoot?
- The source code for Kubernetes Troubleshoot is hosted at github.com/NanaGyamfiPrempeh30/k8s-troubleshoot-mcp.
Do you run this server?
Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.