MCP.so
Sign In

Hass-MCP

@voska

Repository

About Hass-MCP

Control and query Home Assistant from Claude and other LLMs — a Model Context Protocol (MCP) server.

#home-automation#mcp#home-assistant#mcp-server

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "hass-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HA_URL",
        "-e",
        "HA_TOKEN",
        "voska/hass-mcp"
      ],
      "env": {
        "HA_URL": "http://homeassistant.local:8123",
        "HA_TOKEN": "YOUR_LONG_LIVED_TOKEN"
      }
    }
  }
}

Tools

15

Get the Home Assistant version

Get the state of a specific entity with optional field filtering

Perform actions on entities (turn on, off, toggle)

Get a list of entities with optional domain filtering and search

Search for entities matching a query

Get a summary of a domain's entities

Get a list of all automations

Call any Home Assistant service

Restart Home Assistant

Get the state history of an entity (last N hours)

Get state-change history for an entity over an

Get long-term aggregated statistics (mean / min / max

Same, but for an explicit date/time range —

Get the Home Assistant error log, with optional

List entities in a specific area / room

Overview

What is Hass-MCP?

Hass-MCP is a Model Context Protocol (MCP) server that allows AI assistants like Claude to interact directly with a Home Assistant instance. It enables querying device states, controlling entities, troubleshooting automations, and more.

How to use Hass-MCP?

Install via Docker (recommended) or Python 3.13+ with uv. Configure the HA_URL and HA_TOKEN environment variables with your Home Assistant URL and a long-lived access token. Add the server to your MCP client (e.g., Claude Desktop, Cursor, Claude Code CLI) using the provided configurations.

Key features of Hass-MCP

  • Entity management: get states, control devices, search entities
  • Domain summaries for high-level entity type info
  • Automation support: list and control automations
  • Guided conversations for common tasks via prompts
  • Smart search for entities by name, type, or state
  • Token‑efficient JSON responses to minimize usage

Use cases of Hass-MCP

  • Ask your AI for the current state of any device or sensor
  • Control lights, switches, and other entities by voice or text
  • Troubleshoot failing automations and misbehaving entities
  • Generate optimized smart home routines based on usage patterns
  • Audit entity naming consistency and dashboard layouts

FAQ from Hass-MCP

What prerequisites are needed to run Hass-MCP?

A Home Assistant instance with a long-lived access token. You also need Docker or Python 3.13+ with uv installed.

Can I use Hass-MCP with clients other than Claude?

Yes. The README includes setup instructions for Cursor, Claude Code CLI, and any MCP client that supports the streamable HTTP transport.

Does Hass-MCP support HTTP transport, and is it secure?

Yes, it supports MCP streamable HTTP transport. However, HTTP mode exposes full Home Assistant control over the network without built‑in authentication, so you must put it behind a reverse proxy, VPN, or bind to localhost only.

Where does user data live when using Hass-MCP?

All data is queried directly from the user's Home Assistant instance. The server does not store or log data externally.

Are there any known limitations of Hass-MCP?

The README does not mention explicit limits. It notes token‑efficient JSON responses but does not detail maximum entity count or rate limits.

Frequently asked questions

What prerequisites are needed to run Hass-MCP?

A Home Assistant instance with a long-lived access token. You also need Docker or Python 3.13+ with uv installed.

Can I use Hass-MCP with clients other than Claude?

Yes. The README includes setup instructions for Cursor, Claude Code CLI, and any MCP client that supports the streamable HTTP transport.

Does Hass-MCP support HTTP transport, and is it secure?

Yes, it supports MCP streamable HTTP transport. However, HTTP mode exposes full Home Assistant control over the network without built‑in authentication, so you must put it behind a reverse proxy, VPN, or bind to localhost only.

Where does user data live when using Hass-MCP?

All data is queried directly from the user's Home Assistant instance. The server does not store or log data externally.

Are there any known limitations of Hass-MCP?

The README does not mention explicit limits. It notes token‑efficient JSON responses but does not detail maximum entity count or rate limits.

Comments

Basic information

Category

AI & Agents

License

MIT

Transports

stdio

Author

voska

Submitted by

Matt Voska

More AI & Agents MCP servers

F

fhirHydrant

faulkj

Open-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.

14
L

Legion MCP

faulkj

MCP-native LLM councils for debates, juries, blind panels, voting, refinement, and custom multi-model deliberation.

1

PDI Bridge for Claude

jxrlabs

Connect Claude Desktop to your ServiceNow PDI. Query records, inspect Business Rules, review ACLs, and troubleshoot against your live instance.

bsv.cx

Andy Rowe

Timestamp and verify evidence on-chain. Let your agent prove what it saw and when. bsv.cx gives an AI agent verifiable memory. Timestamp a hash of any output, archive a web page as it looked, or fetch a URL with a recei

GetIntel

tarang8811

Public docs + tool manifest for the GetIntel MCP connector (app.getintel.ai)