Home Assistant▌

by oleander
Transform your smarter home with Home Assistant: advanced home automation smart home control and secure device managemen
Enables natural language control of Home Assistant smart home systems with tools for querying entity states, executing service calls, and retrieving system information through secure WebSocket or stdio communication.
best for
- / Smart home owners wanting voice/chat control
- / Home automation enthusiasts building AI assistants
- / Developers creating natural language home interfaces
capabilities
- / Query smart device states and properties
- / Execute Home Assistant service calls
- / Control lights, switches, and other entities
- / Retrieve system information and history
- / Manage automations and scenes
- / Access entity attributes and metadata
what it does
Connects Large Language Models to Home Assistant, enabling natural language control and querying of smart home devices and automations.
about
Home Assistant is a community-built MCP server published by oleander that provides AI assistants with tools and capabilities via the Model Context Protocol. Transform your smarter home with Home Assistant: advanced home automation smart home control and secure device managemen It is categorized under developer tools.
how to install
You can install Home Assistant in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Home Assistant is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Home Assistant MCP Server
A Model Context Protocol (MCP) server for integrating with Home Assistant, allowing LLMs to control and query your smart home.
Features
- Query and control Home Assistant entities via natural language
- Works with any MCP-compatible client (like Claude Desktop)
- Provides tools for state management, service calls, history, and more
- Secure authentication using Home Assistant long-lived access tokens
- Multiple transport options (stdio for local processes, SSE for remote clients)
- Demo mode with mock data for testing and demonstration when Home Assistant is not available
Installation
# Install globally using bun
bun install -g home-assistant-mcp-server
# Or install from source
git clone https://github.com/oleander/home-assistant-mcp-server.git
cd home-assistant-mcp-server
bun install
bun run build
bun link
Configuration
Create a .env file in your current directory with the following variables:
# Required configurations
HASS_URL=http://your-home-assistant:8123 # URL to your Home Assistant instance
HASS_TOKEN=your_long_lived_access_token # Long-lived access token for authentication
# Optional configurations
PORT=3000 # Port for the HTTP server (default: 3000)
HASS_MOCK=false # Enable mock data mode when Home Assistant is unavailable (default: false)
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
HASS_URL | Yes | - | URL to your Home Assistant instance (e.g., http://homeassistant.local:8123) |
HASS_TOKEN | Yes | - | Long-lived access token for authenticating with Home Assistant |
PORT | No | 3000 | Port number for the HTTP server when using HTTP/SSE transport |
HASS_MOCK | No | false | When set to "true", enables mock data mode for testing without a Home Assistant connection |
To get a long-lived access token:
- Log in to your Home Assistant instance
- Click on your profile (bottom left)
- Scroll down to "Long-Lived Access Tokens"
- Create a new token with a descriptive name
- Copy the token value (you won't see it again)
Usage
Running as a standalone server
# Standard mode (requires a running Home Assistant instance)
home-assistant-mcp-server # Start with HTTP/SSE transport
home-assistant-mcp-server --stdio # Start with stdio transport for direct process communication
# Demo mode (with mock data when Home Assistant is unavailable)
home-assistant-mcp-server --mock # Start with HTTP/SSE transport and mock data
home-assistant-mcp-server --stdio --mock # Start with stdio transport and mock data
Integration with Claude Desktop
To use with Claude Desktop:
-
Edit your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Add the server configuration:
{
"mcpServers": {
"homeassistant": {
"command": "home-assistant-mcp-server"
"env": {
"HASS_URL": "http://your-home-assistant:8123",
"HASS_TOKEN": "your_token_here",
"HASS_MOCK": "true"
}
}
}
}
If you have Home Assistant running, simply remove the --mock flag and set HASS_MOCK to false.
- Restart Claude Desktop
Available Tools
The server exposes several tools for interacting with Home Assistant:
states- Query entity stateslights- List lightslight- Control a lightservice- Call Home Assistant serviceshistory- Retrieve historical entity dataservices- List available servicesconfig- Get Home Assistant configurationdomains- List available domainserror_log- Get Home Assistant error logdevices- Get all devices in Home Assistant
For detailed usage examples, see docs/hass-mcp.md.
Security
This server requires a Home Assistant access token with full access. Consider these security recommendations:
- Only run the server on trusted networks
- Use HTTPS if exposing the server remotely
- Keep your
.envfile secure and don't commit it to source control - Consider using a token with limited permissions when possible
License
This project is licensed under the MIT License - see the LICENSE file for details.
FAQ
- What is the Home Assistant MCP server?
- Home Assistant is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Home Assistant?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Home Assistant is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Home Assistant against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Home Assistant is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Home Assistant reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Home Assistant for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Home Assistant surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Home Assistant has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Home Assistant benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Home Assistant into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Home Assistant is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.