Home MCP Server

Enable Cursor, VS Code, Claude Code or any MCP-enabled IDE to help you vibecode and manage Home Assistant: create automations, design dashboards

Local serverstdioTypeScript

What is the Home MCP server?

Enable Cursor, VS Code, Claude Code or any MCP-enabled IDE to help you vibecode and manage Home Assistant: create automations, design dashboards, tweak themes, modify configs, and deploy changes using natural language. That is what the home mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

You describe your goal → AI inspects your Home Assistant → designs a custom solution → and deploys it on-board automatically. 🚀

Getting it running

Installation goes through your MCP client rather than a global install: point it at ENOENT on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Variable — Description
  • HA_AGENT_URL — URL of HA Vibecode Agent
  • HA_AGENT_KEY — Agent Key for authentication
  • Architecture — The Architecture tool exposed by this server

What it needs from you

Configuration is passed through the environment: HA_AGENT_URL, HA_AGENT_KEY, SUPERVISOR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Home's toolset — Variable, HA_AGENT_URL, HA_AGENT_KEY and 1 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
VariableDescription
HA_AGENT_URLURL of HA Vibecode Agent
HA_AGENT_KEYAgent Key for authentication
ArchitectureThe Architecture tool exposed by this server.

How to install the Home MCP server

{
  "mcpServers": {
    "home-assistant": {
      "command": "npx",
      "args": ["-y", "@coolver/home-assistant-mcp@latest"],
      "env": {
        "HA_AGENT_URL": "http://<home-assistant-host>:8099",
        "HA_AGENT_KEY": "your_api_key_here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
HA_AGENT_URLEndpoint or connection string the server talks to.Yes
HA_AGENT_KEYCredential the server authenticates with.Yes
SUPERVISOR_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Home to Variable.
  • Use Home to HA AGENT URL.
  • Use Home to HA AGENT KEY.

Frequently asked questions

It connects Home to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Variable, HA_AGENT_URL, HA_AGENT_KEY, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Home directly.