Built-in MCP server 🛰️🤝🤖
HomeLab Monitor now ships a first-class, read-only MCP
server inside the same image — connect Claude (or any MCP client) to your homelab
and explore it with full dashboard parity. No extra container.
# the dashboard is on :9800; the MCP server is on :9810
claude mcp add --transport http homelab http://YOUR-HUB:9810/mcpThen ask things like "which host has a reboot pending and an OS upgrade — what's the
safe order?", "why is the GPU pinned, and which service is calling it?", or
"what's filling /backup?".
12 read-only tools
list_hosts, get_host, get_snapshot, get_containers, get_services,
get_memory (per-service/per-process RAM), get_gpu (util/VRAM/power + caller
attribution), get_ai_models, get_history (charted series),
get_events/get_alerts, and scan_disk (WizTree-style folder treemap).
Resources: homelab://metrics, homelab://health, homelab://changelog.
Details
- Runs alongside the dashboard via a small process supervisor; the dashboard is
unaffected if the MCP server restarts. Opt out withENABLE_MCP=0. - New AI agent (MCP) card in the Setup tab shows status, endpoint and a
copy-paste connect command. - Read-only by design — no write tools.
Docs → https://sikamikanikobg.github.io/homelab-monitor/mcp/
Upgrade: docker compose pull && docker compose up -d. Closes #70.