Kubernetes Troubleshoot

Kubernetes Troubleshoot runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e KUBECONFIG -e ALLOWED_NAMESPACES -e LOG_LEVEL -e API_TIMEOUT_SECONDS -e MAX_LOG_LINES docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0. It reads these environment variables: KUBECONFIG (required), ALLOWED_NAMESPACES (required), LOG_LEVEL, API_TIMEOUT_SECONDS and MAX_LOG_LINES; set them in the client's configuration for this server. Required arguments: --mount.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "k8s-troubleshoot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "KUBECONFIG",
        "-e",
        "ALLOWED_NAMESPACES",
        "-e",
        "LOG_LEVEL",
        "-e",
        "API_TIMEOUT_SECONDS",
        "-e",
        "MAX_LOG_LINES",
        "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
      ],
      "env": {
        "KUBECONFIG": "<value>",
        "ALLOWED_NAMESPACES": "<value>",
        "LOG_LEVEL": "<value>",
        "API_TIMEOUT_SECONDS": "<value>",
        "MAX_LOG_LINES": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect