homebutler
homebutler is an MCP server published by SangheeSon with verified support for the current MCP specification revision (2026-07-28). It is the first-party server from SangheeSon. Last verified 2026-09-15.
Does homebutler support the current MCP specification (2026-07-28)?
Yes. homebutler has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-09-15).
Is homebutler a first-party (official) MCP server?
Yes. homebutler is the first-party MCP server published by SangheeSon (last verified 2026-09-15).
How do I connect to homebutler?
homebutler is available via the package npm:homebutler, the official MCP Registry under io.github.Higangssh/homebutler, the source repository at https://github.com/Higangssh/homebutler. Authentication: none. Transports: stdio.
What tools does homebutler expose?
homebutler exposes 37 tools, including system_status, docker_restart, docker_logs, backup_create, backup_restore, wake (last verified 2026-09-15).
Does homebutler support MCP revision 2024-11-05?
Yes. homebutler supports MCP revision 2024-11-05 (checked 2026-09-15).
Does homebutler support MCP revision 2025-03-26?
Yes. homebutler supports MCP revision 2025-03-26 (checked 2026-09-15).
Does homebutler support MCP revision 2025-06-18?
Yes. homebutler supports MCP revision 2025-06-18 (checked 2026-09-15).
Does homebutler support MCP revision 2025-11-25?
Yes. homebutler supports MCP revision 2025-11-25 (checked 2026-09-15).
Which tools does homebutler expose?
37 tools verified.
system_statusdocker_restartdocker_logsbackup_createbackup_restorewakeproxmox_guestsinstall_app
homebutler is a single Go binary that inspects and manages a homelab: server
status, Docker containers, open ports, backups, and an optional Proxmox VE
cluster the operator already runs, exposed to AI agents through an MCP
server. It ships 37 tools, including system_status, docker_restart,
backup_create, backup_restore, and a family of proxmox_* tools for VM
and container operations. The npm package (homebutler) is a thin installer
around the Go binary; the MCP interface runs over stdio only, with no network
port opened, so the README states that only the parent AI process can reach
it.
The project is maintained by a single individual, SangheeSon (GitHub account Higangssh), whose ownership is confirmed by the GitHub API (account type User), the npm package's sole maintainer email, and the project's own site at homebutler.dev, which links back to the same GitHub account. homebutler does not front any named third-party home-automation vendor; it talks directly to infrastructure the operator already controls (Docker, SSH, Proxmox) and bundles install recipes for third-party self-hosted apps without wrapping any one of them as a product. That makes it a self-contained tool published by its own maker, so authority is first_party.
Vendor documentation (docs/mcp-server.md, "Protocol versions") states: "homebutler implements the MCP revisions 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05." That names the current spec revision plus four legacy ones, grounding spec_status as current. The repository has published two security advisories, both rated high: GHSA-v8mc-vpp8-jr4p (unauthenticated arbitrary file overwrite via a crafted manifest.json in restore, published 2026-08-26) and GHSA-9x86-gvgx-3cfh (symlink escape in restore --allow-bind, published 2026-08-30). Both concern the backup_restore tool exposed over MCP.
Which MCP spec revisions does homebutler support?
homebutler has 5 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2024-11-05 | Supported | Source | |
| MCP 2025-03-26 | Supported | Source | |
| MCP 2025-06-18 | Supported | Source | |
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Supported | Source |
How widely adopted is homebutler?
Ranked #198 in The MCP 500 with Adoption Index 51.02 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 381 | API · |
| GitHub stars | 282 | API · |
| GitHub forks | 19 | API · |
| Last push | 2026-09-15T14:41:28Z | API · |
| Repository archived | no | API · |
How was this verified, and what are the sources?
Verified · method: vendor-docs
· confidence 1.00 (High).
- Official MCP Registry record for io.github.Higangssh/homebutler, re-fetched 2026-09-15 by version - version 0.31.0, package npm homebutler 0.31.0 with stdio transport, status active, description "Inspect and manage a homelab over MCP - status, Docker, ports, backups - without shell access" - accessed
- Repository metadata, fetched 2026-09-15 - Higangssh/homebutler, MIT, 282 stars, 19 forks, last push 2026-09-14, not archived; owner is a GitHub User account (SangheeSon) - accessed
- Repository README, fetched 2026-09-15 - "No daemon required. No database. No always-on web service. Just one Go binary you can use from the terminal, scripts, a web dashboard, or AI tools"; interface table lists MCP as JSON-RPC over stdio - accessed
- Vendor documentation docs/mcp-server.md, fetched 2026-09-15, "Protocol versions" section - "homebutler implements the MCP revisions 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05"; also states "No network ports opened. MCP uses stdio (stdin/stdout) - only the parent AI process can communicate with homebutler" - accessed
- npm registry metadata for homebutler, fetched 2026-09-15 - dist-tags latest 0.31.0 matches the registry record exactly; sole maintainer "sanghee" <sonsanghee3@gmail.com>, same email as the GitHub account's public email; no @modelcontextprotocol/sdk dependency on the latest version - accessed
- Repository security advisories, fetched 2026-09-15 - two published, both high severity: GHSA-v8mc-vpp8-jr4p (unauthenticated arbitrary file overwrite via crafted manifest.json in restore, 2026-08-26) and GHSA-9x86-gvgx-3cfh (restore --allow-bind symlink escape, 2026-08-30) - accessed