What it does
Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).
- Connects Runs on your computer
- Account or key No key needed · 1 setting to fill in (HOMELAB_MONITOR_URL)
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 29/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 41/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
HOMELAB_MONITOR_URLBase URL of the running HomeLab Monitor dashboard (e.g. http://YOUR-HUB:9800)
Descriptions are as written by the maker.
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
Checking the commands · copy buttons appear once they pass
Quit Claude and open it again
Try it
Use HomeLab Monitor and tell me what you can do for me, then show me one thing✓ If Claude says it is using HomeLab Monitor or shows a HomeLab Monitor tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
MCP_TRANSPORTTransport mode: stdio (default for this package entry) or http · default stdio
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect HomeLab Monitor yet
HomeLab Monitor runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect HomeLab Monitor
- 1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- 1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time)
- 1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time)
- 1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time)
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
HOMELAB_MONITOR_URLBase URL of the running HomeLab Monitor dashboard (e.g. http://YOUR-HUB:9800)
Descriptions are as written by the maker.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
Checking the commands · copy buttons appear once they pass
Type /mcp in Claude Code
You should see HomeLab Monitor listed as connected
Try it
Use HomeLab Monitor and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using HomeLab Monitor or shows a HomeLab Monitor tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
MCP_TRANSPORTTransport mode: stdio (default for this package entry) or http · default stdio
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time)
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
HOMELAB_MONITOR_URLBase URL of the running HomeLab Monitor dashboard (e.g. http://YOUR-HUB:9800)
Descriptions are as written by the maker.
Click this button to open Cursor
Checking the commands · copy buttons appear once they pass
Fill in your key
In the HomeLab Monitor settings, HOMELAB_MONITOR_URL is empty; add your key and save
Open the AI chat in Cursor in Agent mode
Try it
Use HomeLab Monitor and tell me what you can do for me, then show me one thing✓ If Cursor says it is using HomeLab Monitor or shows a HomeLab Monitor tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
MCP_TRANSPORTTransport mode: stdio (default for this package entry) or http · default stdio
Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
1 setting(s) to fill in (HOMELAB_MONITOR_URL) · Install Docker on your computer first (one time)
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 1 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
HOMELAB_MONITOR_URLBase URL of the running HomeLab Monitor dashboard (e.g. http://YOUR-HUB:9800)
Descriptions are as written by the maker.
Click this button to open VS Code
Checking the commands · copy buttons appear once they pass
Fill in your key
In the HomeLab Monitor settings, HOMELAB_MONITOR_URL is empty; add your key and save
Open the AI chat in VS Code in Agent mode
Try it
Use HomeLab Monitor and tell me what you can do for me, then show me one thing✓ If VS Code says it is using HomeLab Monitor or shows a HomeLab Monitor tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
MCP_TRANSPORTTransport mode: stdio (default for this package entry) or http · default stdio
Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
Checking the commands · copy buttons appear once they pass
Claude Desktop (claude_desktop_config.json)
Checking the commands · copy buttons appear once they pass
Cursor (~/.cursor/mcp.json)
Checking the commands · copy buttons appear once they pass
VS Code (mcp.json)
Checking the commands · copy buttons appear once they pass
Values you fill in
HOMELAB_MONITOR_URLrequired envBase URL of the running HomeLab Monitor dashboard (e.g. http://YOUR-HUB:9800)MCP_TRANSPORTenvTransport mode: stdio (default for this package entry) or http
Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- Not on npm/PyPI
- Connection
- Runs on your computer
- Transport
- stdio
- Latest versioni
- 0.14.2
- Categoryi
- Developer tools
- Published to registryi
- Jun 9, 2026
- Code last changedi
- Nov 20, 2026
- Maker
- SikamikanikoBG
- Packages
oci: docker.io/sikamikaniko123/homelab-monitor:0.14.2- Website
- sikamikanikobg.github.io
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 21, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account SikamikanikoBG, which owns the repo
- ✓ Pass
Still maintained
Code last changed yesterday
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
Not checked: only npm and PyPI packages with a version can be checked
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/sikamikanikobg-homelab-monitor)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 98% of the other 6702 servers in this category
- Published to the registry more recently than 13% of the other 6702 servers in this category
- Basic checks equal to or better than 99% of the other 6702 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is HomeLab Monitor safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed yesterday, and the latest version (0.14.2) reached the registry 5 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one HomeLab Monitor | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
HomeLab Monitor
Ask your homelab. One self-hosted page for every box and GPU you run — and an AI agent that reads all of it, answers in plain words, and fixes things only when you say so. It runs on the models already in your lab. No cloud, nothing to install on your machines.
Real answer, real fleet: one click on the Overview, a local model on the lab's own GPUs, about 45 seconds (sped up here). Host names are anonymised.
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 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. And when you'd rather not click through tabs, just ask.
Get started
# Grab the compose file and go. No GPU required — the GPU panels just light up when one's present.
curl -fsSLO https://raw.githubusercontent.com/SikamikanikoBG/homelab-monitor/main/docker-compose.yml docker compose up -d
Open http:// :9800 and you're done. The AI agent is already there: the Overview walks you through turning it on in about a minute. Full options (from source, GPU toolkit, Windows/WSL2) → Install docs.
🆕 What's new — every release is written up in full, with the reasoning behind it: latest release · changelog. The dashboard also shows you the notes once, in-app, after it updates itself.
Ask your homelab — an AI agent that knows your lab
It answers from what the dashboard actually measures. Ask from the Ask your lab card on the Overview, the floating Ask button on any page (it knows which page and host you're on), or the Agent tab. It reads your lab with the same tools the MCP server has, starts from the fleet overview and drills down only when it has to. The answer comes back as text and tables, never a wall of JSON. Every answer says what it checked ("Checked 4 machines · 2 look-ups · 46 s") and offers follow-ups. Ask in English, Bulgarian or anything else; it replies in your language.
| A real answer — the whole fleet in one table, then what needs you. | Nothing runs until you approve. The exact command is one click away. |
Your models, your rules. It finds the model servers already on your network — Ollama, vLLM, llama.cpp, LM Studio, LocalAI — and tests them while you watch, or takes your own key for OpenAI, Anthropic, Gemini, Groq, Mistral, OpenRouter and others. Keys never leave the hub.
You decide what it may do. Each machine is *Look only*, *Ask me first* or *Handle the small stuff*. Actions come from a fixed catalogue — restart or stop a container, restart a service, prune dangling images and build cache, shrink the journal, unload or delete an Ollama model — with no shell anywhere. The server checks the policy when the agent proposes an action and again when it runs. The monitor's own container and whatever serves the model are always off-limits.
Routines that run while you sleep. Ten ready-made ones — disk-space watch, GPU health, container health, Docker cleanup, model housekeeping, update and cost reports, backup freshness and more — or your own prompt, on a schedule. Each one can report, propose actions or act within your policy. Reports go to your alert channels, and proposals wait for you under Approvals.
Every step on the record. Activity shows what each run read, what the policy decided and why, and who approved it. You can export it as JSON or CSV, and every action is also written to docker logs.
Off until you turn it on, and only ever behind the dashboard login → AI agent docs.
What you get
One page, every box, the questions you actually have. The classics are all here — and a whole AI cockpit builds on top of them.
A front page for your lab — and a wall screen. The Overview opens with a Launchpad: the apps you actually open, as tiles with their real logos, pinned straight from a container row with the address already filled in, grouped and dragged into the order you want. Pins live on the hub, not in one browser — pin it on the laptop and it's there on the phone and on the wall. The whole board fits the screen: it measures its own overrun after every paint and gives ground in order — trimming lists, tightening the fleet rail, folding pins behind a +N more — rather than clipping a card in half or running past the fold. Verified from 4K down to 1366×768. And ⛶ Display (or /?display=1, all a dedicated kiosk box needs) drops every scrap of chrome and fills the monitor: you choose which panels the wall shows, and on Chromium-based browsers it opens full-screen on whichever screen you point it at.
Your GPU, demystified — and the same tab on every box. A card pinned at "100% util" can still be throttling, memory-bandwidth-bound, or quietly drooping its clocks. The GPU tab decodes nvidia-smi's throttle reasons, and shows memory-bandwidth util, core/mem clocks, power-vs-limit, p-state — and fan speed — for *every* machine in the fleet, not just the one running the container. Multi-GPU boxes get one panel per card on a shared scale per metric, so a taller temperature line really is a hotter card; thermal-throttle windows are shaded right on the sparkline. You can see which card a service is sitting on (a 3×3090 box shows a model's 63 GB split 22.5 / 22.1 / 18.8 across the cards, not one pooled number), what each service cost in energy, and get alerted when a card throttles, overheats or loses a fan — sustained, per card, with per-host thresholds, because a box running a deliberately lowered power limit is *supposed* to sit at its cap. And it's no longer NVIDIA-only: AMD GPUs are read on Linux straight from the kernel's amdgpu interface (no ROCm), and AMD and Intel GPUs on Windows hosts — so your card shows up with its name, utilisation and VRAM, no vendor tools required. Anything a driver won't report says so, instead of drawing a confident zero.
What it costs — down to the process. Power becomes money: per machine, then per component (GPU measured via nvidia-smi, CPU/DRAM via RAPL), then per process, container or model — click any row to see what it drew and what it cost over any window. Day & night tariffs (Economy 7, Heures Creuses, …), or just pick your country for a sensible estimate. Every watt is measured or a baseline you set; wall power is never guessed. And a busy-hours heatmap turns months of samples into one picture of *when* your lab costs you money — a 7×24 day-of-week × hour grid that shows which hour of the week is priciest at a glance.
Your training runs, priced. Push a run from Jupyter, Colab or Kaggle with a one-file client (or mirror it from MLflow), and it comes back with the loss curve *and* the GPU energy the box drew over the run window, on the same timeline. That window figure is the whole card's draw, not a per-run measurement — GPUs do not meter per process. Create, name, expire and revoke API keys yourself.
"Will it fit?" — measured, not guessed. The Benchmark Lab loads each of your local ollama models and sweeps a ladder of context sizes on your actual cards, recording generation & prompt tokens/sec, load time, how much spilled from VRAM into system RAM, and the largest context that still fits fully in VRAM — the cap worth setting. Pick which GPU(s) to test (via a throwaway pinned ollama container — your main one is never touched), overlay stored runs to compare cards, and every run comes back with the energy it burned and what it cost. Results are stored: benchmark once, re-run only when something changes.
And the rest of the lab, the way it always was:
- Containers, honestly — health plus RAM and VRAM in separate columns (real resident RAM, not page cache), and click one to tail its logs in a side drawer. Every box in the fleet gets the same controls — logs, start/stop/restart, restart policy, pin — over the same SSH connection the probe already uses, and the whole tab works on a phone.
- systemd services — local or remote, your own units highlighted, failures first.
- WizTree-style disk treemaps — on any box in the fleet. Click into the folders filling a disk on the hub *or* on any Linux host you've added; a remote is scanned over the same SSH connection everything else uses, so there's still nothing to install on it. Plus network I/O with per-container top talkers and a mini-htop for who's eating CPU and RAM.
- It moves like a live dashboard. Utilisation, RAM, temperature and p