Skip to main content
Glama
ongjin
by ongjin

Related Servers

Alternatives to K8s Doctor MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables read-only, stack-aware diagnostics for microservices on Kubernetes, turning debugging runbooks into conversational tools that investigate slow requests, changes, leaks, and in-pod conditions without exposing cluster credentials.
      57
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interactive Kubernetes cluster monitoring and troubleshooting through natural language queries. Users can diagnose pod issues, check service status, and investigate cluster problems using conversational AI.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Kubernetes diagnostic agent that provides on-demand root cause analysis and human-in-the-loop remediation via Slack, using LLM reasoning with OPA-bounded security controls.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect and operate multiple Kubernetes clusters through natural language, providing multi-cluster diagnostics, RBAC analysis, security checks, and app-centric deployment with GitOps and smart workload placement.
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables real-time Kubernetes cluster observability and debugging through standardized MCP interface. Provides access to pods, services, nodes, events, and includes built-in tools for cluster health analysis and issue identification.
      -

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation3/5

    There is significant overlap between tools like diagnose-pod, debug-crashloop, and analyze-logs, which all involve analyzing pod issues with logs and events, potentially causing confusion. However, tools like list-namespaces and list-pods have distinct purposes, and the descriptions help clarify some boundaries, such as debug-crashloop focusing specifically on CrashLoop states.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., analyze-logs, check-events, list-pods), with clear and readable names. The only minor deviation is full-diagnosis, which uses a hyphenated adjective-noun form instead of a verb, but overall the naming is predictable and easy to understand.

    Tool Count5/5

    With 8 tools, the count is well-scoped for a Kubernetes diagnostic server, covering a range of common troubleshooting tasks without being overwhelming. Each tool appears to serve a specific purpose in cluster analysis, making the set appropriately sized for its domain.

    Completeness4/5

    The tool set covers key diagnostic areas like logs, events, resources, and pod states, with comprehensive tools like full-diagnosis. A minor gap is the lack of tools for proactive monitoring or remediation actions (e.g., fixing issues), but agents can work around this by using the analysis tools to identify problems.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues