Skip to main content
Glama
perfectra1n

kubesearch-mcp

by perfectra1n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to kubesearch-mcp

No user-submitted related servers found.

    Related Servers

    • Argo CD MCP Server

      mane-tv2
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.
      Apache 2.0

    • K8s MCP Server

      apecloud
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs like Claude to securely execute Kubernetes CLI tools (kubectl, helm, istioctl, argocd) across multiple clusters through dynamic kubeconfig support, allowing natural language Kubernetes management and operations.
      5
      MIT

    • argocd-mcp

      adityaraj178
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Argo CD applications through natural language, providing tools for cluster, project, application, and resource management via stdio and HTTP transports.
      Apache 2.0

    • mcp-openshift

      dockndevai
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to explore and operate OpenShift/Kubernetes clusters, offering read-only tools for projects, pods, logs, and resources, with opt-in higher modes for scaling, restarts, applying manifests, and deletions under safe-by-default guards.
      6
      241 npm
      MIT
    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

    A4.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: kubesearch_* handles index-wide searches and details, while repo_* handles cloned repository file operations. Even the three grep-like tools are cleanly separated by scope (indexed values across all repos, all files in popular repos, and a specific cloned repo).

    Naming Consistency4/5

    Names largely follow a domain-prefix plus action pattern: kubesearch_search_*, kubesearch_get_*, repo_clone, repo_read_file, repo_grep. Minor deviations exist (repo_cleanup is noun-first, kubesearch_grep_values uses a verb-noun pairing not mirrored elsewhere), but the convention is predictable enough.

    Tool Count5/5

    Eleven tools is a well-scoped set for the server's purpose: search the kubesearch.dev index, retrieve release details, and inspect real repositories. Each tool covers a distinct operation and none feel redundant or ornamental.

    Completeness5/5

    The surface covers the full workflow: search releases/images/values, get detailed release information, clone repos, list/read/grep files, and clean up clones. The only minor nicety might be explicit pagination on release search, but detailed deployment pagination is already covered via kubesearch_get_release.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources