Home Assistant MCP Server logo

Home Assistant MCP Server

Manage Home Assistant dashboards, files, automations, scripts, scenes, and input helpers from an MCP client.

Install Home Assistant MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "home-assistant-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jarahkon/hass-mcp-server@latest"
      ],
      "env": {
        "HA_URL": "YOUR_VALUE_HERE",
        "HA_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 66 tools correctly (10d ago).

Overview

Home Assistant MCP Server MCP server connects an MCP client to a Home Assistant instance for configuration and file-management tasks. It uses the Home Assistant REST and WebSocket APIs, plus SSH/SFTP for file operations. Tools cover Lovelace dashboards, files, automations, scripts, scenes, and input helpers. Reach for it when an agent needs to inspect or modify Home Assistant configuration rather than only query device state.

Use cases

  • Manage Lovelace dashboards through an MCP client
  • Deploy dashboard configuration JSON
  • Edit Home Assistant automations, scripts, and scenes
  • Upload and read files on a Home Assistant instance
  • Create and update input helpers

Key features

  • Lovelace dashboard CRUD and configuration deployment
  • Home Assistant file management over SSH/SFTP
  • Automation, script, and scene CRUD
  • Input helper management
  • REST and WebSocket API access

Tools66

What Home Assistant MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~5.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

8/8 checks healthy over the last 48d

What it can do

From the 66 tools this server returned when we ran it.

Can delete or modify data · 8Writes files · 2Read-only tools · 56
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age209 days
Maintainers1

Observed 2026-10-20 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @jarahkon/hass-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads506Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed66Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Home Assistant MCP Server works

What Home Assistant MCP Server MCP server does

Home Assistant MCP Server MCP server exposes Home Assistant administration tasks as MCP tools. It can list, create, update, and delete Lovelace dashboards; retrieve and deploy complete dashboard configuration JSON; and manage files relative to the Home Assistant /config/ directory.

The configuration tools cover automations, scripts, scenes, and input helpers. Helpers include input booleans, numbers, text fields, selects, datetimes, buttons, counters, and timers. The available operations vary by resource, but the resource groups generally support listing, retrieval, creation, updates, and deletion.

How it works

The server runs as a local MCP process, commonly launched with npx, while the MCP client supplies its configuration. Home Assistant API operations use the instance URL and a long-lived access token. The README identifies REST and WebSocket as API transport layers.

File tools use SSH/SFTP rather than the Home Assistant API. File access is optional; the server can start without SSH settings, but file operations require them.

Setup and configuration

Home Assistant MCP Server MCP server requires Home Assistant OS or another Home Assistant installation with Supervisor, Node.js 20 or newer, a Home Assistant base URL, and a long-lived access token. Create the token from the Home Assistant profile’s Security section, under Long-Lived Access Tokens.

Set HA_URL to the Home Assistant base URL and HA_TOKEN to the token in the MCP client configuration. The documented stdio setup runs npx -y @jarahkon/hass-mcp-server@latest, allowing the client to download and start the package when needed.

For file management, configure HA_SSH_HOST, HA_SSH_PORT, HA_SSH_USER, and either HA_SSH_KEY_PATH or HA_SSH_PASSWORD. The documented SSH user is root. An SSH application such as Advanced SSH & Web Terminal is required for these file tools.

VS Code can install the extension or use an mcp.json entry. The extension accepts the Home Assistant URL and token through its settings and command palette. Claude Desktop is also documented as a client setup target.

Tools and capabilities

  • Manage Lovelace dashboards and their full JSON configurations.
  • Browse, read, upload, write, create, check, and delete Home Assistant files.
  • Create, inspect, modify, and remove automations, scripts, and scenes.
  • Create and manage the supported Home Assistant input helper types.
  • Connect through REST, WebSocket, and SSH/SFTP transport layers.

Limitations and notes

Home Assistant MCP Server MCP server needs a reachable Home Assistant instance and a valid long-lived access token. SSH configuration is not needed for API-backed tools, but file operations will fail without suitable SSH access. File deletion is restricted to safe directories according to the project description. The material does not document client-specific support beyond the listed VS Code and Claude Desktop setup paths.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Home Assistant MCP Server

Home Assistant MCP Server is an MCP server that connects AI clients to a Home Assistant instance through REST, WebSocket, and SSH/SFTP. Its tools manage Lovelace dashboards, files, automations, scripts, scenes, and input helpers, with creation, updates, retrieval, and deletion operations where supported.

Run it through your MCP client with `npx -y @jarahkon/hass-mcp-server@latest`; no separate package installation is required. Configure `HA_URL` and `HA_TOKEN` in the client’s server definition, and use Node.js 20 or newer.

Configure SSH settings in the MCP client, including `HA_SSH_HOST`, `HA_SSH_USER`, and an SSH key path or password. File tools also require an SSH application on the Home Assistant installation, while the other tools can run without these settings.

Yes, Home Assistant MCP Server works with VS Code through its Marketplace extension or an `mcp.json` stdio configuration. The extension can store the Home Assistant URL and token, and the server then appears in Copilot Chat.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHome Assistant MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/home-assistant-mcp-server?style=directory)](https://allmcps.com/mcp/home-assistant-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/home-assistant-mcp-server"><img src="https://allmcps.com/api/badge/home-assistant-mcp-server?style=directory" alt="Home Assistant MCP Server on AllMCPs" /></a>