Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KUBECONFIGNoPath to the kubeconfig file. If empty, the server loads the default kubeconfig and falls back to in-cluster config.
K8S_CONTEXTNoKubernetes context to use from the kubeconfig.
K8S_NAMESPACENoDefault namespace to use for Kubernetes operations.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
k8s_connectC

Load a kubeconfig context, or in-cluster config when no kubeconfig is available.

k8s_disconnectC

Drop a Kubernetes session.

k8s_statusB

List Kubernetes sessions.

k8s_list_namespacesB

List namespace names.

k8s_list_podsB

List pods with phase, ready count, and node.

k8s_pod_logsB

Read the tail of a pod log.

k8s_eventsA

Show the latest 30 namespaced events.

k8s_list_deploymentsB

List deployments and ready replica counts.

k8s_list_servicesB

List services, type, and cluster IP.

k8s_list_nodesB

List nodes and Ready condition.

k8s_list_secret_namesB

List Secret names only. Values are not returned.

k8s_scaleC

Scale a Deployment.

k8s_restartC

Roll a Deployment by setting restartedAt.

k8s_delete_podB

Delete one pod so the controller recreates it. confirm=true is required.

k8s_applyB

Create or patch a Deployment or ConfigMap from YAML.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 15 tools

Disambiguation5/5

Each tool targets a distinct resource and action: connect/disconnect manage sessions, list_* covers different Kubernetes resources, and pod_logs/scale/restart/delete_pod/apply are specific operations. There is no meaningful overlap—even multiple pod-related tools are clearly differentiated by their verbs.

Naming Consistency4/5

All tools share the k8s_ prefix and generally follow a verb_noun pattern (list_namespaces, scale, delete_pod). Minor deviations exist: k8s_events and k8s_pod_logs omit the list/get verb, but the pattern is still predictable and readable.

Tool Count4/5

At 15 tools, the server sits at the upper bound of the typical well-scoped range. The breadth is justified by covering connection management plus a variety of Kubernetes resources and operations, though it feels slightly heavy for a single-purpose MCP server.

Completeness3/5

The server covers listing many resources, logs, events, scaling, restarting, and applying YAML, but lacks get operations for individual resources, delete for most resources (only pods), and any write operations for services, secrets, or namespaces. It is read-heavy with limited lifecycle coverage beyond Deployments.

Maintenance

ActivityMaintained
ResponsivenessNo issues