Skip to main content
Glama
nicolasmosquerar

k8s-mcp-assistant

by nicolasmosquerar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to k8s-mcp-assistant

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • mcp-k8s-ro

      your-ko
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that gives Claude safe access to Kubernetes clusters, enabling listing, describing, and monitoring resources without mutation risks and with secret masking.
      1
      MIT

    • Kubernetes Monitor

      vlttnv
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for Kubernetes that allows querying cluster information and diagnosing issues through natural language interfaces like Claude.
      8
      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

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one checks pod status for an application, while the other retrieves logs for a specific pod. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern using 'k8s.' prefix and snake_case (app_status, pod_logs). This uniformity enhances readability and predictability across the tool set.

    Tool Count2/5

    With only two tools, the server feels thin for a Kubernetes assistant domain, which typically involves more operations like scaling, deployment, or resource management. This limited scope may hinder agent workflows.

    Completeness2/5

    The tool set is severely incomplete for Kubernetes operations, lacking essential CRUD actions such as creating, updating, or deleting resources. Agents will face significant gaps when trying to perform common tasks in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources