A
licenseB
qualityB
maintenanceA Model Context Protocol (MCP) server that gives AI assistants full visibility and control over Kubernetes clusters.
73
MIT
Radar
by skyhook-io
Related Servers
Alternatives to Radar
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityAmaintenanceModel Context Protocol (MCP) server for debugging, analyzing, and diagnosing Kubernetes clusters directly from AI agents.66MIT
- FlicenseAqualityDmaintenanceAI-powered MCP server for enterprise OpenShift/Kubernetes cluster management, providing diagnostic tools, RAG knowledge retrieval, and autonomous remediation recommendations.9-
- FlicenseNot gradedqualityCmaintenanceAn MCP server for autonomous Kubernetes troubleshooting and remediation. It enables continuous cluster monitoring, local AI-powered diagnosis via Ollama, and automated kubectl-based fixes.-
- AlicenseNot gradedqualityCmaintenanceAn open source MCP server empowering SREs with intelligent observability, predictive analytics, and AI-driven automation across Kubernetes, OpenShift, and Tekton environments.11Apache 2.0
TDQS
A4.4/5.0
Scored across 25 tools
Disambiguation5/5
Each tool targets a distinct concern: get_dashboard and issues for triage, diagnose for deep root-cause, get_pod_logs vs get_workload_logs for log scope, search for content lookup, and manage_* for explicit actions. Even where overlap exists (e.g., diagnose bundles get_resource+events+logs), the descriptions explicitly tell the agent which to use and when, eliminating ambiguity.
Naming Consistency4/5
The majority follow a clear verb_noun pattern: get_* for reads, list_* for enumeration, manage_* for actions, apply_resource/patch_resource for writes. Minor deviations like 'issues' and 'diagnose' act as situational verbs (state analysis) and are still distinct and readable, so the set remains predictable overall.
Tool Count4/5
25 tools is at the heavy end of the recommended range, but the breadth is justified for a Kubernetes diagnostics platform covering reads, writes, logs, metrics, events, RBAC, Helm, GitOps, and topology. Each tool serves a unique purpose with no gratuitous duplication, so the count is appropriate for the domain's complexity.
Completeness4/5
The surface covers discovery (list_*, search), troubleshooting (issues, diagnose, logs, events, metrics), management (apply/patch, manage_*), and specialized views (topology, neighborhood, RBAC, GitOps). The most notable gap is the absence of a delete resource tool, but the read/manage/act coverage is strong enough that agents won't hit dead ends.
Maintenance
ActivityActive
ResponsivenessUnresponsive