Home Assistant MCP Server
mcpkey · packageio.github.jarahkon/hass-mcp-server · v1.0.6
MCP server for full Home Assistant control — dashboards, files, automations, add-ons, and more
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
#!/usr/bin/env bash # hass (io.github.jarahkon/hass-mcp-server), recipe baremetal (generated). # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-hass.service. set -euo pipefail export HOST=127.0.0.1 PORT=8101 exec npx -y supergateway@4 --stdio 'npx -y @jarahkon/[email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz [Unit] Description=MCP server hass (toolset my-agent), generated by Hub After=network-online.target Wants=network-online.target [Service] Type=simple User=mcp Group=mcp EnvironmentFile=/etc/mcp/my-agent.env Environment=HOME=/var/lib/mcp/hass WorkingDirectory=/var/lib/mcp/hass ExecStart=/opt/mcp/my-agent/bin/hass.sh Restart=on-failure RestartSec=5 NoNewPrivileges=true ProtectSystem=strict ProtectHome=true PrivateTmp=true ReadWritePaths=/var/lib/mcp/hass [Install] WantedBy=multi-user.target
generated from the record, not tested yet
docker run --rm -p 127.0.0.1:8101:8000 -e HA_URL -e HA_TOKEN -e HA_SSH_HOST -e HA_SSH_PORT -e HA_SSH_USER -e HA_SSH_KEY_PATH -e HA_SSH_PASSWORD node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y @jarahkon/[email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T12:47:54+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
hass:
image: node:22-alpine
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @jarahkon/[email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
ports:
- 127.0.0.1:8101:8000
volumes:
- npm-cache:/root/.npm
healthcheck:
test:
- CMD-SHELL
- wget -qO- http://127.0.0.1:8000/healthz || exit 1
interval: 30s
timeout: 5s
retries: 5
start_period: 2m
restart: unless-stopped
environment:
HA_URL: ${HA_URL}
HA_TOKEN: ${HA_TOKEN}
HA_SSH_HOST: ${HA_SSH_HOST}
HA_SSH_PORT: ${HA_SSH_PORT}
HA_SSH_USER: ${HA_SSH_USER}
HA_SSH_KEY_PATH: ${HA_SSH_KEY_PATH}
HA_SSH_PASSWORD: ${HA_SSH_PASSWORD}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T12:47:54+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: hass
namespace: mcp
labels: &id001
app: hass
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: hass
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: HA_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_URL
- name: HA_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_TOKEN
- name: HA_SSH_HOST
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_HOST
- name: HA_SSH_PORT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_PORT
- name: HA_SSH_USER
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_USER
- name: HA_SSH_KEY_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_KEY_PATH
- name: HA_SSH_PASSWORD
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_PASSWORD
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @jarahkon/[email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: hass
namespace: mcp
spec:
selector:
app: hass
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T12:47:54+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
hass:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: hass
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: HA_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_URL
- name: HA_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_TOKEN
- name: HA_SSH_HOST
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_HOST
- name: HA_SSH_PORT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_PORT
- name: HA_SSH_USER
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_USER
- name: HA_SSH_KEY_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_KEY_PATH
- name: HA_SSH_PASSWORD
valueFrom:
secretKeyRef:
name: mcp-credentials
key: HA_SSH_PASSWORD
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y @jarahkon/[email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: HA_URL, HA_TOKEN, HA_SSH_HOST, HA_SSH_PORT, HA_SSH_USER, HA_SSH_KEY_PATH, HA_SSH_PASSWORD. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsnpx -y @jarahkon/[email protected] # env: HA_URL, HA_TOKEN, HA_SSH_HOST, HA_SSH_PORT, HA_SSH_USER, HA_SSH_KEY_PATH, HA_SSH_PASSWORD
{
"mcpServers": {
"hass": {
"command": "npx",
"args": [
"-y",
"@jarahkon/[email protected]"
],
"env": {
"HA_URL": "${HA_URL}",
"HA_TOKEN": "${HA_TOKEN}",
"HA_SSH_HOST": "${HA_SSH_HOST}",
"HA_SSH_PORT": "${HA_SSH_PORT}",
"HA_SSH_USER": "${HA_SSH_USER}",
"HA_SSH_KEY_PATH": "${HA_SSH_KEY_PATH}",
"HA_SSH_PASSWORD": "${HA_SSH_PASSWORD}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add hass -e "HA_URL=${HA_URL}" -e "HA_TOKEN=${HA_TOKEN}" -e "HA_SSH_HOST=${HA_SSH_HOST}" -e "HA_SSH_PORT=${HA_SSH_PORT}" -e "HA_SSH_USER=${HA_SSH_USER}" -e "HA_SSH_KEY_PATH=${HA_SSH_KEY_PATH}" -e "HA_SSH_PASSWORD=${HA_SSH_PASSWORD}" -- npx -y @jarahkon/[email protected]
{
"mcpServers": {
"hass": {
"command": "npx",
"args": [
"-y",
"@jarahkon/[email protected]"
],
"env": {
"HA_URL": "${HA_URL}",
"HA_TOKEN": "${HA_TOKEN}",
"HA_SSH_HOST": "${HA_SSH_HOST}",
"HA_SSH_PORT": "${HA_SSH_PORT}",
"HA_SSH_USER": "${HA_SSH_USER}",
"HA_SSH_KEY_PATH": "${HA_SSH_KEY_PATH}",
"HA_SSH_PASSWORD": "${HA_SSH_PASSWORD}"
}
}
}
}
{
"servers": {
"hass": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@jarahkon/[email protected]"
],
"env": {
"HA_URL": "${HA_URL}",
"HA_TOKEN": "${HA_TOKEN}",
"HA_SSH_HOST": "${HA_SSH_HOST}",
"HA_SSH_PORT": "${HA_SSH_PORT}",
"HA_SSH_USER": "${HA_SSH_USER}",
"HA_SSH_KEY_PATH": "${HA_SSH_KEY_PATH}",
"HA_SSH_PASSWORD": "${HA_SSH_PASSWORD}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.jarahkon/hass-mcp-server
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.