A
licenseNot graded
qualityD
maintenanceAn MCP server for generating Kubernetes manifests (deployments, services, configmaps, secrets, ingresses, namespaces) and performing kubectl operations like apply, delete, get, describe, logs, and exec.
MIT
k8s-interactive-mcp
by TaichiHo
Related Servers
Alternatives to k8s-interactive-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityAmaintenanceA powerful and flexible Kubernetes MCP server implementation with support for OpenShift.2,116GoApache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets AI assistants safely inspect and operate on Kubernetes clusters through natural conversation.88 PyPIMIT
- 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 gradedqualityDmaintenanceThis project is intended as a both MCP server connecting to Kubernetes and a library to build more servers for any custom resources in Kubernetes.384MIT
TDQS
B3.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as running kubectl commands, making it impossible for an agent to confuse it with another tool.
Naming Consistency5/5
Since there is only one tool, naming consistency is inherently perfect. The tool name 'run_kubectl_command' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
Tool Count2/5
A single tool is too few for a Kubernetes management server, as it lacks coverage for common operations like listing resources, applying configurations, or checking cluster status. This forces agents to rely solely on raw kubectl commands, which is inefficient and error-prone for the domain.
Completeness2/5
The tool surface is severely incomplete for Kubernetes management. While 'run_kubectl_command' provides a generic entry point, it lacks dedicated tools for essential operations such as get, apply, delete, describe, or logs, leaving significant gaps that will cause agent failures in automated workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues