Home Assistant MCP
Click on "Install 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 MCPturn on the bedroom light"
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
A Model Context Protocol (MCP) server that integrates Claude AI with your local Home Assistant instance, enabling natural language control of your smart home devices directly through Claude's chat interface.
Overview
This project bridges Claude AI and Home Assistant, allowing you to:
Control smart home devices using natural language in Claude chat
Query device states and automation status
Execute Home Assistant actions through conversational AI
Keep everything local and secure with your own Home Assistant instance
Related MCP server: Home Assistant MCP Server
Features
š Local Smart Home Integration - Your Home Assistant instance and devices stay completely local; only your chat messages go to Claude for processing/Understanding your conversation
š¤ Claude AI Control - Use natural language to control devices
š Secure Credentials - Environment-based configuration keeps tokens safe
š MCP Protocol - Follows Model Context Protocol standard
ā” Real-time Device Control - Execute automations and control devices instantly
š MCP Standard - Works with any AI tool/chat that supports Model Context Protocol, not limited to Claude
Compatibility
This MCP server works with any AI assistant that supports the Model Context Protocol standard, including:
Claude (claude.ai, Claude Desktop, Claude API)
VS Code (with MCP extension)
Other MCP-compatible tools (growing ecosystem)
This means your smart home integration isn't vendor-locked and will work with future AI tools that adopt the MCP standard.
Prerequisites
Node.js 16+
Local Home Assistant instance running
Home Assistant long-lived access token
Claude Desktop or Claude.ai with Developer access
Quick Start
1. Clone and Install
git clone https://github.com/aniketbhondave/Home-Assistant-MCP.git
cd Home-Assistant-MCP
npm install2. Get Your Home Assistant Token
Open your Home Assistant instance
Click your profile (bottom left)
Scroll to "Long-lived access tokens"
Click "Create Token"
Name it (e.g., "Claude MCP") and copy the token
3. Add to Claude Desktop
Click the settings icon (gear) in the top right
Click Developer tab
Click Edit Config button
Paste this configuration:
{
"mcpServers": {
"home-assistant": {
"command": "bash",
"args": [
"-c",
"cd /path/to/Home-Assistant-MCP && HOME_ASSISTANT_URL=http://192.168.x.xxx:8123 HOME_ASSISTANT_TOKEN=your-token-here node index.js"
]
}
}
}Replace the following:
/path/to/Home-Assistant-MCP- Full path to your project (e.g.,/Users/yourname/Home-Assistant-MCP)http://192.168.x.xxx:8123- Your Home Assistant URL (use IP address, not homeassistant.local)your-token-here- The token you copied from Home Assistant
Click Save
Restart Claude Desktop completely (close and reopen)
4. Test It
Ask Claude:
"List all my devices"
"Turn on the bedroom light"
"What devices are currently on?"
Done! š
Example Commands
"List all my devices"
"Turn on the bedroom light"
"What devices are currently on?"
"Turn off all lights"
"Get the status of my kitchen fan"
Claude will understand natural language and communicate with your Home Assistant instance to perform the requested actions.
Project Structure
Home-Assistant-MCP/
āāā index.js # Main MCP server entry point
āāā .env.example # Environment variables template
āāā .gitignore # Git configuration
āāā package.json # Node.js dependencies
āāā README.md # This file
āāā LICENSE # MIT LicenseSmithery Deployment
This MCP is ready and planned to be deployed to Smithery. Users will be able to install it directly through the Smithery marketplace (TODO).
Security Notes
Use IP addresses instead of hostnames (homeassistant.local) for Home Assistant URL
Keep your Home Assistant token secure and rotate it periodically
Use strong authentication for your Home Assistant instance
Always verify the Home Assistant instance is accessible only from trusted networks
Status & Roadmap
š§ Work in Progress
Current features and planned enhancements:
Basic MCP server setup
Home Assistant connection
Check device status via Claude
Turn devices on/off via Claude
Natural language device matching
Brightness and color control
Automation triggering
Climate control (temperature, humidity)
Enhanced error handling
Batch device operations
Device state caching for performance
Advanced scene management
Troubleshooting
"Server transport closed unexpectedly"
Verify the path to your Home Assistant MCP project is correct
Check that Home Assistant URL and token are correct (no typos)
Ensure Home Assistant is accessible from your machine
Restart Claude Desktop completely
"Cannot connect to Home Assistant"
Verify
HOME_ASSISTANT_URLis correct (use IP, not hostname)Check the token hasn't expired - create a new one if needed
Ensure Home Assistant is running
Verify the machine running Claude can reach Home Assistant IP
Device Control Not Working
Verify the token has appropriate permissions in Home Assistant
Check that devices exist in your Home Assistant instance
Review Claude's responses for specific error messages
MCP Server not showing in Claude
Restart Claude Desktop completely (close and reopen)
Check JSON syntax in config file (invalid JSON will be ignored)
Verify all paths are absolute (full paths, not relative)
License
MIT License
Copyright (c) 2026 Aniket Bhondave
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.
Support
For help and questions:
Check the Troubleshooting section above
Review Home Assistant documentation
Check MCP documentation
Open an issue on GitHub
Acknowledgments
Built with Home Assistant
Powered by Claude AI
Follows Model Context Protocol standards
Note: This project is in active development. Features and APIs may change. Please refer to README for updates.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aniketbhondave/Home-Assistant-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server