Homey MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOMEY_IP | No | IP address of Homey Pro for local connection | |
| HOMEY_TOKEN | Yes | Your Homey Personal Access Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| homey_list_devicesA | List all devices on Homey with their current states. |
| homey_get_sensor_readingsA | Get current readings from all sensors (temperature, humidity, motion, etc.) across the home. |
| homey_get_deviceA | Get detailed information about a specific device by ID. |
| homey_find_devices_by_zoneA | List all devices in a specific zone (room or floor). |
| homey_control_lights_in_zoneB | Turn all lights in a specific zone on or off. |
| homey_set_capabilityA | Set a capability value on a device (e.g. turn on/off, dim, target_temperature). |
| homey_list_flowsA | List all standard flows on Homey. |
| homey_list_advanced_flowsB | List all Advanced Flows on Homey. |
| homey_run_flowB | Trigger a specific standard flow. |
| homey_run_advanced_flowB | Trigger a specific Advanced Flow. |
| homey_list_zonesA | List all zones (rooms/floors) and their hierarchy. |
| homey_get_energy_dataB | Get energy consumption logs for devices. |
| homey_get_flowB | Get detailed information about a specific flow. |
| homey_get_flow_foldersA | List the folder structure for flows. |
| homey_get_flow_cardsA | List available flow cards (triggers, conditions, actions) for devices or system. |
| homey_run_flow_card_actionC | Manually execute a specific flow card action. |
| homey_get_device_insightsA | Retrieve historical logs for any device capability over a period. |
| homey_get_device_flow_capabilitiesB | Identify which flow cards are applicable to a specific device. |
| homey_get_live_insightsC | Provides real-time data for specific device capabilities (Dashboard style). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Each tool targets a distinct resource/action (devices, sensors, zones, flows, energy, insights). Even similar tools like list_flows vs list_advanced_flows are clearly differentiated by type. No overlapping purposes that would cause misselection.
All tools follow the consistent 'homey_verb_noun' pattern with snake_case. Verbs like list, get, find, control, set, run are used predictably. The naming convention is uniform and easy to infer.
19 tools is slightly above the typical well-scoped range, but the broad scope of a smart home hub (devices, zones, flows, energy, insights) justifies the count. Each tool serves a distinct purpose, so it doesn't feel excessive.
The tool surface covers core home automation workflows: reading device/sensor state, controlling devices, managing/running flows, and accessing energy/insight data. Minor gaps exist (e.g., no create/update/delete for flows or zones, no bulk zone control beyond lights), but these are workable and typical for a control-oriented server.