ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPS_MCP_TOOLS_HOME | No | Path to the directory containing the tool repositories (container-autopsy, death-noticer, git-sins). Defaults to the parent directory of the server script. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| container_autopsyA | Diagnose WHY a Docker container died, not just THAT it died. Collects exit code, OOM state, restart count, uptime and last log lines, then returns a markdown autopsy report with the cause of death and the exact fix. Works on running containers too. |
| container_obituaryA | Write a one-off obituary for a dead Docker container: who it was, how long it lived, the cause of death (deterministic rules) and its final words (last log lines). Returns markdown. |
| git_sinsA | The confession booth for a git repository. Analyzes the history read-only (3 AM commits, 'wip' messages, mega-commits, TODO graveyards, zombie branches...) and returns a markdown confession with evidence, penance and a 0-100 Sin Score. |
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 3 tools
container_autopsy and container_obituary substantially overlap—both diagnose why a container died, examine logs, and output a markdown report. An agent would struggle to reliably choose between them despite the slight difference in depth and tone. git_sins is the only clearly distinct tool.
All three tools follow a consistent lowercase_snake_case pattern with a domain prefix and a thematic noun: container_autopsy, container_obituary, git_sins. The pattern is predictable and readable, though the playful nouns deviate slightly from conventional verb_noun naming.
Three tools is on the thin side for a server named 'ops-mcp', but the set is tightly focused on diagnostics and forensics. It feels more like a themed utility collection than an operational coverage layer, which is acceptable but not rich.
The scope is narrow—container death investigation and git history analysis—and within that scope the tools cover their stated purposes. However, the two container tools are redundant rather than complementary, and there is no action-oriented tooling (e.g., restart, cleanup) that an 'ops' user might expect.