Home Assistant with Home MCP in Pi coding agent

Hombee Free

Understand the Pi integration

Pi intentionally keeps its core small and does not bundle an MCP client. This setup uses the third-party pi-mcp-adapter extension listed in the Pi package directory. Pi extensions execute code with the agent’s privileges, so review the package source and pin a version before installing it in a trusted setup.

Install and configure Home MCP

  1. Install the reviewed adapter with pi install npm:pi-mcp-adapter and restart Pi.
  2. Add a hombee entry to .mcp.json for the current project or to ~/.config/mcp/mcp.json for your user.
  3. Set url to the public Home MCP URL ending in /mcp and auth to oauth.
  4. Open /mcp, select hombee and complete Hombee authorization.
  5. Keep the default proxy mode while evaluating the connection. It lets Pi discover tools on demand instead of placing the whole catalog in context.
{
  "mcpServers": {
    "hombee": {
      "url": "https://your-public-home-mcp-url/mcp",
      "auth": "oauth"
    }
  }
}

The adapter stores OAuth credentials in the operating-system credential store. Do not replace this flow with a browser session or commit credentials with the project configuration.

Verify Home Assistant from Pi

Ask: “Use hombee to list Home Assistant rooms and read-only tool categories. Do not change state.” Inspect the selected tool and arguments before approval.

If the server is missing, confirm which configuration file /mcp detected. If authorization is required, run the adapter’s explicit authentication action. If discovered tools differ between users, compare Hombee account, installation and enabled modules rather than assuming the adapter exposes a fixed catalog.

Continue exploring