MCP setup (Cursor / Claude Code / VS Code / OpenCode) 1. Mint a token at https://hire.vome.io/account/api-tokens (GitHub sign-in). 2. Add to ~/.cursor/mcp.json (one entry per HA instance): Hosted (recommended — no install, no Node required): { "mcpServers": { "vome": { "type": "http", "url": "https://vome.io/mcp", "headers": { "Authorization": "Bearer " } } } } One entry reaches every instance the token is scoped to. VS Code (.vscode/mcp.json): the same entry, but the top-level key is "servers", not "mcpServers". OpenCode (opencode.json) has its own shape: { "$schema": "https://opencode.ai/config.json", "mcp": { "vome": { "type": "remote", "url": "https://vome.io/mcp", "enabled": true, "oauth": false, "headers": { "Authorization": "Bearer " } } } } Local alternative (runs the server on your machine): { "mcpServers": { "ha-home": { "command": "npx", "args": ["-y", "@vortitron/home-assistant-mcp"], "env": { "VOMEHOME_API_URL": "https://hire.vome.io", "VOMEHOME_TOKEN": "", "VOMEHOME_INSTANCE_ID": "" } } } } Needs Node 18+ with npx on PATH. A "Connection closed" error almost always means the agent could not find npx: check "which npx", and if that works, set command to that absolute path (editors spawn MCP servers with a minimal environment). On Windows use WSL. Permissions live on the token (server-side): read-only by default; per-instance ha:write / ha:config and account-wide instances:write are granted per token on the tokens page and revocable any time. No account at all: install the Vome add-on in Home Assistant and open its panel -> Coding agent. Tick what the key may do, press Issue a key, and paste the mcp.json it hands back. It covers that one instance and stops working after two days unless the owner connects a Vome account, which keeps the same key working. Direct mode (no Vome at all): set HA_URL + HA_TOKEN instead — see https://github.com/Vortitron/home-assistant-mcp#readme