A
licenseA
qualityA
maintenanceProvides a set of read-only Kubernetes functions via an MCP server, enabling interaction with Kubernetes clusters through agents or coding assistants like GitHub Copilot.
9
3
Apache 2.0
k8s-mcp-server
Related Servers
Alternatives to k8s-mcp-server
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
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server that gives AI assistants full visibility and control over Kubernetes clusters.73MIT
- 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 gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with Kubernetes clusters through natural language, supporting core Kubernetes operations, monitoring, security, and diagnostics.39 npm960MIT
- FlicenseNot gradedqualityDmaintenanceAn Model Context Protocol server that lets language models directly manage and visualize Kubernetes clusters through safe, high-level operational tools.1-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
TDQS
A4.7/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct Kubernetes resource or action: namespaces, pods, logs, events, deployments, and services. No functional overlap that would confuse tool selection.
Naming Consistency4/5
Names follow a consistent lowercase snake_case verb_noun pattern, but four use 'list_' while two use 'get_'. The split is semantically reasonable yet not perfectly uniform.
Tool Count5/5
Six tools form a focused, readable set for read-only Kubernetes inspection and troubleshooting, without redundant or excessive entries.
Completeness5/5
The set covers the core resources needed for workload troubleshooting: namespaces, pods, logs, cluster events, deployments, and services. There are no obvious dead ends for the inferred read-only diagnostic domain.
Maintenance
ActivityMaintained
ResponsivenessNo issues