x=hub

your toolset

    build deployment
    sign in

    Homey-Wan-Kenobi MCP

    mcpother
    io.github.Ringosystems/homey-wan-kenobi-mcp · v2.2.0
    deploy just this

    MCP server for Homey Pro: 60 tools for devices, flows, energy, and Z-Wave/Zigbee diagnostics.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    #!/usr/bin/env bash
# homey-wan-kenobi (io.github.Ringosystems/homey-wan-kenobi-mcp), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-homey-wan-kenobi.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-homey-wan-kenobi -p 127.0.0.1:${PORT}:8000 -e HOMEY_ADDRESS -e HOMEY_TOKEN docker.io/ringosystems/homey-wan-kenobi:2.2.0

[Unit]
Description=MCP server homey-wan-kenobi (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target

[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/homey-wan-kenobi
WorkingDirectory=/var/lib/mcp/homey-wan-kenobi
ExecStart=/opt/mcp/my-agent/bin/homey-wan-kenobi.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/homey-wan-kenobi

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    docker run --rm -p 127.0.0.1:8101:8000 -e HOMEY_ADDRESS -e HOMEY_TOKEN docker.io/ringosystems/homey-wan-kenobi:2.2.0
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-19T01:26:10+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:
  homey-wan-kenobi:
    image: docker.io/ringosystems/homey-wan-kenobi:2.2.0
    ports:
    - 127.0.0.1:8101:8000
    restart: unless-stopped
    x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
      HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
      instead.'
    environment:
      HOMEY_ADDRESS: ${HOMEY_ADDRESS}
      HOMEY_TOKEN: ${HOMEY_TOKEN}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-19T01:26:10+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: homey-wan-kenobi
  namespace: mcp
  labels: &id001
    app: homey-wan-kenobi
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: homey-wan-kenobi
        image: docker.io/ringosystems/homey-wan-kenobi:2.2.0
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: HOMEY_ADDRESS
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: HOMEY_ADDRESS
        - name: HOMEY_TOKEN
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: HOMEY_TOKEN
---
apiVersion: v1
kind: Service
metadata:
  name: homey-wan-kenobi
  namespace: mcp
spec:
  selector:
    app: homey-wan-kenobi
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-19T01:26:10+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:
  homey-wan-kenobi:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: homey-wan-kenobi
      image: docker.io/ringosystems/homey-wan-kenobi:2.2.0
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: HOMEY_ADDRESS
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: HOMEY_ADDRESS
      - name: HOMEY_TOKEN
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: HOMEY_TOKEN

# 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
    deploy to koyeb

    The form opens with CHANGE_ME for each value you supply: HOMEY_ADDRESS, HOMEY_TOKEN. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure
    deploy to azuretemplate

    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 needs
    docker run -i --rm -e HOMEY_ADDRESS -e HOMEY_TOKEN docker.io/ringosystems/homey-wan-kenobi:2.2.0
    {
  "mcpServers": {
    "homey-wan-kenobi": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HOMEY_ADDRESS",
        "-e",
        "HOMEY_TOKEN",
        "docker.io/ringosystems/homey-wan-kenobi:2.2.0"
      ],
      "env": {
        "HOMEY_ADDRESS": "${HOMEY_ADDRESS}",
        "HOMEY_TOKEN": "${HOMEY_TOKEN}"
      }
    }
  }
}
    #!/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 homey-wan-kenobi -e "HOMEY_ADDRESS=${HOMEY_ADDRESS}" -e "HOMEY_TOKEN=${HOMEY_TOKEN}" -- docker run -i --rm -e HOMEY_ADDRESS -e HOMEY_TOKEN docker.io/ringosystems/homey-wan-kenobi:2.2.0

    {
  "mcpServers": {
    "homey-wan-kenobi": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HOMEY_ADDRESS",
        "-e",
        "HOMEY_TOKEN",
        "docker.io/ringosystems/homey-wan-kenobi:2.2.0"
      ],
      "env": {
        "HOMEY_ADDRESS": "${HOMEY_ADDRESS}",
        "HOMEY_TOKEN": "${HOMEY_TOKEN}"
      }
    }
  }
}
    {
  "servers": {
    "homey-wan-kenobi": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HOMEY_ADDRESS",
        "-e",
        "HOMEY_TOKEN",
        "docker.io/ringosystems/homey-wan-kenobi:2.2.0"
      ],
      "env": {
        "HOMEY_ADDRESS": "${HOMEY_ADDRESS}",
        "HOMEY_TOKEN": "${HOMEY_TOKEN}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.Ringosystems/homey-wan-kenobi-mcp
    • 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.