Add the remote server only with OAuth support
Jan Desktop supports remote MCP servers using Streamable HTTP. Open Settings →
MCP Servers → Add, name the server Hombee Home MCP and enter the public
URL ending in /mcp.
Home MCP requires user OAuth in addition to the HTTP transport. Continue only if the installed Jan release starts a supported browser authorization flow for the server. If it only asks for a static header, do not paste a Hombee session, cookie or access token into Jan. Update Jan or choose a client with verified remote MCP OAuth support.
Running the model locally does not make Home MCP data local. Requests still reach Hombee, and the returned tools remain scoped to the signed-in user and installation.
Verify Home Assistant with a local model
Choose a model with dependable tool use and ask: “Through Hombee Home MCP, list Home Assistant areas and read-only capabilities. Do not change state.” Verify that Jan shows a real MCP call and require manual approval for consequential tools.
If the server is offline, confirm that its type is HTTP rather than a local
command and that the URL ends in /mcp. If the model answers without a tool
call, enable the MCP server for the conversation or use a model with stronger
tool-use support. Never treat a generated answer as proof of current home state.