Home Assistant MCP Server
The Home Assistant MCP Server allows you to interact with your Home Assistant instance via the Model Context Protocol (MCP). With this server, you can:
Get the current state of specific Home Assistant entities
Control devices by toggling them on or off
Trigger predefined Home Assistant automations
List all available entities, optionally filtered by domain
Allows to interact with Home Assistant devices, including getting device states, controlling device states (on/off), triggering automations, and listing available entities
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Home Assistant MCP Server turn on the living room lights"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Home Assistant MCP Server
🌟 Sponsors
Website | Description |
AI Tools Directory & Launch Platform - Free submission service for discovering and promoting AI SaaS products, startups, and developer tools with community-driven rankings | |
AI SaaS Discovery Platform - Free listing directory for artificial intelligence software, automation tools, and productivity applications with curated collections | |
AI-Powered Image Fusion Tool - Free online service for merging and combining photos using artificial intelligence with preset styles and custom prompts for professional results |
A Model Context Protocol (MCP) server for interacting with Home Assistant. This server provides tools to control and monitor your Home Assistant devices through MCP-enabled applications.
This project is part of the AI Model Context Protocol (MCP) ecosystem. For more information and documentation about MCP tools, visit www.aimcp.info.
Related MCP server: Hass-MCP
Features
Get device states
Control device states (on/off)
Trigger automations
List available entities
Installation
Installing via Smithery
To install Home Assistant MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @hekmon8/Homeassistant-server-mcp --client claudeManual Installation
Clone this repository:
git clone https://github.com/yourusername/homeassistant-server-mcp.git
cd homeassistant-server-mcpInstall dependencies:
npm installBuild the project:
npm run buildConfigure the MCP server by adding the following to your MCP settings file (typically located at
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonfor VSCode):
{
"mcpServers": {
"homeassistant": {
"command": "node",
"args": ["/path/to/homeassistant-mcp/homeassistant-server/build/index.js"],
"env": {
"HA_URL": "http://your-homeassistant-url:8123",
"HA_TOKEN": "your-long-lived-access-token"
}
}
}
}Replace your-homeassistant-url and your-long-lived-access-token with your Home Assistant instance URL and access token.
Usage
The server provides the following tools:
1. Get Device State
// Example usage
use_mcp_tool({
server_name: "homeassistant",
tool_name: "get_state",
arguments: {
entity_id: "light.living_room"
}
});2. Toggle Device State
// Example usage
use_mcp_tool({
server_name: "homeassistant",
tool_name: "toggle_entity",
arguments: {
entity_id: "switch.bedroom",
state: "on" // or "off"
}
});3. Trigger Automation
// Example usage
use_mcp_tool({
server_name: "homeassistant",
tool_name: "trigger_automation",
arguments: {
automation_id: "automation.morning_routine"
}
});4. List Entities
// Example usage
use_mcp_tool({
server_name: "homeassistant",
tool_name: "list_entities",
arguments: {
domain: "light" // optional, filters by domain
}
});Contributing
Contributions are welcome! Here's how you can help:
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
Please make sure to update tests as appropriate and follow the existing code style.
Documentation
For detailed documentation about MCP tools and the ecosystem:
Visit www.aimcp.info
Check the MCP tools directory on the website
Read the integration guides and best practices
License
This project is licensed under the MIT License - see below for details:
MIT License
Copyright (c) 2024 homeassistant-mcp
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.Security
To securely use this server:
Always use HTTPS for your Home Assistant instance
Keep your access tokens secure and never commit them to version control
Regularly rotate your access tokens
Use environment variables for sensitive information
Support
If you encounter any issues or have questions, please:
Check the existing issues in the repository
Create a new issue if your problem hasn't been reported
Provide as much context as possible when reporting issues
Visit www.aimcp.info for additional support resources
Available Tools
4 toolsget_stateC
Get the current state of a Home Assistant entity
Inputs: entity_id (required).
list_entitiesC
List all available entities in Home Assistant
Inputs: domain.
toggle_entityC
Toggle a Home Assistant entity on/off
Inputs: entity_id (required), state (required).
trigger_automationC
Trigger a Home Assistant automation
Inputs: automation_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_state retrieves entity status, list_entities enumerates available entities, toggle_entity changes binary states, and trigger_automation initiates automations. The actions (get, list, toggle, trigger) and targets (state, entities, entity, automation) are uniquely paired, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case: get_state, list_entities, toggle_entity, and trigger_automation. The verbs are precise and descriptive, and the naming convention is uniform across all four tools, making them predictable and easy to understand.
With 4 tools, the count is slightly low but reasonable for basic Home Assistant control. It covers core operations like monitoring and toggling entities, and triggering automations, though it lacks advanced actions like setting specific states or managing scenes, which might be expected in a more comprehensive set.
The tool set covers essential read and toggle operations for entities and automations, providing a functional surface for basic interactions. However, there are minor gaps, such as the inability to set specific entity states (e.g., brightness or temperature) or manage other Home Assistant components like scenes or scripts, which could limit more complex agent workflows.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
A Model Context Protocol server for Wix AI tools
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates with Home Assistant to provide smart home control capabilities through natural language, supporting devices like lights, climate systems, locks, alarms, and humidifiers.3MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact directly with Home Assistant, allowing them to query device states, control smart home entities, and perform automation tasks.29351MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows large language models to control and query Home Assistant smart home systems through natural language interactions.34 npm5MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server providing 60 tools across 9 categories to interact with and manage Home Assistant smart home systems via the REST API.5MIT