zima-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZIMA_HOST | Yes | Hostname or IP of the box | |
| ZIMA_USER | Yes | SSH user | |
| ZIMA_SSH_KEY | No | Path to SSH private key (optional) | |
| ZIMA_SSH_PORT | No | SSH port | 22 |
| ZIMA_SSH_TIMEOUT | No | Seconds before an SSH command times out | 20 |
| ZIMA_RESTART_ALLOWLIST | No | Comma-separated container names that may be restarted |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zima_loadA | Load average and uptime of the box. Quick check of whether it is busy. |
| zima_topB | Top processes by CPU. Use it to find what is pegging the CPU. |
| zima_docker_psA | List running Docker containers with status and image. |
| zima_docker_statsA | One snapshot of CPU and memory per container. Best tool for finding the culprit. |
| zima_diskB | Disk usage (df -h). |
| zima_container_logsB | Tail recent logs for one named container. |
| zima_restart_containerA | Restart one named container. Only containers in ZIMA_RESTART_ALLOWLIST are allowed. |
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 7 tools
Each tool targets a distinct host or container concern (load, CPU, disk, container listing, stats, logs, restart), and descriptions explicitly differentiate the overlapping-looking ones (e.g. docker_ps vs docker_stats, top vs docker_stats). Minor residual overlap between host CPU tools and container CPU tools, but selection is generally clear.
All tools share a zima_ prefix and consistent lowercase snake_case, so the set reads as a coherent family. The style is noun-oriented rather than strict verb_noun (load, top, disk, docker_ps), with only restart_container using a verb, but this is a minor deviation rather than confusion.
Seven tools is well-scoped for a host-plus-Docker monitoring server: one per core observation (load, CPU, disk, container list, container stats, logs) plus a single guarded mutation. Nothing feels redundant or missing at the count level.
Covers the main diagnostic surface: host load/CPU/disk, container listing/stats/logs, and a safe restart. Gaps include host memory/network metrics and start/stop operations (only restart exists), but an agent can work around these for typical troubleshooting.