Skip to main content
Glama
kamroy

platform-mcp-server

by kamroy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to platform-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • kubeaid-mcp

      1Shubham7
      A
      license
      A
      quality
      D
      maintenance
      Exposes a Kubernetes cluster to MCP-compatible AI clients, enabling read-only and optional write operations on cluster resources like pods, deployments, and namespaces through natural language.
      9
      1
      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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource (tenants, pods, SLO, ArgoCD applications, chaos schedules, catalog services) with clear descriptions. Even the tenant-specific tools (pods, SLO, chaos schedules) are differentiated by the resource they return, so there is minimal ambiguity.

    Naming Consistency4/5

    The naming generally follows a list_/get_ prefix with resource names, but the pattern is not perfectly consistent: list_ is used for global resources while get_ is used for tenant-specific ones, and get_chaos_schedules omits 'tenant' from its name. Despite this minor deviation, the verb_noun structure is recognizable.

    Tool Count5/5

    Six tools is a well-scoped number for a read-only platform observability server. The set covers the main platform resources without unnecessary bloat, and each tool serves a distinct purpose within the apparent domain.

    Completeness3/5

    The tool set covers listing and basic tenant-scoped queries but lacks any single-resource detail views (e.g., a specific ArgoCD app or catalog service) and any management/mutation operations. This limits the surface to read-only inspection, which may be intentional but leaves notable gaps for a 'platform' server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources