Skip to content

MCP server

Home Assistant MCP server

Home Assistant's built-in MCP server lets AI read the state of exposed devices and control them, such as lights, climate and covers.

At a glance

Maintained by
Home Assistant (Open Home Foundation)
Tools exposed
8 listed below
Reviewed
September 24, 2026

Why it matters

What it does and why it matters

Home Assistant is an open-source platform for controlling smart devices, used in homes and increasingly in small offices, shops and rental properties. Its built-in MCP server lets an assistant read the state of devices you choose to expose and control them: turn things on and off, set lights and temperatures, move blinds and manage lists.

For small facilities, that means questions such as "is the heating on in the meeting room" and actions such as "turn off all lights on floor two" in plain language.

The tools are Home Assistant intents, and what the assistant can control depends on which devices you expose. Expose only the devices that are safe for an assistant to control, and never locks, alarms or safety systems without careful thought and confirmation steps.

Use cases

Best business use cases

Climate

Check and set temperatures in rooms.

Lighting

Turn lights on or off by area.

Blinds and covers

Open or close blinds on a schedule or request.

Status checks

Check which devices are on after hours.

Shared lists

Add items to shared lists.

Tools

Available tools

Tool names as published by the maintainer at review time. Versions change, so check the repository for the current list.

Tools come from the Assist API the integration exposes; names are Home Assistant built-in intents (developers.home-assistant.io/docs/intent_builtin). Which tools appear depends on exposed entities and chosen LLM API.

Read and write: Read and write: read device state and control exposed devices only.

  • HassTurnOn

    Turn on a device or entity.

  • HassTurnOff

    Turn off a device or entity.

  • HassGetState

    Check the state of an entity.

  • HassLightSet

    Set a light's brightness or color.

  • HassClimateSetTemperature

    Set the target indoor temperature.

  • HassSetPosition

    Set the position of a cover or similar entity.

  • HassListAddItem

    Add an item to a to-do list.

  • HassMediaPause

    Pause a media player.

Workflows

Example workflows

End-of-day check

  1. 1

    Ask what is still on in the office.

  2. 2

    The assistant reads device states.

  3. 3

    It lists lights and heating that are on.

  4. 4

    You confirm what to turn off.

  5. 5

    It switches them off.

Prepare a meeting room

  1. 1

    Ask to prepare room 2 for 10 a.m.

  2. 2

    The assistant sets the temperature.

  3. 3

    It turns on the lights.

  4. 4

    It opens the blinds.

  5. 5

    It confirms the room is ready.

Prompts

Example prompts

  • “What lights and heating are still on in the office?”

  • “Set the meeting room to 21 degrees.”

  • “Turn off all lights on the second floor.”

Setup

Installation and configuration

Examples for Claude Desktop and Claude Code. Replace the placeholder values with your own keys, and store secrets outside version control.

Claude Desktop: claude_desktop_config.json

{
    "mcpServers": {
        "Home Assistant": {
            "command": "mcp-proxy",
            "args": [
                "--transport=streamablehttp",
                "--stateless",
                "http://<your_local_home_assistant_ip_or_url>:8123/api/mcp"
            ],
            "env": {
                "API_ACCESS_TOKEN": "<your_access_token_here>"
            }
        }
    }
}

Claude Code: terminal

claude mcp add-json "HA" '{"type": "http", "url": "https://<your_home_assistant_url>/api/mcp", "oauth": {"clientId": "http://localhost:12345", "callbackPort": 12345}}' --client-secret
  • Hosted server: http(s)://<your_home_assistant_url>/api/mcp (Streamable HTTP, served by your Home Assistant).
  • Needs: OAuth (IndieAuth) or a Home Assistant long-lived access token..
  • Claude Desktop: This JSON is the documented local setup. For a remote HA, docs use a custom connector with OAuth.

Security

Security considerations

  • Expose carefully

    Expose only devices that are safe for an assistant to control.

  • Locks and alarms

    Do not expose locks, alarms or safety systems without confirmation steps.

  • Access tokens

    Use a dedicated long-lived token and protect it.

  • History

    Review device history for unexpected actions.

Related servers

Servers that pair well with it

n8n

n8n's official instance-level MCP server lets AI search, run, build, update and publish workflows and look up nodes and credentials.

Zapier

Zapier's official MCP server lets AI discover, enable and run actions across thousands of connected apps, with separate read and write tools.

Time

The MCP project's Time reference server gives AI the current time in any time zone and converts times between zones.

Keep exploring

FAQ

Questions people ask us

Have a question that is not here? Ask us directly.

Start a project

Want this connected to your own systems? We build AI workflows with MCP.

Send a short brief. We reply with questions, a suggested plan and an estimate you can compare with other offers.

Your privacy choices

We use necessary storage to run this site. With your permission we also use Google Analytics to see which pages help people, and load maps from Google. You can change this at any time. Read the cookie policy.