infra-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCKER_HOST | No | Docker socket path | /var/run/docker.sock |
| NVIDIA_SMI_PATH | No | Path to nvidia-smi binary | nvidia-smi |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_overviewA | One-shot system health check: CPU load averages, memory usage, swap, and uptime |
| gpu_statusA | NVIDIA GPU status: name, temperature, utilization, VRAM usage |
| gpu_processesA | List processes currently using NVIDIA GPU VRAM |
| disk_usageA | Disk usage per mount point (excludes tmpfs, devtmpfs, efivarfs) |
| io_pressureA | PSI (Pressure Stall Information) for CPU, memory, and I/O — shows if the system is under real stress |
| top_processesA | Top N processes sorted by CPU or memory usage |
| service_statusA | Check systemd service status (system or user unit) |
| memory_detailA | Full /proc/meminfo breakdown with human-readable sizes |
| list_containersB | List Docker containers with optional filters |
| inspect_containerC | Full inspect details for a Docker container |
| container_logsB | Tail logs from a Docker container |
| start_containerA | Start a stopped Docker container |
| stop_containerB | Stop a running Docker container with optional timeout |
| restart_containerC | Restart a Docker container |
| compose_statusA | Show Docker Compose projects with their containers grouped by project |
| list_imagesA | List Docker images with optional all filter |
| list_volumesA | List Docker volumes and warnings |
| list_networksA | List Docker networks with IPAM info |
| container_healthC | Show Docker container health check status |
| docker_statsA | Show one-shot Docker stats for running containers |
| prune_systemC | Show or perform Docker system prune summaries |
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 21 tools
Most tools have clearly distinct purposes: system monitoring tools target different metrics, and Docker tools separate list/inspect/logs/start/stop/restart. Minor overlap exists between list_containers and compose_status (both list containers but with different grouping) and between container_health and inspect_container (health info is a subset of inspect), but descriptions help differentiate them.
The naming is mixed: system and GPU tools use noun_noun patterns (system_overview, gpu_status, disk_usage), while Docker tools use verb_noun patterns (list_containers, start_container, restart_container). This inconsistency is mildly confusing, though the pattern is predictable within each subdomain, and all names are readable.
21 tools is on the higher end of the optimal range, but each tool covers a specific monitoring or Docker management function that justifies its presence. The count is appropriate for a server that spans both system health and container operations, without feeling bloated.
The server covers system monitoring and Docker container lifecycle well, but has notable gaps: no service management (only status), no Docker container create/remove, no image pull/remove, and no volume/network creation. Basic operations are covered, but full infrastructure management is incomplete.