Add Home MCP as a goose extension
goose implements extensions through MCP. Configure Hombee as a streamable_http
extension with the public Home MCP URL ending in /mcp.
extensions:
hombee:
type: streamable_http
name: hombee
display_name: Hombee Home MCP
enabled: true
uri: https://your-public-home-mcp-url/mcp
headers: {}
timeout: 300
You can also start an isolated test session with
goose session --with-streamable-http-extension <url>. Complete the browser
OAuth flow when goose requests authorization. Do not add copied session tokens
to headers.
goose can expose many extensions and may run in an autonomous permission mode.
Use available_tools to limit Hombee tools and require review for calls that
change Home Assistant state, security, automations or external systems.
Verify Home Assistant from goose
Start a fresh session and ask: “Using the Hombee extension, list available Home Assistant rooms and read-only capabilities. Do not perform actions.” Check that the response comes from a Home MCP tool call rather than model knowledge.
If the extension is unavailable, confirm the type is streamable_http, the
field is uri, and the URL ends in /mcp. If authorization cannot open on a
remote machine, configure goose’s documented OAuth callback port or forwarding
instead of weakening authentication. Different accounts can correctly discover
different tool lists.


