
MCP AI Bridge for Homey
io.github.weide43v5.0.0Updated Oct 9, 2026
Control a Homey Pro smart home: devices, flows, energy and more. Runs on the Homey itself.
Overview
AI-generated overview
Lets an assistant control a Homey Pro smart home, including devices, flows and energy data, through a remote endpoint.
- What it does
- This server exposes a Homey Pro smart home to an AI assistant, covering devices, flows, energy and more, according to the registry description. It runs on the Homey itself and is reached as a remote streamable HTTP endpoint at the user's Homey host. The manifest does not list individual tools, so the exact set of operations is not documented here.
- When to use it
- Worth adding when you want an assistant to read or act on your Homey Pro setup, such as checking devices, running or inspecting flows, or looking at energy information, without building your own integration.
- Requirements
- A Homey Pro reachable at your Homey host, and a client that connects to a remote streamable HTTP endpoint. Authentication is optional: either an Authorization header with a Bearer API key from the Security tab, or OAuth sign-in on a consent page for clients that support it.
Before you install
The server can control a smart home, so assistant actions may change device states or run flows. The Authorization header carries an API key from the Security tab; treat that key as a secret. The endpoint is hosted on your own Homey, so availability depends on that device being online.
Installation
In SourceWeft
- Open MCP AI Bridge for Homey in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"homey-mcp-ai-bridge": {
"type": "http",
"url": "https://{homey_host}/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v5.0.0LatestOct 9, 2026
