Index / Homelab

HomeLab Monitor (built-in MCP)

access level: read-only✔ Source-reviewed Oct 2026

We read this project's source code and tool definitions (Oct 2026). This is a code review, not a live test against real systems. Re-check after upgrades.
Repositoryhttps://github.com/SikamikanikoBG/homelab-monitor
CategoryHomelab
Systems touchedHomelab hosts: CPU/RAM/disk, Docker containers, systemd services, GPUs and local AI model servers (Ollama/vLLM/llama.cpp), energy costs, history and alerts
Access (as described)read-only (MCP); dashboard controls write by default
License / priceMIT / free
GitHub stars236 (checked Oct 2026)
Read tools20 read tools: hosts, containers, systemd services, GPU and process use, per-process RAM, AI model servers and models, costs, benchmarks, disk treemaps, history, alerts
Write / delete / exec toolsNone over MCP. Dashboard/agent: container and service start/stop/restart, Docker cleanup, journal shrink, model unload, one-click self-update (controls and self-update ON by default)
Read-only modeMCP is read-only by design (ENABLE_MCP=0 turns it off). Use docker-compose.readonly.yml or ENABLE_CONTROLS=0 + ALLOW_SELF_UPDATE=0 for pure monitoring
Safety notesThe MCP has no auth and listens on 0.0.0.0:9810 with no Host allowlist by default — set MCP_ALLOWED_HOSTS and keep it on LAN/VPN only. The container runs with host PID, a read-write Docker socket and D-Bus, so the dashboard itself is effectively root on the host; dashboard login is off until you set a password.
Verifiedyes (README + docker-compose review 2026-11-14)
NotesSingle-container homelab dashboard with a read-only MCP server (20 tools) on :9810/mcp. v0.38 (2026-11-08/09) added an optional built-in AI agent with per-host Off/Passive/Active modes and per-action Deny/Ask/Allow (default Deny). Added 2026-11-14.

📬 SysAdmin Agents

The SysAdmin Agents newsletter: new MCP servers, agent skills and safety notes for sysadmins. One email a week.