Add a remote context server
Zed describes MCP connections as context servers. Configure Hombee as a remote server so Zed uses the HTTP endpoint rather than trying to start a local process.
- Open Zed settings and the MCP or context server management view.
- Choose Add remote server.
- Name the connection Hombee Home MCP.
- Enter the public Home MCP URL ending in
/mcp. - Save the server. When Zed detects that authorization is required, complete the standard MCP OAuth flow in the browser.
- Return to Zed and check that the context server exposes tools.
Do not work around OAuth by adding a copied Hombee session to Zed settings. If you keep settings in version control, place the private Home MCP server in user settings instead.
Verify Home Assistant from Zed
Open the agent panel and ask:
From Hombee Home MCP, read the Home Assistant room list and summarize the available capabilities. Do not change any state.
Check that the proposed tool belongs to the Hombee context server and review its arguments. Keep confirmation enabled for actions that change devices, security modes or automations.
Zed-specific troubleshooting
- If Zed tries to execute a command, recreate the entry as a remote URL server.
- If OAuth does not start, remove any manual authorization header and reconnect so the standard discovery flow can run.
- If the server connects but the agent cannot use it, enable the Hombee context server for that conversation.
- If the tool list differs from another client, compare Hombee account and installation capabilities before treating it as a Zed problem.