Skip to main content
Glama
raihan0824

kubernetes-runbooks-mcp-server

by raihan0824
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to kubernetes-runbooks-mcp-server

No user-submitted related servers found.

    Related Servers

    • Kubernetes MCP Server

      kishanrao92
      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.
      -

    • kube-diagnostics-mcp

      ranson21
      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

    • K8s Doctor MCP

      ongjin
      A
      license
      B
      quality
      D
      maintenance
      AI-powered Kubernetes diagnostics that analyzes pod crashes, logs, and cluster health to provide root cause analysis and actionable solutions for common issues like CrashLoopBackOff, OOM kills, and connection errors.
      8
      4 npm
      1
      MIT

    • Claude Ops Investigator

      Randhir123
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only Kubernetes incident investigation through MCP tools for listing pods, describing resources, fetching logs, and searching runbooks.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: fetching a runbook by topic, listing all topics, and searching by keyword. There is no overlap in functionality, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., fetch-runbook, list-topics). The convention is uniform and predictable.

    Tool Count5/5

    Three tools is well-scoped for a read-only Kubernetes runbook server. It provides essential operations (list, fetch, search) without unnecessary bloat.

    Completeness5/5

    The tool surface covers the core read operations for runbooks: listing topics, fetching by topic, and searching. No obvious gaps exist given the server's stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources