Mcp-homey

Developers
1

:robot: Claude AI + Homey Integration via MCP Protocol - Looking for Feedback!

Hey Homey community! :waving_hand:

I’ve been working on something exciting that I’d love to share and get your feedback on. I’ve created an MCP (Model Context Protocol) server that allows Claude AI to directly control your Homey devices through natural language conversations!

:rocket: What is this?

This integration lets you chat with Claude AI and control your entire Homey setup just by talking to it naturally:

  • “Turn on the kitchen lights at 75%”
  • “Set the thermostat to 22 degrees”
  • “Start my evening routine”
  • “What’s the temperature in the bedroom?”
  • “Show me my energy usage this month”

:sparkles: Features

:house: Complete Device Control (21 tools total):

  • Control lights, thermostats, sensors, and smart appliances
  • Zone-based control (“turn off all bedroom lights”)
  • Advanced light control (color, brightness, temperature)
  • Thermostat management
  • Flow/automation triggering

:bar_chart: Smart Analytics:

  • Historical device data and trends
  • Energy consumption monitoring
  • Real-time dashboard metrics
  • Usage pattern detection
  • Data export capabilities

:globe_showing_europe_africa: Cross-Platform:

  • Works on Windows, macOS, and Linux
  • Simple setup via Claude Desktop
  • Demo mode for testing without real devices

:hammer_and_wrench: How it works

The integration uses Homey’s local API and runs as an MCP server that connects to Claude Desktop. You configure it once, and then you can have natural conversations with Claude about your smart home.

Example conversation:

You: "What devices do I have in the living room?"
Claude: Shows all your living room devices with current status

You: "Turn on the living room lamp and set it to warm white"
Claude: Executes the command and confirms the action

You: "Show me yesterday's energy usage"
Claude: Displays detailed energy consumption analytics

:warning: Current Status & Feedback Needed

This is still experimental! While the core functionality works, I’m sure there are edge cases and improvements needed. I’d really appreciate feedback on:

  1. Device compatibility - Does it work with your specific Homey devices?
  2. API reliability - Any connection issues or timeouts?
  3. Feature requests - What would you like to see added?
  4. Bugs & issues - Anything that doesn’t work as expected?
  5. Documentation - Is the setup process clear enough?

:wrench: Setup Requirements

  • Homey Pro with local API enabled
  • Claude Desktop application
  • Python 3.11+ with uv package manager
  • Personal Access Token from my.homey.app (with all scopes!)

:clipboard: Repository

The code is available on GitHub: GitHub - maerestijnde/mcp-homey

Full documentation, installation guide, and Windows/macOS setup instructions are included in the README.

2 Likes
2

I see that the macOS/Linux shell script uses hardcoded paths to your home directory. You can replace /Users/sdemaere in the script with $HOME and it should work for others too.

Also, I would replace this:

export PATH="/Users/sdemaere/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"

With this:

export PATH="$HOME/.local/bin:$PATH"
2 Likes
3

should be fixed, thanks!

1 Like