Decide between project and global configuration
Cursor can read MCP servers from a project .cursor/mcp.json file or from the
global MCP settings. Home control is personal and installation-specific, so a
global private configuration is usually safer than committing the server to a
repository. Never commit credentials or authorization headers.
Configure Hombee Home MCP
- Open Cursor settings and the MCP section.
- Add a remote Streamable HTTP server named Hombee Home MCP.
- Enter the public Home MCP URL ending in
/mcp. - Start the OAuth flow from Cursor and finish signing in in the browser.
- Return to Cursor and verify that the server is connected and tools are listed.
If you use mcp.json, keep the URL in the server definition and let Cursor own
the authorization flow. A minimal definition identifies the Hombee server and
its remote URL. It does not contain a copied Hombee session.
Test Home Assistant from the editor
Open a new agent conversation and ask:
Through Hombee Home MCP, read the current Home Assistant room list and report the available device categories. Make no changes.
Review Cursor’s tool-call panel. It names the Hombee server and shows the specific tool before execution. Keep manual approval enabled for tools that can change devices, security, or automations.
Cursor-specific troubleshooting
- If the server works globally but not in one repository, inspect project MCP settings for a conflicting server with the same name.
- If tools remain stale after reconnecting, start a new agent conversation so the client performs discovery again.
- If authorization completes but discovery fails, verify the selected Hombee installation and its exposed capabilities rather than adding manual headers.
- If a repository contains
.cursor/mcp.json, review it before sharing the project and keep account-specific configuration out of version control.