Model Context Protocol Server for Home Assistant
The server uses the MCP protocol to share access to a local Home Assistant instance with an LLM application.
A powerful bridge between your Home Assistant instance and Language Learning Models (LLMs), enabling natural language control and monitoring of your smart home devices through the Model Context Protocol (MCP). This server provides a comprehensive API for managing your entire Home Assistant ecosystem, from device control to system administration.
Features
- ๐ฎ Device Control: Control any Home Assistant device through natural language
- ๐ Real-time Updates: Get instant updates through Server-Sent Events (SSE)
- ๐ค Automation Management: Create, update, and manage automations
- ๐ State Monitoring: Track and query device states
- ๐ Secure: Token-based authentication and rate limiting
- ๐ฑ Mobile Ready: Works with any HTTP-capable client
Real-time Updates with SSE
The server includes a powerful Server-Sent Events (SSE) system that provides real-time updates from your Home Assistant instance. This allows you to:
- ๐ Get instant state changes for any device
- ๐ก Monitor automation triggers and executions
- ๐ฏ Subscribe to specific domains or entities
- ๐ Track service calls and script executions
Quick SSE Example
const eventSource = new EventSource(
'http://localhost:3000/subscribe_events?token=YOUR_TOKEN&domain=light'
);
eventSource.onmessage = (event) => {
const data = JSON.parse(event.data);
console.log('Update received:', data);
};See SSE_API.md for complete documentation of the SSE system.
Table of Contents
- Key Features
- Prerequisites
- Installation
- Configuration
- Development
- API Reference
- Natural Language Integration
- Troubleshooting
- Project Status
- Contributing
- Resources
- License
Key Features
Core Functionality ๐ฎ
- Smart Device Control
- ๐ก Lights: Brightness, color temperature, RGB color
- ๐ก๏ธ Climate: Temperature, HVAC modes, fan modes, humidity
- ๐ช Covers: Position and tilt control
- ๐ Switches: On/off control
- ๐จ Sensors & Contacts: State monitoring
- ๐ต Media Players: Playback control, volume, source selection
- ๐ช๏ธ Fans: Speed, oscillation, direction
- ๐ Locks: Lock/unlock control
- ๐งน Vacuums: Start, stop, return to base
- ๐น Cameras: Motion detection, snapshots
System Management ๐ ๏ธ
-
Add-on Management
- Browse available add-ons
- Install/uninstall add-ons
- Start/stop/restart add-ons
- Version management
- Configuration access
-
Package Management (HACS)
- Integration with Home Assistant Community Store
- Multiple package types support:
- Custom integrations
- Frontend themes
- Python scripts
- AppDaemon apps
- NetDaemon apps
- Version control and updates
- Repository management
-
Automation Management
- Create and edit automations
- Advanced configuration options:
- Multiple trigger types
- Complex conditions
- Action sequences
- Execution modes
- Duplicate and modify existing automations
- Enable/disable automation rules
- Trigger automation manually
Architecture Features ๐๏ธ
-
Intelligent Organization
- Area and floor-based device grouping
- State monitoring and querying
- Smart context awareness
- Historical data access
-
Robust Architecture
- Comprehensive error handling
- State validation
- Secure API integration
- TypeScript type safety
- Extensive test coverage
Prerequisites
- Node.js 20.10.0 or higher
- NPM package manager
- Docker Compose for containerization
- Running Home Assistant instance
- Home Assistant long-lived access token (How to get token)
- HACS installed for package management features
- Supervisor access for add-on management
Installation
Basic Setup
# Clone the repository
git clone https://github.com/tevonsb/homeassistant-mcp.git
cd homeassistant-mcp
# Install dependencies
npm install
# Build the project
npm run buildDocker Setup (Recommended)
The project includes Docker support for easy deployment and consistent environments across different platforms.
-
Clone the repository:
git clone https://github.com/tevonsb/homeassistant-mcp.git cd homeassistant-mcp -
Configure environment:
cp .env.example .envEdit the
.envfile with your Home Assistant configuration:# Home Assistant Configuration HASS_HOST=http://homeassistant.local:8123 HASS_TOKEN=your_home_assistant_token HASS_SOCKET_URL=ws://homeassistant.local:8123/api/websocket # Server Configuration PORT=3000 NODE_ENV=production DEBUG=false -
Build and run with Docker Compose:
# Build and start the containers docker compose up -d # View logs docker compose logs -f # Stop the service docker compose down -
Verify the installation: The server should now be running at
http://localhost:3000. You can check the health endpoint athttp://localhost:3000/health. -
Update the application:
# Pull the latest changes git pull # Rebuild and restart the containers docker compose up -d --build
Docker Configuration
The Docker setup includes:
- Multi-stage build for optimal image size
- Health checks for container monitoring
- Volume mounting for environment configuration
- Automatic container restart on failure
- Exposed port 3000 for API access
Docker Compose Environment Variables
All environment variables can be configured in the .env file. The following variables are supported:
HASS_HOST: Your Home Assistant instance URLHASS_TOKEN: Long-lived access token for Home AssistantHASS_SOCKET_URL: WebSocket URL for Home AssistantPORT: Server port (default: 3000)NODE_ENV: Environment (production/development)DEBUG: Enable debug mode (true/false)
Configuration
Environment Variables
# Home Assistant Configuration
HASS_HOST=http://homeassistant.local:8123 # Your Home Assistant instance URL
HASS_TOKEN=your_home_assistant_token # Long-lived access token
HASS_SOCKET_URL=ws://homeassistant.local:8123/api/websocket # WebSocket URL
# Server Configuration
PORT=3000 # Server port (default: 3000)
NODE_ENV=production # Environment (production/development)
DEBUG=false # Enable debug mode
# Test Configuration
TEST_HASS_HOST=http://localhost:8123 # Test instance URL
TEST_HASS_TOKEN=test_token # Test tokenConfiguration Files
- Development: Copy
.env.exampleto.env.development - Production: Copy
.env.exampleto.env.production - Testing: Copy
.env.exampleto.env.test
Adding to Claude Desktop (or other clients)
To use your new Home Assistant MCP server, you can add Claude Desktop as a client. Add the following to the configuration. Note this will run the MCP within claude and does not work with the Docker method.
{
"homeassistant": {
"command": "node",
"args": [<path/to/your/dist/folder>]
"env": {
NODE_ENV=development
HASS_HOST=http://homeassistant.local:8123
HASS_TOKEN=your_home_assistant_token
PORT=3000
HASS_SOCKET_URL=ws://homeassistant.local:8123/api/websocket
LOG_LEVEL=debug
}
}
}
API Reference
Device Control
Common Entity Controls
{
"tool": "control",
"command": "turn_on", // or "turn_off", "toggle"
"entity_id": "light.living_room"
}Light Control
{
"tool": "control",
"command": "turn_on",
"entity_id": "light.living_room",
"brightness": 128,
"color_temp": 4000,
"rgb_color": [255, 0, 0]
}Add-on Management
List Available Add-ons
{
"tool": "addon",
"action": "list"
}Install Add-on
{
"tool": "addon",
"action": "install",
"slug": "core_configurator",
"version": "5.6.0"
}Manage Add-on State
{
"tool": "addon",
"action": "start", // or "stop", "restart"
"slug": "core_configurator"
}Package Management
List HACS Packages
{
"tool": "package",
"action": "list",
"category": "integration" // or "plugin", "theme", "python_script", "appdaemon", "netdaemon"
}Install Package
{
"tool": "package",
"action": "install",
"category": "integration",
"repository": "hacs/integration",
"version": "1.32.0"
}Automation Management
Create Automation
{
"tool": "automation_config",
"action": "create",
"config": {
"alias": "Motion Light",
"description": "Turn on light when motion detected",
"mode": "single",
"trigger": [
{
"platform": "state",
"entity_id": "binary_sensor.motion",
"to": "on"
}
],
"action": [
{
"service": "light.turn_on",
"target": {
"entity_id": "light.living_room"
}
}
]
}
}Duplicate Automation
{
"tool": "automation_config",
"action": "duplicate",
"automation_id": "automation.motion_light"
}Core Functions
State Management
GET /api/state
POST /api/stateManages the current state of the system.
Example Request:
POST /api/state
{
"context": "living_room",
"state": {
"lights": "on",
"temperature": 22
}
}Context Updates
POST /api/contextUpdates the current context with new information.
Example Request:
POST /api/context
{
"user": "john",
"location": "kitchen",
"time": "morning",
"activity": "cooking"
}Action Endpoints
Execute Action
POST /api/actionExecutes a specified action with given parameters.
Example Request:
POST /api/action
{
"action": "turn_on_lights",
"parameters": {
"room": "living_room",
"brightness": 80
}
}Batch Actions
POST /api/actions/batchExecutes multiple actions in sequence.
Example Request:
POST /api/actions/batch
{
"actions": [
{
"action": "turn_on_lights",
"parameters": {
"room": "living_room"
}
},
{
"action": "set_temperature",
"parameters": {
"temperature": 22
}
}
]
}Query Functions
Get Available Actions
GET /api/actionsReturns a list of all available actions.
Example Response:
{
"actions": [
{
"name": "turn_on_lights",
"parameters": ["room", "brightness"],
"description": "Turns on lights in specified room"
},
{
"name": "set_temperature",
"parameters": ["temperature"],
"description": "Sets temperature in current context"
}
]
}Context Que
โฆ