Homey-Wan-Kenobi-MCP
Provides tools for Zigbee mesh network diagnostics, including controller health, node status, and issue remediation.
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., "@Homey-Wan-Kenobi-MCP turn on the living room lights"
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.
Homey-Wan-Kenobi MCP
MCP server for controlling Homey Pro smart home systems through the Model Context Protocol.
The name nods to Obi-Wan Kenobi, your home's only hope for natural-language control.
60 tools and 3 knowledge prompts for device control, flow authoring, automation, monitoring, troubleshooting, network diagnostics, and self-hosted deployment.
Why Homey-Wan-Kenobi
Athom ships an official Homey MCP Server: a cloud-brokered remote connector you add to a paid Claude or ChatGPT plan and sign into with your Homey account. It covers device status and control, renaming and moving devices, creating, updating and starting Flows and Advanced Flows, and setting Moods.
This server differs in two ways. It is self-hosted, so you run it yourself over stdio or streamable-HTTP with no third-party broker and no paid AI-plan requirement. And it adds operational depth for power users that is not part of the official server's described capabilities.
The table reflects Athom's publicly described capabilities as of June 2026. Athom does not publish a formal tool list, so the right-hand gaps are inferred from their documentation, not stated by Athom.
Capability | Official Homey MCP ( | Homey-Wan-Kenobi |
Hosting | Cloud-brokered remote connector | Self-hosted, stdio or HTTP, no broker |
Access | Paid Claude/ChatGPT connector plan | Any MCP client, no plan requirement |
Devices, zones, control, rename, move | Yes | Yes |
Flow and Advanced Flow authoring | Yes | Yes |
Moods | Yes | Yes |
Flow-card schema discovery (build flows from scratch) | Not described | Yes |
Energy: live power and day/week/month/year reports | Not described | Yes |
Insights: historical sensor and meter data | Not described | Yes |
Z-Wave and Zigbee mesh diagnostics with remediations | Not described | Yes |
App memory and usage analysis (removal candidates) | Not described | Yes |
Infrastructure ops: backups, reboot, updates, memory, storage | Not described | Yes |
Raw Homey Web API passthrough | Not described | Yes |
Listed in the public MCP Registry | No | Yes |
The depth, in practice
Network diagnostics that the official server does not describe.
diagnose_zwave_networkanddiagnose_zigbee_networkread controller health, grade each node by last-seen age (battery-sleep aware), group transmit failures, correlate them with unavailable devices, and return severity-ranked remediations.get_zwave_logexposes the raw network log.Energy and Insights analysis. Live power by zone and device, day/week/month/year energy reports, and timestamped historical sensor and meter data, so the model can answer "what is using power right now" or "how has the bedroom temperature trended this week".
App memory and usage analysis.
analyze_app_usagecross-references every app against RAM, device counts and flow references to flag safe removal candidates and estimate savings. Read-only and advisory.Build automations from scratch. A flow-card discovery engine (
list_flow_cards,get_flow_card) returns each card's full argument schema, and full standard and Advanced Flow CRUD (including delete) lets an AI author and tear down the whole cards graph by UUID.Infrastructure operations from one interface. Backups, reboot, update checks, memory and storage usage, drivers, LED ring, session and location info.
A future-proof escape hatch.
homey_api_callreaches any Homey Web API endpoint directly, so new firmware features work without waiting for a tool update.
It runs on a hardened, non-root node:22-alpine image whose every build and release is gated on a Trivy scan, and it is published to Docker Hub, GHCR and the public MCP Registry. See the tool reference below for the full list.
When the official server is the better fit
This server is local-first and self-hosted, which is both its strength and its trade-off. The official Homey MCP is the easier choice when you want:
Zero setup and managed hosting. Add one URL and sign in with your Homey account. There is no container to run, expose, or maintain, and there is a one-click ChatGPT app.
Secure remote access from anywhere. Athom brokers the connection through its cloud, so it works away from home without exposing anything on your LAN. This server's HTTP mode is intended for a trusted local network; remote use is your own VPN or authenticated reverse proxy.
Every Homey model. The official endpoint reaches Homey Cloud, Pro, Pro mini and Self-Hosted Server, including cloud-only setups that have no local API. This server targets a Homey reachable over its local API or your Athom token, so it is happiest with a Homey Pro.
First-party support. It is maintained by Athom, kept in step with firmware, and officially tested with Claude and the ChatGPT app. This project is independent and best-effort.
The two are complementary. Many people use the official connector for quick remote control and this server for the deep local diagnostics, energy analysis, and infrastructure work. Athom does not publish a formal tool list, so the official server may also include capabilities not reflected above.
Related MCP server: homekit-cli
Quick Start
git clone https://github.com/Ringosystems/Homey-Wan-Kenobi-MCP.git
cd Homey-Wan-Kenobi-MCP
npm install
npm run buildAuthenticate with your Homey:
npx homey login
npx homey selectAdd to your MCP client config (Kiro, Claude Desktop, Cline, etc.):
{
"mcpServers": {
"homey": {
"command": "node",
"args": ["/path/to/Homey-Wan-Kenobi-MCP/dist/index.js"]
}
}
}Authentication
The server supports two authentication methods:
Homey CLI (recommended) runs npx homey login and npx homey select. The server reads the stored OAuth token from ~/.athom-cli/settings.json automatically.
Local API Key is created at my.homey.app. Set environment variables:
export HOMEY_ADDRESS=http://192.168.1.x
export HOMEY_TOKEN=your-api-keyThe local API key method is the recommended choice when running self-hosted in a container, since it does not depend on a mounted CLI settings file.
Self-Hosted (Docker / HTTP)
The image is published at ringosystems/homey-wan-kenobi (mirrored to ghcr.io/ringosystems/homey-wan-kenobi), and the server is listed in the MCP Registry as io.github.Ringosystems/homey-wan-kenobi-mcp. It is built on node:22-alpine, runs as a non-root user, and ships no baked-in secrets. See SECURITY.md for the audit details.
It defaults to the stdio transport so an MCP client can launch it directly, and exposes a long-lived streamable-HTTP service (via supergateway at /mcp, health at /healthz) when you set MCP_TRANSPORT=streamable-http.
Fastest: one command (prebuilt image)
No clone or build. Pull two things and start it:
curl -fsSLO https://raw.githubusercontent.com/Ringosystems/Homey-Wan-Kenobi-MCP/main/docker-compose.deploy.yml
printf 'HOMEY_ADDRESS=http://192.168.1.x\nHOMEY_TOKEN=your-local-api-key\n' > .env
docker compose -f docker-compose.deploy.yml up -dThe service is then at http://<host>:8000/mcp (health at /healthz). On Unraid, add the template by URL instead: Docker, Add Container, paste https://raw.githubusercontent.com/Ringosystems/Homey-Wan-Kenobi-MCP/main/deploy/unraid/homey-wan-kenobi.xml into the Template field. The image is multi-arch, so it runs on x86 and ARM (Apple Silicon, Raspberry Pi) hosts.
The
/mcpendpoint has no built-in authentication. Keep it on a trusted LAN or behind a reverse proxy that adds TLS and auth.
Run as an MCP client (stdio)
docker run -i --rm \
-e HOMEY_ADDRESS=http://192.168.1.x \
-e HOMEY_TOKEN=your-local-api-key \
ringosystems/homey-wan-kenobi:latestRun as an HTTP service
docker run -d -p 8000:8000 \
-e MCP_TRANSPORT=streamable-http \
-e HOMEY_ADDRESS=http://192.168.1.x \
-e HOMEY_TOKEN=your-local-api-key \
--restart unless-stopped \
ringosystems/homey-wan-kenobi:latestDocker Compose
Supply your Homey credentials via a .env file next to docker-compose.yml:
cat > .env <<'EOF'
HOMEY_ADDRESS=http://192.168.1.x
HOMEY_TOKEN=your-local-api-key
EOF
# Pull the published image, or add --build to build locally instead
docker compose up -dThe provided docker-compose.yml references the published image (with build: . as a local-build fallback) and applies container hardening (read-only root filesystem, dropped Linux capabilities, no-new-privileges, and memory/PID limits):
services:
homey-wan-kenobi:
image: ringosystems/homey-wan-kenobi:latest
build: .
container_name: homey-wan-kenobi
ports:
- "8000:8000"
environment:
MCP_TRANSPORT: streamable-http
HOMEY_ADDRESS: "${HOMEY_ADDRESS:-http://192.168.1.x}"
HOMEY_TOKEN: "${HOMEY_TOKEN:-}"
restart: unless-stopped
read_only: true
tmpfs:
- /tmp
security_opt:
- no-new-privileges:true
cap_drop:
- ALL
mem_limit: 256m
pids_limit: 128
healthcheck:
test: ["CMD", "node", "-e", "fetch('http://localhost:8000/healthz').then(r=>process.exit(r.ok?0:1)).catch(()=>process.exit(1))"]
interval: 30s
timeout: 5s
retries: 3
start_period: 20sBuild locally
docker build -t ringosystems/homey-wan-kenobi .
docker run -d -p 8000:8000 \
-e MCP_TRANSPORT=streamable-http \
-e HOMEY_ADDRESS=http://192.168.1.x \
-e HOMEY_TOKEN=your-local-api-key \
--restart unless-stopped \
ringosystems/homey-wan-kenobiConnecting a client
Point an MCP client at the streamable-HTTP endpoint:
{
"mcpServers": {
"homey": {
"type": "streamable-http",
"url": "http://your-host:8000/mcp"
}
}
}Check health with curl http://your-host:8000/healthz.
Tools
Devices
Tool | Description |
| List devices with live capability values, filter by zone or class |
| Get full device details and all capability values by ID |
| Search devices by name, class, or capability |
| Control a device (onoff, dim, target_temperature, volume_set, etc.) |
Device & Zone Management
Tool | Description |
| Rename a device |
| Move a device to a different zone (room) |
| Create a new zone, optionally nested under a parent |
Zones
Tool | Description |
| List all zones (rooms/areas) with their hierarchy |
Flows
Tool | Description |
| List simple and advanced flows with enabled/broken status |
| Run a flow immediately |
| Enable or disable a flow |
Flow Authoring
Tool | Description |
| Get a standard WHEN/AND/THEN flow definition by ID |
| Create a standard flow from trigger/conditions/actions |
| Update fields of a standard flow |
| Permanently delete a standard flow |
| Get an Advanced Flow definition (cards, args, connections) |
| Create an Advanced Flow from a cards graph |
| Update an Advanced Flow (replaces the cards graph) |
| Permanently delete an Advanced Flow |
Flow Card Discovery
Tool | Description |
| List trigger/condition/action cards, filtered by substring |
| Get one flow card's full definition and argument schema |
Logic & Apps
Tool | Description |
| List logic variables with current values |
| Set a logic variable value |
| List installed apps with version, status, and origin |
| Restart a Homey app |
| Enable or disable an app |
| Uninstall an app and remove its devices |
Insights & Energy
Tool | Description |
| List available insight logs |
| Get historical sensor/meter data over a time range |
| Live power consumption by zone and device |
| Energy report for day/week/month/year |
Weather, Presence & Location
Tool | Description |
| Current weather at Homey's location |
| Hourly weather forecast |
| Home/away and awake/asleep status for all users |
| Set your own presence or sleep state |
| Homey's configured geographic location |
Alarms & Moods
Tool | Description |
| List all alarms and timers |
| Create or update an alarm |
| Delete an alarm |
| List moods (scenes) per zone |
| Activate a mood in a zone |
Notifications
Tool | Description |
| List the 50 most recent notifications |
| Send a notification to the Homey timeline |
Network Diagnostics
Tool | Description |
| Zigbee mesh health, per-node last-seen, issues and remediations |
| Z-Wave health, transmit failures, unavailable nodes, remediations |
| Raw recent Z-Wave network log for troubleshooting |
App Usage Analysis
Tool | Description |
| Cross-reference apps against RAM, devices, and flow references to flag removal candidates (advisory, read-only) |
System & Infrastructure
Tool | Description |
| System info (version, wifi, hostname, hardware) |
| List all available device drivers |
| Backup config and last backup time |
| Schedule a new backup |
| LED ring screensaver options and current setting |
| Set the LED ring screensaver |
| Check for system updates and update settings |
| Current API session info (user, role, scopes) |
| Reboot the Homey Pro |
| Memory usage by app and component |
| Storage usage breakdown |
| Set the Homey system name |
Advanced
Tool | Description |
| Raw escape hatch to call any Homey Web API endpoint directly |
Prompts
Built-in knowledge prompts accessible via the MCP prompts API:
Prompt | Description |
| Zone architecture, device naming, protocol tips, energy management, security |
| Diagnosing offline devices, Z-Wave/Zigbee issues, flow debugging, performance |
| Automation patterns, naming conventions, anti-patterns to avoid |
Development
npm run dev # Run with tsx (no build step)
npm run build # Compile TypeScript
npm run lint # ESLint
npm run typecheck # TypeScript strict check
npm start # Run compiled versionTech Stack
TypeScript + Node.js (>=20)
homey-api v3, the official Homey Web API client
@modelcontextprotocol/sdk v1.29, MCP server (
registerToolwithToolAnnotations)zod for parameter validation
supergateway for the self-hosted streamable-HTTP transport
Security
The dependency tree, base image, and container configuration are audited with Trivy and npm audit. The published image runs as a non-root user on node:22-alpine with no baked-in secrets, and the production dependencies ship with 0 high or critical advisories. See SECURITY.md for the full audit, accepted residual risks, and how to reproduce the scans.
License
Release process, one-time setup, and Unraid Community Applications submission are documented in PUBLISHING.md; notable changes in CHANGELOG.md.
Available Tools
60 toolsanalyze_app_usageAnalyze App Usage & MemoryARead-only
Cross-references installed apps against RAM usage (from the memory report), how many devices each provides, and whether each app is referenced by any flow (full flow definitions are scanned, not just metadata). Flags removal candidates (apps with 0 devices and no flow references, largest RAM first), reports potential RAM savings, and groups possible duplicate/overlapping app categories (e.g. multiple MQTT apps). Read-only and advisory; it does NOT uninstall anything. Caveat: a few apps run background logic (schedules, exports, tokens) without devices or flow cards, so verify before removing.
Inputs: no named parameters.
create_advanced_flowCreate Advanced FlowAIdempotent
Create a new Advanced Flow. Provide a name and a 'cards' object keyed by UUID; each card has type (trigger/condition/action/note/start/delay/all/any), id (flow card id), optional args, x/y coordinates, and outputSuccess/outputError arrays linking to other card UUIDs. Returns the new flow id and broken status (broken=false means all cards resolved).
Inputs: name (required), cards (required), folder, enabled.
create_backupCreate BackupAIdempotent
Schedule a new backup of the Homey configuration. Backup runs in the background.
Inputs: no named parameters.
create_flowCreate Standard FlowAIdempotent
Create a standard WHEN/AND/THEN Flow. Provide a name and a 'flow' object containing trigger (card object) and optional conditions[]/actions[] arrays. Use get_flow on a similar flow to learn the exact card shape.
Inputs: flow (required), name (required).
create_notificationSend NotificationAIdempotent
Send a notification to the Homey timeline. Visible in the Homey app for all household members.
Inputs: excerpt (required).
create_zoneCreate ZoneAIdempotent
Create a new zone (room/area). Optionally nest it under a parent zone.
Inputs: name (required), parent.
delete_advanced_flowDelete Advanced FlowADestructive
Permanently delete an Advanced Flow by ID. Cannot be undone.
Inputs: id (required).
delete_alarmDelete AlarmADestructive
Permanently delete an alarm. Use list_alarms to find the alarm ID.
Inputs: id (required).
delete_flowDelete Standard FlowBDestructive
Permanently delete a standard Flow by ID. Cannot be undone.
Inputs: id (required).
diagnose_zigbee_networkDiagnose Zigbee NetworkARead-only
Read the Zigbee mesh state and report health: controller status, node count, per-node last-seen age, and detected issues with recommended remediations. Note: battery Zigbee devices sleep, so a stale last-seen on a battery node can be normal.
Inputs: no named parameters.
diagnose_zwave_networkDiagnose Z-Wave NetworkARead-only
Read the Z-Wave controller state plus recent network log and report health: controller readiness/version, transmit failures grouped by node, currently-unavailable devices, and detected issues with recommended remediations.
Inputs: no named parameters.
enable_appEnable/Disable AppAIdempotent
Enable or disable a Homey app. Disabled apps won't run and their devices become unavailable.
Inputs: id (required), enabled (required).
get_advanced_flowGet Advanced FlowARead-only
Get the full definition of an Advanced Flow by ID, including all cards (triggers/logic/actions) with their args, coordinates and outputSuccess/outputError connections. Use before update_advanced_flow to see the current structure.
Inputs: id (required).
get_backup_statusBackup StatusARead-only
Get backup configuration and last successful backup timestamp.
Inputs: no named parameters.
get_deviceGet Device DetailsARead-only
Get detailed information about a specific device by ID, including all capability values, settings, and availability status. Use list_devices or search_devices first to find the device ID.
Inputs: id (required).
get_energy_liveLive Energy ReportARead-only
Get real-time power consumption broken down by zone and device. Returns watts (W) currently being consumed. Useful for answering 'what is using power right now?'
Inputs: no named parameters.
get_energy_reportEnergy ReportARead-only
Get energy consumption report for a specific period. Returns kWh consumed per device. Useful for 'how much energy did I use today/this week/this month?'
Inputs: period (required), date.
get_flowGet Standard FlowARead-only
Get the full definition of a standard (WHEN/AND/THEN) Flow by ID, including its trigger, conditions and actions cards.
Inputs: id (required).
get_flow_cardGet Flow CardARead-only
Get the full definition of one flow card (by type + id), including its arguments (names, types, dropdown values, ranges). Use this to learn exactly what args a card needs when building a flow.
Inputs: id (required), type (required).
get_insight_entriesGet Insight HistoryARead-only
Get historical data points for an insight log. Returns timestamped values (e.g. temperature readings over time). Use list_insights first to find the log ID.
Inputs: id (required), resolution.
get_ledringLED Ring StatusARead-only
Get LED ring screensaver options and current setting.
Inputs: no named parameters.
get_locationGet LocationARead-only
Get Homey's configured geographic location (address and GPS coordinates). Used for sunrise/sunset calculations and weather.
Inputs: no named parameters.
get_memory_infoMemory UsageARead-only
Get Homey memory usage breakdown by app and system component. Useful for identifying memory-hungry apps.
Inputs: no named parameters.
get_presenceGet Presence StatusARead-only
Get home/away and awake/asleep status for all household members. Useful for 'is anyone home?' or 'who is home?'
Inputs: no named parameters.
get_sessionSession InfoARead-only
Get current API session details including authenticated user, role, and permission scopes.
Inputs: no named parameters.
get_storage_infoStorage UsageARead-only
Get Homey storage usage breakdown. Shows how much disk space is used by apps, insights, and system.
Inputs: no named parameters.
get_system_infoSystem InformationARead-only
Get Homey system information including software version, hostname, Wi-Fi network, and hardware details.
Inputs: no named parameters.
get_updatesCheck UpdatesARead-only
Check for available Homey system updates and current update settings (channel, auto-update).
Inputs: no named parameters.
get_weatherCurrent WeatherARead-only
Get current weather conditions at Homey's location. Returns temperature, humidity, pressure, wind, and weather state (e.g. 'clear sky', 'overcast clouds').
Inputs: no named parameters.
get_weather_hourlyHourly Weather ForecastARead-only
Get hourly weather forecast at Homey's location. Returns temperature and weather conditions for upcoming hours.
Inputs: no named parameters.
get_zwave_logZ-Wave LogARead-only
Get recent Z-Wave network log entries. Shows transmit failures, routing issues, and network events. Essential for diagnosing Z-Wave device connectivity problems.
Inputs: no named parameters.
homey_api_callRaw Homey API CallA
Advanced escape hatch: call any Homey Web API endpoint directly. method is GET/POST/PUT/DELETE; path is the API path (e.g. /manager/zwave/state); body is an optional JSON object. Use to reach endpoints not yet wrapped by a dedicated tool, including new firmware capabilities. Prefer the dedicated tools when one exists.
Inputs: path (required), method (required), body.
list_alarmsList AlarmsARead-only
List all alarms and timers with their schedule and repetition days.
Inputs: no named parameters.
list_appsList Installed AppsARead-only
List all installed Homey apps with version, enabled status, and origin (appstore or devkit). Apps provide device drivers, flow cards, and integrations.
Inputs: no named parameters.
list_devicesList DevicesARead-only
List all Homey devices with current capability values. Returns device ID, name, class, zone, availability, capabilities, and live sensor/state values. Use 'zone' to filter by room name (partial match) or 'class' to filter by device type (light, sensor, thermostat, speaker, lock, socket, etc).
Inputs: zone, class.
list_driversList DriversARead-only
List all available device drivers (protocol integrations). Useful for troubleshooting — shows which drivers are ready.
Inputs: no named parameters.
list_flow_cardsList Flow CardsARead-only
List available flow cards of a given type (trigger/condition/action). There are hundreds, so filter by a substring matched against the card id/title/uri (e.g. a device UUID to find that device's cards, or 'windowcoverings', 'dim', 'button'). Returns id + title. Use get_flow_card for full args.
Inputs: type (required), limit, filter.
list_flowsList FlowsARead-only
List all automation flows (simple and advanced). Returns flow ID, name, enabled/broken status, and type. Flows are Homey's automations with WHEN/AND/THEN logic.
Inputs: no named parameters.
list_insightsList Insight LogsARead-only
List all available insight logs (sensor history, energy meters, etc). Returns log ID, title, data type, and units. Use the log ID with get_insight_entries to retrieve historical data.
Inputs: no named parameters.
list_moodsList MoodsARead-only
List all moods (scenes/presets) per zone. Moods save device states that can be activated together (e.g. 'Movie Mode' dims lights and closes blinds).
Inputs: no named parameters.
list_notificationsList NotificationsARead-only
List the 50 most recent Homey notifications (app updates, alerts, system messages). Sorted newest first.
Inputs: no named parameters.
list_variablesList Logic VariablesARead-only
List all logic variables with their current values. Logic variables store state (boolean, number, string) that can be used in flow conditions and actions.
Inputs: no named parameters.
list_zonesList ZonesARead-only
List all zones (rooms/areas) in the home with their hierarchy. Returns zone ID, name, parent zone, and icon. Zones are organized in a tree: Home → Floors → Rooms.
Inputs: no named parameters.
move_device_to_zoneMove Device to ZoneAIdempotent
Move a device to a different zone (room). Use list_zones for the zone ID and list_devices for the device ID.
Inputs: id (required), zoneId (required).
reboot_homeyReboot HomeyADestructiveIdempotent
Reboot the Homey Pro. Takes 2-3 minutes to come back online. Use this to resolve stale devices or Z-Wave/Zigbee mesh issues after firmware updates.
Inputs: no named parameters.
rename_deviceRename DeviceAIdempotent
Rename a device. Use list_devices to find the device ID.
Inputs: id (required), name (required).
restart_appRestart AppAIdempotent
Restart a Homey app. Useful when devices from that app are unresponsive. Use list_apps to find the app ID (e.g. 'com.fibaro').
Inputs: id (required).
search_devicesSearch DevicesARead-only
Search devices by name, device class, or capability name. Returns matching devices with their current values. Useful for finding devices when you don't know the exact ID — e.g. search 'temperature' to find all temperature sensors, or 'kitchen' to find devices with kitchen in the name.
Inputs: query (required).
set_alarmCreate/Update AlarmAIdempotent
Create a new alarm or update an existing one. Specify time in HH:MM format and optionally which days to repeat.
Inputs: name (required), time (required), id, enabled, +1 more.
set_device_capabilityControl DeviceAIdempotent
Control a device by setting a capability value. Common capabilities: 'onoff' (boolean — turn on/off), 'dim' (number 0-1 — brightness), 'target_temperature' (number — thermostat setpoint), 'volume_set' (number 0-1). Use get_device first to see available capabilities and their current values.
Inputs: value (required), deviceId (required), capability (required).
set_flow_enabledEnable/Disable FlowAIdempotent
Enable or disable a flow automation. Disabled flows won't trigger. Use list_flows to find the flow ID.
Inputs: id (required), enabled (required).
set_ledringSet LED RingAIdempotent
Set the LED ring screensaver animation. Use get_ledring to see available options (e.g. 'spectrum', 'off').
Inputs: screensaverId (required).
set_moodActivate MoodAIdempotent
Activate a mood (scene) in a zone. This sets all devices in the mood to their saved states.
Inputs: moodId (required), zoneId (required).
set_presenceSet PresenceAIdempotent
Set your own presence (home/away) or sleep state (awake/asleep). This affects presence-based automations.
Inputs: asleep, present.
set_system_nameSet System NameAIdempotent
Set the Homey system name (visible in network discovery and the Homey app).
Inputs: name (required).
set_variableSet Logic VariableAIdempotent
Set the value of a logic variable. The value type must match the variable type (boolean, number, or string).
Inputs: id (required), value (required).
trigger_flowTrigger FlowAIdempotent
Trigger (run) a flow immediately by its ID. Tries simple flow first, then advanced flow. Use list_flows to find the flow ID.
Inputs: id (required).
uninstall_appUninstall AppADestructive
Permanently uninstall a Homey app and remove all its devices. This cannot be undone.
Inputs: id (required).
update_advanced_flowUpdate Advanced FlowAIdempotent
Update an existing Advanced Flow. Pass only the fields to change (name, enabled, and/or the full cards map). Replacing cards replaces the entire flow graph, so fetch with get_advanced_flow first and send the complete cards object. Returns broken status.
Inputs: id (required), name, cards, enabled.
update_flowUpdate Standard FlowAIdempotent
Update a standard Flow. Pass the flow id and a 'flow' object with only the fields to change (name, trigger, conditions, actions, enabled).
Inputs: id (required), flow (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 60 tools
Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. For example, create_advanced_flow and create_flow target different flow types, while analyze_app_usage is advisory and separate from list_apps. No two tools overlap in function.
Most tool names follow a verb_noun pattern (e.g., list_devices, create_backup, set_device_capability). A few outliers like 'analyze_app_usage' and 'homey_api_call' break the pattern but are still readable. Overall, the naming is mostly consistent and predictable.
With 60 tools, the count is high and exceeds the 'too many' threshold from the calibration. While the domain is broad, the number may overwhelm agents and increase navigation difficulty. A more focused set could improve coherence.
The tool surface covers all major aspects of Homey management: flow CRUD, device control, energy monitoring, network diagnostics, system administration, and more. There are no obvious gaps; even advanced operations like Zigbee diagnosis and API escape hatches are included.
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for full Home Assistant control, enabling AI agents to manage dashboards, automations, files, apps, entities, and more via REST API, WebSocket, and SSH.66151 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for inspecting and controlling Apple HomeKit accessories, scenes, automations, and more via the HomeClaw app, enabling natural language interaction with your smart home.7 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Homebridge that enables AI assistants to control smart home accessories, manage plugins, edit configuration, and monitor the Homebridge server.22221 npm11MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to control and query smart home devices through Homey Pro via an HTTP-based MCP server.2MIT