HomeLab Monitor MCP Server

Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services). Exposed over MCP by the homelab monitor mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Your home lab grew into a couple of machines, a Pi, and a GPU that's mysteriously always busy — and lately it's running models too. HomeLab Monitor gives you one self-hosted page that answers the real questions: what's that GPU actually doing, which model is holding it, what's it costing you to run, which container is eating RAM, what's filling your disks, and is anything down — across every box over SSH: Linux, a Pi, even Windows. Readable from your phone over the VPN.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• WizTree — style disk treemaps**, network I/O with per-container top talkers, and a mini-htop for who's eating CPU and RAM
• Multi — machine over SSH** — paste one key per box; Linux, a Pi, even Windows. No agents, no installs. The GPU tab works per host too: a remote multi-GPU
• Variable — Default
• SAMPLE_INTERVAL — 10
• RETENTION_DAYS — 180
• PRESSURE_FREE_MB — 2048
• PORT — 9800
• MCP_PORT — 9810
• ENABLE_MCP — 1
• WATCH_CONTAINERS — —
• WATCH_SERVICES — —
• CHECK_UPDATES — true

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch HomeLab Monitor.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the homelab monitor mcp server does with a few real requests.

When to reach for it

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. HomeLab Monitor's toolset — WizTree, Multi, Variable and 10 more — is a fair guide to whether it matches your workflow. It is maintained by SikamikanikoBG; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.