Kubernetes Troubleshoot

io.github.NanaGyamfiPrempeh30/k8s-troubleshoot-mcp

Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes.

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "k8s-troubleshoot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
      ],
      "env": {
        "KUBECONFIG": "<your KUBECONFIG>",
        "ALLOWED_NAMESPACES": "<your ALLOWED_NAMESPACES>",
        "LOG_LEVEL": "INFO",
        "API_TIMEOUT_SECONDS": "30",
        "MAX_LOG_LINES": "200"
      }
    }
  }
}
Environment variables
  • KUBECONFIGrequiredPath 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.
  • ALLOWED_NAMESPACESrequiredComma-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.
  • LOG_LEVELDEBUG, INFO, WARNING or ERROR. All logging goes to stderr; stdout carries the JSON-RPC stream exclusively.
  • API_TIMEOUT_SECONDSKubernetes API request timeout. Must be a positive integer.
  • MAX_LOG_LINESMaximum 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.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.0.0
Registry
active
Published
8/24/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that Kubernetes Troubleshoot is listed here — it’s also the link we check for a free listing.

Kubernetes Troubleshoot — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-nanagyamfiprempeh30-k8s-troubleshoot-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Kubernetes Troubleshoot — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Kubernetes Troubleshoot — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-nanagyamfiprempeh30-k8s-troubleshoot-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.