OpenShift 4 MCP Server
Related Servers
Alternatives to OpenShift 4 MCP Server
- AlicenseNot gradedqualityCmaintenanceAn open source MCP server empowering SREs with intelligent observability, predictive analytics, and AI-driven automation across Kubernetes, OpenShift, and Tekton environments.31 PyPI11Apache 2.0
Related Servers
- FlicenseAqualityDmaintenanceAI-powered MCP server for enterprise OpenShift/Kubernetes cluster management, providing diagnostic tools, RAG knowledge retrieval, and autonomous remediation recommendations.9-
- FlicenseNot gradedqualityDmaintenanceAn 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.-
- AlicenseAqualityBmaintenanceAn MCP server exposing 72 tools across 26 homelab services, enabling LLMs to monitor and manage infrastructure, media, storage, and networking with a single endpoint.16MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that connects LLMs to Kubernetes clusters for troubleshooting, scanning failing pods, diagnosing root causes, and applying guarded fixes or generating manifests via natural language.MIT
- AlicenseAqualityBmaintenanceCloudOps 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.6MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the Red Hat Advanced Cluster Security for Kubernetes API, providing LLM access to all 69 API services and 361 endpoints through six meta-tools for discovery, inspection, and direct API calls.Apache 2.0
TDQS
Scored across 216 tools
Every tool name includes a specific action and resource type (e.g., list_pods, get_pod, scale_deployment), making each tool's purpose clear and distinct. Even with 216 tools, the consistent naming prevents ambiguity, and generic escape hatches like run_oc_command are explicitly labeled.
All tools follow a consistent verb_noun pattern (list_, get_, create_, delete_, scale_, rollout_*, etc.), with resource types as the noun. Deviations like apply_manifest and get_resource still adhere to the same structure, ensuring predictability.
216 tools is extreme and far exceeds any reasonable scope for an MCP server. Even for a comprehensive OpenShift management platform, this count is overwhelming and will likely confuse agents, making tool selection difficult. It falls into the 'extreme mismatch' category.
The tool set covers an extensive range of OpenShift domains including compute, networking, storage, security, operators, machine management, monitoring, service mesh, OpenShift AI, virtualization, GitOps, Tekton, and ACM. However, some resource types lack individual get/update/delete operations (e.g., Deployments have no get or delete), relying on generic tools like get_resource and delete_resource, creating minor gaps.