Home Assistant with Home MCP in Gemini CLI

Hombee Free

Configure the remote server

Gemini CLI stores MCP servers in its settings. Use user settings for a private home connection. Use project settings only when the repository intentionally documents the shared server definition.

  1. Open Gemini CLI settings, normally in ~/.gemini/settings.json for the user.
  2. Add an mcpServers entry named hombee.
  3. Set httpUrl to the public Hombee Home MCP URL ending in /mcp.
  4. Start Gemini CLI and run the MCP authentication command for the hombee server.
  5. Complete OAuth in the browser with the Hombee account for the intended installation.
  6. Use the MCP status command or menu to confirm that Hombee is connected and tools were discovered.

Do not add copied cookies, session tokens or authorization headers to the settings file. Keep personal MCP settings out of repositories and backups that are shared with other users.

Verify Home Assistant in the terminal

Ask Gemini CLI:

Use the hombee MCP server to list Home Assistant rooms and available read-only tool categories. Do not modify the installation.

Inspect the proposed tool name and arguments. Gemini CLI can discover many MCP servers, so naming hombee in the request helps avoid selecting an unrelated tool. Require confirmation for state-changing calls.

Gemini CLI troubleshooting

  • If the server is configured but unauthenticated, run the MCP authentication flow for that exact server name.
  • If httpUrl is ignored, verify that the server was not accidentally configured as a local command transport.
  • If discovery changes after a Hombee update, restart the CLI session and check status again.
  • If no Home Assistant tool matches the task, verify installation capabilities in Hombee instead of broadening permissions in the client.

Continue exploring