k8scortex-mcp
Related Servers
Alternatives to k8scortex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to interact with Kubernetes clusters by translating natural language into kubectl and Helm operations. It allows users to query, manage, and diagnose Kubernetes resources and cluster states through a seamless integration.21Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables natural language interaction with Kubernetes clusters, allowing management of pods, deployments, namespaces, and cluster resources through conversational queries or API endpoints.1MIT
- 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
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets AI assistants safely inspect and operate on Kubernetes clusters through natural conversation.MIT
- AlicenseCqualityBmaintenanceAn MCP server that provides complete Kubernetes API operations, enabling cluster management, resource CRUD, diagnostics, backup/restore, and multi-cluster configuration via natural language.322MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered Kubernetes management using natural language, supporting kubectl, Helm, diagnostics, and port forwarding via MCP protocol.MIT
TDQS
Scored across 75 tools
Each tool targets a distinct resource and action, with detailed descriptions that clearly separate them. Despite the high number, there is no ambiguity between tools like list_pods, get_pod_logs, and describe_pod.
Most tools follow a verb_noun pattern in snake_case (e.g., list_pods, create_deployment). However, there is a mix of 'get_' and 'describe_' for similar operations, and some verbs like 'cordon' and 'drain' are non-standard, causing slight inconsistency.
With 75 tools, the server is extremely overloaded. Even for a comprehensive Kubernetes management server, this number far exceeds the typical well-scoped range (3-15) and qualifies as an extreme mismatch, making it difficult for agents to navigate.
The tool set covers a wide range of Kubernetes resources and GitOps operations, including CRUD for many resources and additional utilities. Minor gaps like missing update_deployment and delete_pod exist, but the overall surface is quite complete for cluster management.