About Home Assistant MCP Server
Home Assistant MCP Server is an MCP server for interacting with Home Assistant. It exposes tools that let MCP-enabled applications read and control smart home device states and trigger automations.
Key features
- 01Get device states
- 02Turn devices on and off
- 03Trigger automations
- 04List available entities
Use cases
- 01Checking the current state of a light from an MCP client
- 02Switching a bedroom switch from an AI assistant
- 03Running a morning routine automation on demand
MCP support
This project is an MCP server that exposes tools such as get_state, toggle_entity, trigger_automation and list_entities to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEHome Assistant MCP Server
🌟 Sponsors
| Website | Description |
|---|---|
| ProductDirs.com | AI Tools Directory & Launch Platform - Free submission service for discovering and promoting AI SaaS products, startups, and developer tools with community-driven rankings |
| ThisTools.app | AI SaaS Discovery Platform - Free listing directory for artificial intelligence software, automation tools, and productivity applications with curated collections |
| AIImgCombiner.com | 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.
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 claude
Manual Installation
- Clone this repository:
git clone https://github.com/yourusername/homeassistant-server-mcp.git
cd homeassistant-server-mcp
- Install dependencies:
npm install
- Build the project:
npm run build
- Configure 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.