I maintain a small open-source tool called HomeLab Monitor — one dashboard for every box in my homelab: host vitals, containers, systemd services, GPU, and which AI model servers are loaded right now.
It's good at being a pair of human eyes. The next thing I want is to make it a source of context for an AI agent.
So the idea: give it an MCP server. Model Context Protocol is the thing that lets an agent like Claude call tools and read resources. If the monitor speaks MCP, an agent can connect and explore the whole fleet — "which container is leaking RAM?", "the GPU's been pinned for an hour, who's driving it?", "this host wants a reboot and an OS upgrade, what order is safe?" — and start helping with the maintenance instead of me squinting at graphs.
The fun part for whoever builds it: it's mostly a thin wrapper over a REST API that already exists. The monitor already serves clean, read-only JSON (/api/data, /api/fleet, /api/host_data/<name>, /metrics). MCP just adds the semantics — tools and resources with names an LLM can reason about instead of a raw blob. Read-only to start; any future write tool stays opt-in.
It's genuinely weekend-sized if you've wrapped an MCP server around an API before — and a great first one if you haven't and want to learn.
Repo: https://github.com/SikamikanikoBG/homelab-monitor
The idea + a suggested first PR: https://github.com/SikamikanikoBG/homelab-monitor/issues/70
If wiring this sounds fun, come say hi on the issue — I'll help scope the first commit.
Top comments (0)