Skip to main content
Glama
ay-garg

OpenShift 4 MCP Server

by ay-garg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to OpenShift 4 MCP Server

No user-submitted related servers found.

    Related Servers

    • LUMINO MCP Server

      spre-sre
      A
      license
      Not graded
      quality
      C
      maintenance
      An open source MCP server empowering SREs with intelligent observability, predictive analytics, and AI-driven automation across Kubernetes, OpenShift, and Tekton environments.
      11
      Apache 2.0

    • OpsPilot MCP

      srurora
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server exposing Kubernetes-style diagnostic tools to an LLM agent, with a safety approval gate for destructive actions, all backed by a mock cluster for local testing.
      -

    • CloudOps MCP

      bienherasme
      A
      license
      A
      quality
      B
      maintenance
      CloudOps MCP is a read-only Model Context Protocol server that exposes normalized operational infrastructure context (logs, metrics, deployments, health) to AI agents through a small set of typed, bounded tools.
      6
      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.2/5.0

    Scored across 138 tools

    Disambiguation5/5

    Each tool targets a specific resource and action (e.g., list_pods, get_pod, delete_pod), with clear descriptions that distinguish overlapping concepts like list_custom_resources vs. get_resource. The escape hatch run_oc_command is clearly marked as a last resort.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., list_pods, create_namespace, delete_service). Verbs are uniform (list, get, create, delete, scale, start, stop, etc.), with only rare exceptions like rolllout_restart_deployment which still fits the pattern.

    Tool Count4/5

    138 tools is high, but appropriate for a comprehensive OpenShift management server covering many subsystems (core K8s, builds, operators, service mesh, AI, VMs, ACM, etc.). While it borders on excessive, each tool serves a distinct purpose in its domain.

    Completeness4/5

    The toolset covers most CRUD/lifecycle operations across a wide range of resources. Minor gaps exist (e.g., no direct create/update for Deployments, Services), but these can be addressed via apply_manifest. Overall, it provides a thorough surface for cluster management.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources