Configure Cline for a remote server
Cline runs inside Visual Studio Code but maintains its own MCP server settings. Do not assume that a server configured for GitHub Copilot is automatically available to Cline.
- Open Cline and select the MCP servers view.
- Choose the option to edit or add an MCP server.
- Create a remote Streamable HTTP server named Hombee Home MCP.
- Enter the public Home MCP URL ending in
/mcp. - Save and enable the server, then complete browser authorization if Cline starts the standard OAuth flow.
- Confirm that Cline lists Hombee tools before starting a task.
Keep the configuration at user scope when it contains a private home endpoint. Do not paste cookies or a Hombee session into custom headers. If your installed Cline version cannot complete authorization for a remote MCP server, do not replace OAuth with an unmanaged token.
Verify Home Assistant with Cline
Start with:
Use Hombee Home MCP to read the Home Assistant room and capability summary. Do not execute any state-changing tool.
Cline normally asks before invoking tools. Read the server name, tool name and arguments in the approval panel. Keep automatic approval disabled for home actions until you have reviewed the installation, arguments and consequences.
Cline-specific troubleshooting
- If Cline cannot see a server configured elsewhere in VS Code, add it in Cline’s own MCP settings.
- If a JSON configuration is rejected, use the editor generated by your installed Cline version because transport field names can change.
- If authorization is unsupported in that version, update Cline or use another verified remote MCP client; do not store a browser session as a header.
- If tools appear but a capability is missing, verify Hombee permissions and modules for the selected installation.