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

    • mcp-argocd

      vish288
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to interact with Argo CD through its REST API, providing tools to triage application status, sync, roll back, inspect drift, read logs, and manage ApplicationSets, clusters, projects, and repositories. Supports read-only safeguards, curated GitOps resources, and workflow prompts for safe operations.
      37
      272 PyPI
      MIT

    • 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

    • k8s-docs-mcp

      villadalmine
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to search official Kubernetes documentation, retrieve verified canonical YAML manifests, and deterministically check API versions, deprecations, and removals directly from upstream Kubernetes sources.
      5
      Apache 2.0
    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources