Home Assistant MCP Server

What is Home Assistant MCP Server?

A Model Context Protocol (MCP) server that provides tools to control and monitor Home Assistant devices through MCP-enabled applications.

How to use Home Assistant MCP Server?

Clone the repository, install dependencies with npm install, build with npm run build, then configure the MCP server in your settings file (e.g., claude_desktop_config.json) by setting the command to node, args to the built index.js, and env variables HA_URL and HA_TOKEN. Use the provided tools (get_state, toggle_entity, trigger_automation, list_entities) from any MCP client.

Key features of Home Assistant MCP Server

• Get device states
• Control device states (on/off)
• Trigger automations
• List available entities

Use cases of Home Assistant MCP Server

• Read the current state of a Home Assistant entity (e.g., a light or sensor).
• Turn a device on or off via the MCP interface.
• Trigger an automation by its ID.
• List all entities in a given domain (e.g., all lights).

FAQ from Home Assistant MCP Server

What are the runtime requirements?

Node.js and npm are required to build and run the server after cloning the repository.

How do I configure authentication?

Set the HA_URL and HA_TOKEN environment variables when configuring the MCP server. Replace with your Home Assistant instance URL and a long-lived access token.

Where does the server connect to?

It connects directly to your Home Assistant instance via the provided URL and access token. All data resides on that instance.

What transport or authentication does the server use?

The server uses the MCP protocol over stdio; authentication is handled via a Home Assistant long-lived access token passed in the HA_TOKEN environment variable.