Skip to main content
Post

Home Assistant MCP: Find What's Using Power Right Now

Quickchat has a step-by-step guide for building an assistant that reads your Home Assistant power sensors over MCP. The example, called Watt Window, answers "What's using the most power right now?" for a small desk with a workstation, a monitor and a lamp.

You start by picking three power sensors, or by creating demo template helpers set to 72 W, 28 W and 6 W. Then you add Home Assistant's Model Context Protocol integration and expose only the Device control tool set with Read-only turned on. In Quickchat, you connect the main /api/mcp URL with a long-lived access token in the Authorization header. Enable only the homeassistant__GetLiveContext tool. The guide also keeps the Agent private while you test it, by turning off widget and chat page access.

The answer should name a device and its wattage, compare it with the other two, and say so when the source can't tell how old a reading is. The guide has you check the reply against the same readings in Home Assistant. It also has you make a reading unavailable to confirm the assistant leaves the missing value missing. A starter kit includes the demo sensor YAML, the full Main Prompt, connection settings and test questions. They're reference files, not an automatic Agent import.

A few conditions apply. You need a Home Assistant install you control and a Quickchat account with credits. Hosted Quickchat needs an authenticated, internet-reachable HTTPS endpoint, so localhost and homeassistant.local won't work. The token inherits its user's permissions, so the read-only limit applies to the MCP endpoint and not to Home Assistant's other APIs. The guide says its example ran against an isolated Home Assistant server, and your hosted setup still needs its own discovery and read check.

Loading replies