ops-copilot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUDIT_DIR | No | Override directory for audit log files. Defaults to ./audit/ |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health check. Returns 'pong'. Read-only, no side effects. |
| list_containersA | READ-ONLY. List Docker containers as a compact text table. By default shows only running containers; pass all=true to include stopped ones. No side effects. |
| get_container_logsA | READ-ONLY. Fetch the last N lines of a container's logs. Resolve the container by id-prefix or exact name. No side effects. |
| restart_containerA | MUTATING: causes downtime. Two-phase confirm flow — call ONCE without confirmToken to preview and receive a single-use token, then call AGAIN with that confirmToken within 120s to actually restart. The token is bound to this exact container. |
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 4 tools
Each tool has a clearly distinct purpose: ping for health, list_containers for inventory, get_container_logs for log retrieval, and restart_container for a mutating operation. There is no overlap or ambiguity between them.
Tools use lowercase snake_case with a verb_noun pattern (list_containers, get_container_logs, restart_container). The exception is 'ping', which is a single verb but is a conventional health-check name and does not detract from overall consistency.
Four tools form a well-scoped set for a Docker operations copilot, covering health, listing, logs, and restart. The count is appropriate for the narrow domain and each tool earns its place.
The core monitoring and restart workflow is covered, but there are minor gaps such as no explicit start/stop container controls. Agents can work around this given the focus on restart and diagnostics.