kubernetes-runbooks-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-runbookB | Fetch a specific Kubernetes runbook by topic |
| search-runbooksB | Search through Kubernetes runbooks by keyword |
| list-topicsA | List all available Kubernetes runbook topics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| troubleshoot-k8s | Get troubleshooting guidance for Kubernetes issues |
| runbook-summary | Summarize key points from Kubernetes runbooks |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Kubernetes Runbook: Kubernetes | Kubernetes troubleshooting guide: Kubernetes |
| Kubernetes Runbook: 0/1 nodes available: insufficient cpu, insufficient memory | Kubernetes troubleshooting guide: 0/1 nodes available: insufficient cpu, insufficient memory |
| Kubernetes Runbook: Cannot Reach Kubernetes Service | Kubernetes troubleshooting guide: Cannot Reach Kubernetes Service |
| Kubernetes Runbook: CreateContainerError | Kubernetes troubleshooting guide: CreateContainerError |
| Kubernetes Runbook: DNS Failures on Kubernetes | Kubernetes troubleshooting guide: DNS Failures on Kubernetes |
| Kubernetes Runbook: Failed Create Pod Sandbox | Kubernetes troubleshooting guide: Failed Create Pod Sandbox |
| Kubernetes Runbook: Pod In CrashLoopBackOff State | Kubernetes troubleshooting guide: Pod In CrashLoopBackOff State |
| Kubernetes Runbook: Pod In ImagePullBackOff State | Kubernetes troubleshooting guide: Pod In ImagePullBackOff State |
| Kubernetes Runbook: Pod In InvalidImageName State | Kubernetes troubleshooting guide: Pod In InvalidImageName State |
| Kubernetes Runbook: Pod In OutOfPods State | Kubernetes troubleshooting guide: Pod In OutOfPods State |
| Kubernetes Runbook: Pod Stuck in Pending State | Kubernetes troubleshooting guide: Pod Stuck in Pending State |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: fetching a runbook by topic, listing all topics, and searching by keyword. There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tools follow a consistent verb_noun pattern in snake_case (e.g., fetch-runbook, list-topics). The convention is uniform and predictable.
Three tools is well-scoped for a read-only Kubernetes runbook server. It provides essential operations (list, fetch, search) without unnecessary bloat.
The tool surface covers the core read operations for runbooks: listing topics, fetching by topic, and searching. No obvious gaps exist given the server's stated purpose.