DevOps & SRE 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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_incident_scenariosA | Search 1,449+ real-world production incident scenarios across Kubernetes, AWS, Terraform, Linux, SRE, and CI/CD by symptoms, error codes (e.g. 137, 143, 502), or keywords. |
| get_scenario_runbookA | Retrieve the complete step-by-step diagnostic runbook, CLI commands, root cause analysis, and production mistakes to avoid for a specific incident scenario ID or slug. |
| decode_errorA | Decode an exit code, Kubernetes pod status, HTTP gateway error, or common Docker/ECS/AWS/Terraform/TLS/DNS error message (e.g. "137", "CrashLoopBackOff", "502", "Error acquiring the state lock"). Returns what it means, likely causes, diagnostic commands, fixes, and related incident scenarios. Offline and read-only. |
| get_interview_elevator_pitchA | Retrieve a senior DevOps/SRE candidate elevator pitch structured in the STAR framework (Situation, Task, Action, Result) with quantifiable production metrics. |
| generate_k8s_manifestA | Generate production-hardened, linted Kubernetes YAML manifests (Deployment, Service, HPA, PDB) with non-root securityContext, probes, and resource requests/limits. |
| get_devops_cheat_sheetA | Instant terminal lookup for dense command references and mental models: "ansible", "kubectl", "subnetting" (CIDR magic number), or "terraform". |
| get_architectural_blueprintC | Retrieve battle-tested cloud architecture blueprints authored by Naveed Ahmed: "aws-zero-downtime-migration", "reduce-aws-costs", "terraform-multi-account-saas", or "agentic-sdlc". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage-kubernetes-pod | Guided interactive incident triage for a failing or crashing Kubernetes pod (CrashLoopBackOff, OOMKilled 137, Pending, Probe failures). |
| mock-devops-interview | Simulates a senior DevOps/SRE architectural interview drill using real-world scenarios from Naveed Ahmed's scenario handbook. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| DevOps Incident Scenarios Catalog Summary | Summary of 1,449+ real-world incident scenarios grouped by technical domain. |
| Curated Kubernetes Production Platform Toolkit | Battle-tested open-source Kubernetes stack: Karpenter, Cilium, ArgoCD, OpenTelemetry, Trivy. |
TDQS
Scored across 7 tools
Most tools target clearly different resources: scenario search, runbook retrieval, error decoding, manifest generation, cheat sheets, blueprints, and interview pitch. The main ambiguity is between search_incident_scenarios and decode_error, since both can be invoked for a specific error code, though their descriptions distinguish broad symptom search from focused error interpretation.
All tool names use consistent snake_case verb_noun phrasing: search_, get_, decode_, generate_. The verbs are clear and predictable, with get_ appropriately used for multiple retrieval-oriented tools.
Seven tools is well-scoped for a DevOps/SRE reference and assistance server. Each tool has a distinct role and the set is neither too thin nor bloated.
The surface covers incident lookup, runbooks, error decoding, Kubernetes manifest generation, cheat sheets, architecture blueprints, and even interview prep. It lacks live operational actions and deeper infrastructure lifecycle tools, but as a DevOps/SRE knowledge assistant the coverage is strong.