A
licenseB
qualityD
maintenanceMCP server for full Home Assistant control, enabling AI agents to manage dashboards, automations, files, apps, entities, and more via REST API, WebSocket, and SSH.
66
182 npm
MIT
HomeLab MCP
by chip10
Integration with Docker for managing containers, including remote Docker hosts and allowed containers.
Integration with Home Assistant for home automation, allowing control and management of smart home devices.
Integration with Proxmox for managing VMs, with support for allowed VM IDs and write operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@HomeLab MCP what's the status of my Docker containers?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
HomeLab MCP v1.0
Integra Home Assistant, Frigate, Docker y Proxmox por STDIO.
Instalación
cd /Users/victortg/Projects
mv homelab-mcp homelab-mcp-backup
unzip ~/Downloads/homelab-mcp-v1.0.zip
mv homelab-mcp-v1.0 homelab-mcp
cd homelab-mcp
uv syncRelated MCP server: mcp-homelab
Configuración MCP
Comando:
/opt/homebrew/bin/uvArgumentos:
--directory
/Users/victortg/Projects/homelab-mcp
run
python
-m
homelab_mcp.serverCopia las variables de .env.example a la configuración del cliente MCP.
Escrituras
Requieren:
ENABLE_WRITES=trueRecurso en
DOCKER_ALLOWED_CONTAINERSoPVE_ALLOWED_VMIDSParámetro
confirmigual aWRITE_CONFIRMATION
Empieza con ENABLE_WRITES=false, prueba las lecturas y luego activa las acciones.
Docker remoto
Ejemplos:
DOCKER_HOST=unix:///var/run/docker.sock
DOCKER_HOST=ssh://root@192.168.3.17Verifica antes:
docker -H ssh://root@192.168.3.17 psSeguridad
No pegues tokens en chats. Revoca cualquier token previamente publicado.
Available Tools
26 toolsdocker_container_logsA
Obtiene las últimas líneas de logs de un contenedor.
Inputs: name (required), tail. Returns: object
docker_list_containersB
Lista contenedores Docker y su estado.
Inputs: all_containers. Returns: result
docker_restart_containerC
Reinicia un contenedor permitido.
Inputs: name (required), confirm (required), timeout. Returns: object
docker_start_containerC
Arranca un contenedor permitido.
Inputs: name (required), confirm (required). Returns: object
docker_stop_containerD
Detiene un contenedor permitido.
Inputs: name (required), confirm (required), timeout. Returns: object
frigate_checkA
Comprueba salud y versión de Frigate.
Inputs: no named parameters. Returns: object
frigate_eventsC
Consulta eventos recientes de Frigate.
Inputs: after, limit, before, labels, +1 more.
frigate_reviewC
Consulta elementos de Review de Frigate.
Inputs: after, limit, before, cameras, +2 more.
frigate_statsC
Obtiene métricas de cámaras, detectores y procesos.
Inputs: no named parameters.
ha_call_serviceC
Ejecuta un servicio de Home Assistant.
Inputs: domain (required), confirm (required), service (required), service_data (required).
ha_checkB
Comprueba conexión, versión y zona horaria de Home Assistant.
Inputs: no named parameters. Returns: object
ha_error_logC
Obtiene el error_log de la sesión actual.
Inputs: max_characters. Returns: object
ha_get_entityB
Obtiene el estado y atributos actuales de una entidad.
Inputs: entity_id (required). Returns: object
ha_run_scriptC
Ejecuta un script de Home Assistant.
Inputs: confirm (required), entity_id (required), variables (required).
ha_search_entitiesC
Busca entidades por entity_id o friendly_name.
Inputs: query (required), limit, domain. Returns: object
ha_set_climate_temperatureC
Establece la temperatura objetivo de una entidad climate.
Inputs: confirm (required), entity_id (required), temperature (required).
ha_trigger_automationC
Dispara una automatización.
Inputs: confirm (required), entity_id (required).
ha_turn_offD
Apaga una entidad.
Inputs: confirm (required), entity_id (required).
ha_turn_onC
Enciende una entidad.
Inputs: confirm (required), entity_id (required).
pve_guestsA
Lista QEMU y LXC de un nodo Proxmox.
Inputs: node (required). Returns: object
pve_guest_statusC
Obtiene el estado de una VM QEMU o un LXC.
Inputs: node (required), vmid (required), guest_type (required).
pve_nodesA
Lista nodos Proxmox y su estado.
Inputs: no named parameters.
pve_reboot_guestC
Reinicia una VM o LXC permitido.
Inputs: node (required), vmid (required), confirm (required), guest_type (required).
pve_shutdown_guestC
Solicita apagado limpio de una VM o LXC permitido.
Inputs: node (required), vmid (required), confirm (required), guest_type (required).
pve_start_guestC
Arranca una VM o LXC permitido.
Inputs: node (required), vmid (required), confirm (required), guest_type (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
C2.8/5.0
Scored across 26 tools
Disambiguation4/5
Tools are grouped into clear subsystems with distinct actions per resource, so an agent can generally tell them apart. The only minor overlap is ha_call_service versus ha_turn_on/ha_turn_off, but the descriptions clarify the direct vs generic path.
Naming Consistency4/5
Names consistently use lowercase snake_case with domain prefixes like pve_, ha_, frigate_, and docker_. Most follow a verb_noun pattern, but a few noun-only endpoints such as pve_nodes, frigate_stats, and ha_error_log are slight deviations.
Tool Count4/5
26 tools is above the typical well-scoped range, but the server covers four distinct subsystems: Proxmox, Home Assistant, Frigate, and Docker. Each area has a focused set of operational tools, so the count feels justified rather than bloated.
Completeness4/5
The tool surface covers the main operational workflows for all four domains: guest lifecycle, container control, Home Assistant state/service/automation, and Frigate monitoring. Some advanced operations like Docker inspect or Proxmox guest creation are absent, but core homelab management is well covered.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues
Related MCP Connectors
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants real-time access to your homelab infrastructure. It enables querying node status, managing Docker containers, controlling Proxmox VMs, and inspecting OPNsense firewall state through natural conversation.2MIT
- AlicenseAqualityCmaintenanceA self-hosted MCP server for Home Assistant that exposes full control over entity states, service calls, history, templates, and areas via local stdio, enabling AI assistants to manage your smart home.9112 npmMIT
- AlicenseNot gradedqualityCmaintenanceA single MCP server that gives an AI assistant comprehensive access to manage a homelab, including SSH, Docker, Proxmox, Synology, Cloudflare, and more, with 85 tools and a centralized configuration.MIT