x=hub

your toolset

    build deployment
    sign in

    Kubernetes Troubleshoot

    mcpother
    io.github.NanaGyamfiPrempeh30/k8s-troubleshoot-mcp · v1.0.0
    deploy just this

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

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    #!/usr/bin/env bash
    # k8s-troubleshoot (io.github.NanaGyamfiPrempeh30/k8s-troubleshoot-mcp), recipe docker (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-k8s-troubleshoot.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec docker run --rm --name mcp-my-agent-k8s-troubleshoot -p 127.0.0.1:${PORT}:8000 -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
    
    [Unit]
    Description=MCP server k8s-troubleshoot (toolset my-agent), generated by Hub
    After=network-online.target docker.service
    Wants=network-online.target
    
    [Service]
    Type=simple
    User=mcp
    Group=mcp
    SupplementaryGroups=docker
    EnvironmentFile=/etc/mcp/my-agent.env
    Environment=HOME=/var/lib/mcp/k8s-troubleshoot
    WorkingDirectory=/var/lib/mcp/k8s-troubleshoot
    ExecStart=/opt/mcp/my-agent/bin/k8s-troubleshoot.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/k8s-troubleshoot
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    docker run --rm -p 127.0.0.1:8101:8000 -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
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-19T00:51:39+00:00).
    # Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
    #   cp .env.example .env    # fill the ${VAR}s
    #   docker compose up -d && bash smoke.sh
    # Remote servers are not here: clients reach them directly (see clients/).
    name: mcp-my-agent
    services:
      k8s-troubleshoot:
        image: docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0
        ports:
        - 127.0.0.1:8101:8000
        restart: unless-stopped
        x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
          HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
          instead.'
        environment:
          KUBECONFIG: ${KUBECONFIG}
          ALLOWED_NAMESPACES: ${ALLOWED_NAMESPACES}
          LOG_LEVEL: ${LOG_LEVEL}
          API_TIMEOUT_SECONDS: ${API_TIMEOUT_SECONDS}
          MAX_LOG_LINES: ${MAX_LOG_LINES}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-19T00:51:39+00:00).
    #   kubectl create namespace mcp
    #   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
    #   kubectl apply -f kubernetes.yaml
    # Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
    # with auth in front before exposing any of them.
    apiVersion: v1
    kind: Namespace
    metadata:
      name: mcp
    ---
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: k8s-troubleshoot
      namespace: mcp
      labels: &id001
        app: k8s-troubleshoot
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: k8s-troubleshoot
            image: docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: KUBECONFIG
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: KUBECONFIG
            - name: ALLOWED_NAMESPACES
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: ALLOWED_NAMESPACES
            - name: LOG_LEVEL
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: LOG_LEVEL
            - name: API_TIMEOUT_SECONDS
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: API_TIMEOUT_SECONDS
            - name: MAX_LOG_LINES
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MAX_LOG_LINES
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: k8s-troubleshoot
      namespace: mcp
    spec:
      selector:
        app: k8s-troubleshoot
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-19T00:51:39+00:00).
    # Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
    # Each server under `servers` is one Deployment + Service; the keys after it configure
    # upstream charts a worker verified.
    servers:
      k8s-troubleshoot:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: k8s-troubleshoot
          image: docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: KUBECONFIG
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: KUBECONFIG
          - name: ALLOWED_NAMESPACES
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: ALLOWED_NAMESPACES
          - name: LOG_LEVEL
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: LOG_LEVEL
          - name: API_TIMEOUT_SECONDS
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: API_TIMEOUT_SECONDS
          - name: MAX_LOG_LINES
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MAX_LOG_LINES
    
    # helm install my-agent helm/my-agent -n mcp
    

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb

    The form opens with CHANGE_ME for each value you supply: KUBECONFIG, ALLOWED_NAMESPACES, LOG_LEVEL, API_TIMEOUT_SECONDS, MAX_LOG_LINES. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure

    A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.

    connect to it

    copy what your client needs
    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
    {
      "mcpServers": {
        "k8s-troubleshoot": {
          "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": "${KUBECONFIG}",
            "ALLOWED_NAMESPACES": "${ALLOWED_NAMESPACES}",
            "LOG_LEVEL": "${LOG_LEVEL}",
            "API_TIMEOUT_SECONDS": "${API_TIMEOUT_SECONDS}",
            "MAX_LOG_LINES": "${MAX_LOG_LINES}"
          }
        }
      }
    }
    #!/usr/bin/env bash
    # Registers every server with Claude Code (run once; `claude mcp list` to check).
    set -euo pipefail
    set -a; [ -f .env ] && source .env; set +a
    claude mcp add k8s-troubleshoot -e "KUBECONFIG=${KUBECONFIG}" -e "ALLOWED_NAMESPACES=${ALLOWED_NAMESPACES}" -e "LOG_LEVEL=${LOG_LEVEL}" -e "API_TIMEOUT_SECONDS=${API_TIMEOUT_SECONDS}" -e "MAX_LOG_LINES=${MAX_LOG_LINES}" -- 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
    
    {
      "mcpServers": {
        "k8s-troubleshoot": {
          "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": "${KUBECONFIG}",
            "ALLOWED_NAMESPACES": "${ALLOWED_NAMESPACES}",
            "LOG_LEVEL": "${LOG_LEVEL}",
            "API_TIMEOUT_SECONDS": "${API_TIMEOUT_SECONDS}",
            "MAX_LOG_LINES": "${MAX_LOG_LINES}"
          }
        }
      }
    }
    {
      "servers": {
        "k8s-troubleshoot": {
          "type": "stdio",
          "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": "${KUBECONFIG}",
            "ALLOWED_NAMESPACES": "${ALLOWED_NAMESPACES}",
            "LOG_LEVEL": "${LOG_LEVEL}",
            "API_TIMEOUT_SECONDS": "${API_TIMEOUT_SECONDS}",
            "MAX_LOG_LINES": "${MAX_LOG_LINES}"
          }
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.github.NanaGyamfiPrempeh30/k8s-troubleshoot-mcp
    
    • not probed yet: tools unpinned, ingest lists them

    tools

    Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.