Windsurf and Cascade terminology
Windsurf is the editor; Cascade is its agent interface. MCP servers configured in Windsurf become tools Cascade can propose in a conversation. Treat both names as part of the same client setup, not as separate Hombee connections.
Add Hombee Home MCP
- Open Windsurf settings and the Cascade MCP management view.
- Add a custom remote MCP server named Hombee Home MCP.
- Select Streamable HTTP when a transport choice is shown.
- Enter the public Home MCP URL ending in
/mcp. - Save the server, start authorization and sign in with the intended Hombee account in the browser.
- Return to Cascade and inspect the tools loaded from Hombee.
Keep the server private unless a reviewed team configuration is required. Never place a Hombee browser session or long-lived authorization value in a repository-level MCP configuration.
Verify Home Assistant from Cascade
Start a new Cascade conversation with:
Read the Home Assistant installation context through Hombee Home MCP. List rooms and available read-only capabilities, and do not change any device.
Confirm that Cascade proposes a Hombee tool and shows its arguments before execution. For later actions, keep approvals enabled and verify the room, device and desired state in the tool call.
Windsurf-specific troubleshooting
- If Cascade does not list Hombee tools, refresh the MCP server and begin a new conversation.
- If a team workspace overrides your server, inspect both local and shared MCP configuration for duplicate names.
- If the browser authorizes a different installation, disconnect and repeat authorization with the correct Hombee account.
- If only some Home Assistant actions appear, compare the installation modules and permissions; do not assume the MCP connection is incomplete.