Skip to main content
Glama
mikhae1

kubeview-mcp

by mikhae1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to kubeview-mcp

No user-submitted related servers found.

    Related Servers

    • kubernetes-mcp

      kkb0318
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that provides safe, read-only access to Kubernetes resources for debugging and inspection. Built with security in mind, it offers comprehensive cluster visibility without modification capabilities.
      43
      MIT

    • opsagent

      batpepe
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes Kubernetes cluster telemetry tools (pods, events, logs, metrics, ArgoCD syncs) with automatic redaction for incident triage and hypothesis ranking.
      MIT

    • k8s-readonly-mcp

      ziyuyu23
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for inspecting Kubernetes clusters, allowing LLMs to list resources, describe pods, and read logs without mutation.
      5
      MIT

    • platform-mcp-server

      kamroy
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.
      6
      -
    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 2 tools

    Disambiguation5/5

    run_code and kube_pod_exec have clearly distinct purposes: one executes TypeScript scripts against Kubernetes APIs, the other runs commands inside pod containers. There is no functional overlap, so agents should not confuse them.

    Naming Consistency3/5

    Both names follow a verb_noun pattern, but their styles diverge: run_code uses a bare verb and object, while kube_pod_exec uses a kube_ prefix and a more specific compound noun. This inconsistency is minor but noticeable.

    Tool Count3/5

    With only two tools, the server is on the thin side. However, one tool is a flexible code-execution interface, so the count might be acceptable for a narrow, specialized scope.

    Completeness2/5

    The server is named kubeview, yet there are no viewing or resource-list tools. run_code can potentially interact with Kubernetes capabilities, but it does not provide a direct, discoverable surface for typical read operations, leaving significant gaps for a toolset claiming to be a Kubernetes viewer.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources