Choose the configuration scope
Kiro CLI reads MCP configuration from .kiro/settings/mcp.json for a project or
~/.kiro/settings/mcp.json for the user. Use user scope for a private Home MCP
connection unless the shared project genuinely requires the server entry.
Add hombee as a remote server with the public URL ending in /mcp. Open the
MCP management view, start authentication for hombee and finish Hombee sign-in
in the browser. Kiro supports remote-server OAuth discovery; use /mcp auth
when the client asks for an explicit login and /mcp logout before handing the
machine to another person.
Do not commit credentials or browser session material. A project file may describe the server URL, but authorization belongs to the individual Hombee account.
Verify Home Assistant from Kiro
Ask: “Through Hombee Home MCP, list Home Assistant areas and read-only tools available to my account. Do not modify state.” Review the exact tool and arguments before approval, especially when an agent runs with broad workspace permissions.
If the browser does not open, inspect the MCP panel for an authorization action and verify the URL. If the server connects but no tools appear, reload MCP after sign-in and confirm installation access. Do not treat a successful OAuth result as proof that every operation is permitted; Home MCP matches the tool list to the current account and installation.