MCP Server Kubernetes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENABLE_TELEMETRY | No | Set to 'true' to enable OpenTelemetry observability. | |
| OTEL_TRACES_SAMPLER | No | Sampling strategy for traces (e.g., 'always_on', 'always_off', or a ratio like '0.1'). | |
| OTEL_EXPORTER_OTLP_ENDPOINT | No | The OTLP endpoint URL for exporting telemetry data (e.g., http://localhost:4317). | |
| ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS | No | Set to 'true' to enable non-destructive mode, disabling destructive operations (delete, uninstall, cleanup, etc.). |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cleanupC | Cleanup all managed resources |
| kubectl_getA | Get or list Kubernetes resources by resource type, name, and optionally namespace |
| kubectl_describeA | Describe Kubernetes resources by resource type, name, and optionally namespace |
| kubectl_applyC | Apply a Kubernetes YAML manifest from a string or file |
| kubectl_deleteB | Delete Kubernetes resources by resource type, name, labels, or from a manifest file |
| kubectl_createC | Create Kubernetes resources using various methods (from file or using subcommands) |
| kubectl_logsB | Get logs from Kubernetes resources like pods, deployments, or jobs |
| kubectl_scaleB | Scale a Kubernetes deployment |
| kubectl_patchB | Update field(s) of a resource using strategic merge patch, JSON merge patch, or JSON patch |
| kubectl_rolloutB | Manage the rollout of a resource (e.g., deployment, daemonset, statefulset) |
| kubectl_contextB | Manage Kubernetes contexts - list, get, or set the current context |
| kubectl_reconnectA | Reconnect to the Kubernetes API server by recreating all API clients. Use this after cluster upgrades (e.g., EKS control plane upgrades that rotate ENIs/IPs) to force fresh DNS resolution and new TCP connections. |
| explain_resourceB | Get documentation for a Kubernetes resource or field |
| install_helm_chartA | Install a Helm chart with support for both standard and template-based installation |
| upgrade_helm_chartC | Upgrade an existing Helm chart release |
| uninstall_helm_chartC | Uninstall a Helm chart release |
| node_managementB | Manage Kubernetes nodes with cordon, drain, and uncordon operations |
| port_forwardC | Forward a local port to a port on a Kubernetes resource |
| stop_port_forwardD | Stop a port-forward process |
| exec_in_podA | Execute a command in a Kubernetes pod or container and return the output. Command must be an array of strings where the first element is the executable and remaining elements are arguments. This executes directly without shell interpretation for security. |
| list_api_resourcesC | List the API resources available in the cluster |
| kubectl_genericB | Execute any kubectl command with the provided arguments and flags |
| pingA | Verify that the counterpart is still responsive and the connection is alive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| k8s-diagnose | Diagnose Kubernetes Resources. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Kubernetes Pods | List of pods in the default namespace |
| Kubernetes Deployments | List of deployments in the default namespace |
| Kubernetes Services | List of services in the default namespace |
| Kubernetes Namespaces | List of all namespaces |
| Kubernetes Nodes | List of all nodes in the cluster |
TDQS
Scored across 23 tools
Each tool has a clearly distinct purpose, from kubectl operations to Helm management and node control. Even similar actions like kubectl_apply and kubectl_create are differentiated by input type. No overlapping functions.
Tools are grouped with prefixes like kubectl_, helm_, and standalone names (e.g., exec_in_pod). Within each group naming is consistent, but the mix of prefixed and non-prefixed tools creates minor inconsistency.
23 tools is well-scoped for Kubernetes management, covering essential operations without redundancy. Each tool addresses a specific need, and the count feels complete but not overwhelming.
Covers core Kubernetes lifecycle (create, read, update, delete, rollout, scale, logs, exec), Helm chart management, node ops, port forwarding, and includes a generic kubectl command for edge cases. No obvious gaps.