Kubernetes MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP/HTTPS server (default: 3002) | 3002 |
| NODE_ENV | No | Node environment (production/development) | production |
| KUBECONFIG | Yes | Path to the Kubernetes configuration file (e.g., /path/to/kubeconfig) | |
| MINIKUBE_CPUS | No | Minikube CPU count (default: 2) | |
| MINIKUBE_DRIVER | No | Minikube driver (e.g., docker) | |
| MINIKUBE_MEMORY | No | Minikube memory in MB (default: 4096) | |
| KUBECTL_NAMESPACE | No | Default namespace for kubectl commands (default: default) | default |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_podsB | Obtener información de pods en Kubernetes |
| get_helm_releasesC | Obtener información de releases de Helm |
| get_cluster_infoB | Obtener información general del cluster |
| analyze_versionsC | Analizar versiones de componentes en el cluster |
| compare_versionsC | Comparar versiones de componentes |
| get_outdated_componentsC | Obtener componentes desactualizados |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The three get_* tools target distinct Kubernetes concepts, but analyze_versions, compare_versions, and get_outdated_components overlap heavily around version analysis, making it easy to confuse them. Descriptions help somewhat, but the boundaries between 'analyze', 'compare', and 'outdated' are not crisply defined.
Most tools follow a clear verb_noun pattern like get_pods, get_helm_releases, and get_outdated_components. However, analyze_versions and compare_versions break the 'get_' prefix convention, introducing minor inconsistency while remaining readable and predictable.
Six tools is a well-scoped number for a focused Kubernetes server. Each tool appears purposeful, and the count is within the ideal range for an agent to understand and navigate without overload.
The toolset covers cluster, pod, and Helm information plus version analysis, but it lacks common Kubernetes resources like deployments, services, nodes, and namespaces. It also has no mutation or upgrade operations, which may leave agents unable to act on version findings.