Check resource alerts for CPU, memory, and disk usage against configured thresholds

Create a Docker compose backup archive for all services or one service

Verify a backup by booting an app in an isolated Docker environment and checking that it responds

List existing backup archives in the configured backup directory

Restore Docker volumes from a backup archive. Destructive: confirm intent before calling.

Check the config file this server is running on: which file was used, which rule selected it, what was read from each section, and anything wrong or silently ignored

Summarize a Docker container's image, state, restart policy, ports, mounts, networks, and health. Environment variable values are never included

List Docker containers with their status, image, and ports

Get logs from a Docker container

Restart a Docker container by name

Get resource usage statistics (CPU, memory, network, block I/O) for all running Docker containers

Stop a Docker container by name

List the processes running inside a Docker container, read from the host. Read-only: no exec, no TTY

Run a read-only diagnosis for resource pressure, stopped containers, public ports, backup hygiene, notifications, and report baseline readiness

Install a self-hosted app via docker compose. Pre-checks docker, ports, and duplicates automatically.

List available self-hosted apps that can be installed

Stop an installed app and delete all data including containers, config, and volumes.

Check the status of an installed app

Stop an installed app and remove its containers. Data is preserved.

Export server inventory/topology as a Mermaid diagram locally, or JSON locally/remotely

Collect server inventory/topology including system status, Docker containers, app ports, and system ports

Scan the local network to discover devices (IP, MAC, hostname)

List open network ports with associated process information

List the top processes by CPU or memory, with a total count and any zombies broken out separately

Reboot one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID

Gracefully shut down one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID

Start one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID

List Proxmox QEMU and LXC guests, optionally filtered by node, status, or type

Get detailed Proxmox node status

Render the pinned install command for one Proxmox VE Community Script. Never fetches or runs it; the caller reviews and runs it themselves on the Proxmox host

List the curated Proxmox VE Community Scripts catalog (community-scripts/ProxmoxVE)

Get Proxmox VE version, cluster status, and resources

Inspect one asynchronous Proxmox task by node and opaque UPID

Get the 50 most recent Proxmox tasks for a node

Generate a butler-style health report with snapshot comparison, warnings, notable changes, and suggested actions

Get system status including CPU, memory, disk usage, and uptime

Send a Wake-on-LAN magic packet to wake a machine

Run a one-shot restart check on watched targets and report restarts detected since the last check. Only docker targets can be inspected this way; systemd and pm2 targets are reported as skipped rather than assumed healthy

List recorded restart incidents, newest first. Captured logs are excluded unless include_logs is set, because every incident carries a hundred lines of output twice over

List the targets being watched, with their kind and what the last check recorded