Loading…
Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes.
Kubernetes Troubleshoot is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 73/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding Kubernetes Troubleshoot to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
docker run -i --rm docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0Review the upstream source before running this command.
{
"_meta": {
"io.modelcontextprotocol.registry/official": {
"status": "active",
"isLatest": true,
"updatedAt": "2026-08-24T20:12:54.510649Z",
"publishedAt": "2026-08-24T20:12:54.510649Z",
"statusChangedAt": "2026-08-24T20:12:54.510649Z"
}
},
"server": {
"name": "io.github.NanaGyamfiPrempeh30/k8s-troubleshoot-mcp",
"title": "Kubernetes Troubleshoot",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"version": "1.0.0",
"packages": [
{
"transport": {
"type": "stdio"
},
"identifier": "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0",
"runtimeHint": "docker",
"registryType": "oci",
"runtimeArguments": [
{
"name": "--mount",
"type": "named",
"value": "type=bind,src={kubeconfig_path},dst=/kubeconfig,readonly",
"variables": {
"kubeconfig_path": {
"format": "filepath",
"isRequired": true,
"description": "Absolute path on the host to a kubeconfig scoped to the diagnostic ServiceAccount. Generate it with scripts/generate-kubeconfig.sh — do not mount an admin kubeconfig. The file must be readable by UID 10001, which the container runs as."
}
},
"isRequired": true,
"description": "Mount the kubeconfig read-only. This server performs no writes of any kind, so a writable mount would grant privilege it has no use for."
}
],
"environmentVariables": [
{
"name": "KUBECONFIG",
"default": "/kubeconfig",
"isRequired": true,
"description": "Path to the kubeconfig inside the container. Must match the mount destination. There is no fallback to ~/.kube/config and no in-cluster config: a missing, unreadable or malformed file is a startup failure rather than a silent downgrade to an ambient credential."
},
{
"name": "ALLOWED_NAMESPACES",
"format": "string",
"isRequired": true,
"description": "Comma-separated namespaces the server may read, e.g. staging,production. Wildcards (* and all) are rejected at startup, and kube-system and kube-public are stripped even if listed. This is defense-in-depth, not the security boundary — the boundary is the ServiceAccount's RBAC bindings."
},
{
"name": "LOG_LEVEL",
"default": "INFO",
"description": "DEBUG, INFO, WARNING or ERROR. All logging goes to stderr; stdout carries the JSON-RPC stream exclusively."
},
{
"name": "API_TIMEOUT_SECONDS",
"default": "30",
"description": "Kubernetes API request timeout. Must be a positive integer."
},
{
"name": "MAX_LOG_LINES",
"default": "200",
"description": "Maximum log lines any single get_pod_logs call may return. Must be a positive integer; clamped to a hard ceiling of 1000 with a warning."
}
]
}
],
"repository": {
"url": "https://github.com/NanaGyamfiPrempeh30/k8s-troubleshoot-mcp",
"source": "github"
},
"websiteUrl": "https://github.com/NanaGyamfiPrempeh30/k8s-troubleshoot-mcp#readme",
"description": "Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes."
}
}