Where the connection runs
Visual Studio Code exposes MCP servers to GitHub Copilot agent experiences. You
can configure a server for one workspace in .vscode/mcp.json or in your user
profile. Prefer user configuration for a private home connection unless a shared
workspace has an explicit reason to describe the server.
Add the Hombee server
- Open the MCP: Add Server command in Visual Studio Code.
- Select HTTP as the transport.
- Enter the public Hombee Home MCP URL ending in
/mcp. - Name the server Hombee Home MCP and choose user or workspace scope.
- Start the server from the MCP management view.
- Complete OAuth in the browser with the correct Hombee account.
- Open Copilot Chat in agent mode and inspect the available tools.
An equivalent workspace definition uses a server entry with type set to http
and url set to the Home MCP address. Do not add a static bearer token to a
committed .vscode/mcp.json file.
Verify Home Assistant tools in Copilot
Ask Copilot:
Use Hombee Home MCP to read the current Home Assistant installation summary. List available rooms and tool categories without changing state.
Use the tool picker or MCP management view to verify that the selected tools come from Hombee. Review every proposed state-changing call before approval, especially when it targets security, access, automations or multiple devices.
VS Code and Copilot troubleshooting
- If the server starts but tools do not appear, refresh discovery from the MCP management view and start a new agent conversation.
- If colleagues inherit a broken connection, remove account-specific values from workspace configuration and let each person authorize independently.
- If OAuth does not open, verify that the server was added as remote HTTP rather than as a local command.
- If Copilot selects an unrelated tool, disable other MCP servers temporarily and repeat a precise, read-only request naming Hombee Home MCP.