- Home
- MCP servers
- Homey
Homey
- typescript
0
GitHub Stars
typescript
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"ndygen-mcp-server-homey": {
"command": "node",
"args": [
"/absolute/path/to/mcp-server-homey/build/index.js"
],
"env": {
"HOMEY_ID": "YOUR_HOMEY_ID",
"HOMEY_CLIENT_ID": "YOUR_CLIENT_ID",
"HOMEY_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
}
}
}
}This MCP Server lets AI agents, such as Claude, talk to your Homey home automation system to manage flows, devices, and zones. It enables natural language commands to batch rename, organize, enable/disable, trigger, and schedule flows, as well as inspect and control devices and zones from an AI agent.
How to use
Connect your MCP client to the Homey MCP Server to perform actions on flows, devices, and zones. You can ask an AI agent to list flows, rename or move them, enable or disable groups of flows, trigger a flow manually, or inspect devices and their capabilities. The server supports batch operations, making large-scale updates—such as renaming many flows to match a new naming convention—fast and auditable.
How to install
Prerequisites you must have before installing the MCP Server:
- Homey Pro with cloud access
- Homey Developer Account
- Node.js 18+
Install and configure the server locally with the following steps.
cd mcp-server-homey
npm install
Configure environment and run
Create and configure the environment file with your Homey credentials and Homey ID. The server reads these values at startup.
cp .env.example .env
Build and start in standalone mode
Build the server so it can be run locally for testing.
npm run build
Run the server for testing
Start the server in standalone mode to listen for MCP messages over stdio.
npm start
Claude Desktop Integration configuration
Configure the Claude Desktop integration to run the Homey MCP Server as a local stdio process. You can either run the server via a direct node invocation pointing to the built index or use the installed package.
{
"mcpServers": {
"homey": {
"command": "node",
"args": [
"/absolute/path/to/mcp-server-homey/build/index.js"
],
"env": {
"HOMEY_CLIENT_ID": "your_client_id",
"HOMEY_CLIENT_SECRET": "your_client_secret",
"HOMEY_ID": "your_homey_id"
}
}
}
}
Or use the installed package
If you have the package installed, you can reference it directly in Claude’s config.
{
"mcpServers": {
"homey": {
"command": "mcp-server-homey"
}
}
}
Available tools
list_flows
List all Homey flows with optional filtering by folder and enabled status.
get_flow
Retrieve detailed information about a specific flow by its ID.
update_flow
Update a flow’s name, enabled state, and destination folder.
list_flow_folders
Return the hierarchical structure of flow folders.
trigger_flow
Manually trigger a flow by its ID.
list_devices
List all devices with optional filtering by zone.
list_zones
List all Homey zones in hierarchical structure.