What remains local
LM Studio can run the language model locally, but Home MCP remains a remote, authenticated Hombee service. A local model does not make home data local and does not bypass the Hombee account, its permissions or each tool’s safeguards.
Add Hombee to LM Studio
- Open the Program or integrations area in LM Studio.
- Open the MCP installation view and edit
mcp.json. - Add a remote server named Hombee Home MCP with the public URL ending in
/mcp. - Save the configuration and reload MCP integrations.
- If LM Studio starts a supported browser authorization flow, sign in with the Hombee account for the target installation.
- Confirm that the server is connected and inspect the discovered tools.
Remote authentication support can vary by LM Studio release. If the installed
version cannot complete the Home MCP OAuth flow, do not add a copied browser
session to mcp.json. Update LM Studio or use another verified MCP client.
Verify Home Assistant with a local model
Choose a model with reliable tool-use support and ask:
Use Hombee Home MCP to list Home Assistant rooms and read-only capabilities. Do not change anything.
Review the exact tool selection and arguments. Smaller local models may choose tools or fill parameters less reliably, so require manual approval for every state-changing Home MCP call and compare the result with the Hombee app.
LM Studio troubleshooting
- If the model answers from general knowledge, verify that MCP tools are enabled for the chat and explicitly name Hombee Home MCP.
- If the server configuration loads but authentication fails, verify remote OAuth support in the installed release rather than adding a static token.
- If the model repeatedly chooses the wrong tool, select a stronger tool-use model and keep calls read-only while testing.
- If tools differ from another client, verify Hombee account and installation modules; the local model does not control discovery.