Check authentication support first
Crush supports remote MCP connections over HTTP, but Home MCP also requires a compatible OAuth flow. Before adding the server, confirm that the installed Crush release can authorize an OAuth-protected remote MCP endpoint. Transport support alone is not enough.
In the Crush configuration, add a hombee entry under mcp, select the HTTP
transport and use the public Home MCP URL ending in /mcp. Keep the entry in
user configuration when possible. Start the client and complete its supported
browser authorization flow.
If the installed release only offers static headers, stop there. Do not copy a
Hombee browser session, access token or cookie into crush.json. Update Crush
or use a verified client with native MCP OAuth.
Limit permissions and verify Home Assistant
Crush supports MCP permission controls. Keep interactive approval enabled and do
not use an unrestricted mode for a server that can affect the physical home.
Begin with: “Through hombee, list Home Assistant areas and read-only tools. Do
not change state.”
If the server never reaches authorization, distinguish an OAuth compatibility problem from an HTTP connection failure. If discovery succeeds but a tool is missing, verify Hombee account and installation modules. A client must not invent or call a capability that Home MCP did not return for the current user.