K8s Doctor MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KUBECONFIG | No | Path to the kubeconfig file for Kubernetes cluster access (defaults to ~/.kube/config if not set) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diagnose-podC | Analyzes pod status, logs, and events to identify root causes and suggest solutions |
| debug-crashloopC | Analyzes pods in CrashLoop state by examining exit codes, logs, and events to find the root cause |
| analyze-logsC | Detects error patterns in logs and suggests causes and solutions (Connection Refused, OOM, DB errors, etc.) |
| check-resourcesC | Compares pod CPU/Memory usage against limits to check for threshold violations |
| full-diagnosisC | Comprehensively analyzes cluster nodes, pods, and resources to evaluate health |
| check-eventsC | Queries events for specific resources or namespaces and analyzes Warning events |
| list-namespacesB | Lists all namespaces in the cluster |
| list-podsC | Lists all pods in a specific namespace |
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 8 tools
There is significant overlap between tools like diagnose-pod, debug-crashloop, and analyze-logs, which all involve analyzing pod issues with logs and events, potentially causing confusion. However, tools like list-namespaces and list-pods have distinct purposes, and the descriptions help clarify some boundaries, such as debug-crashloop focusing specifically on CrashLoop states.
Most tools follow a consistent verb_noun pattern (e.g., analyze-logs, check-events, list-pods), with clear and readable names. The only minor deviation is full-diagnosis, which uses a hyphenated adjective-noun form instead of a verb, but overall the naming is predictable and easy to understand.
With 8 tools, the count is well-scoped for a Kubernetes diagnostic server, covering a range of common troubleshooting tasks without being overwhelming. Each tool appears to serve a specific purpose in cluster analysis, making the set appropriately sized for its domain.
The tool set covers key diagnostic areas like logs, events, resources, and pod states, with comprehensive tools like full-diagnosis. A minor gap is the lack of tools for proactive monitoring or remediation actions (e.g., fixing issues), but agents can work around this by using the analysis tools to identify problems.