Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @coolver/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
HA_AGENT_URL=<value> HA_AGENT_KEY=<secret> claude mcp add io.github.coolver-home-assistant-mcp -- npx -y @coolver/home-assistant-mcp@3.2.12In einem Terminal ausführen.
{ "mcpServers": { "io.github.coolver-home-assistant-mcp": { "command": "npx", "args": [ "-y", "@coolver/[email protected]" ], "env": { "HA_AGENT_URL": "<value>", "HA_AGENT_KEY": "<secret>" } } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
⚙️ This MCP server works together with the
Home Assistant Vibecode Agent, installed as a Home Assistant add-on. The agent runs on your Home Assistant instance and provides “eyes and hands” for AI IDEs like Cursor, VS Code, Claude Code, or any other MCP-enabled IDE.
Vibecode your Home Assistant setup from your IDE: automations, dashboards, themes and configs
Let AI build your Home Assistant automations – or act as your DevOps for the ones you write by hand. Just describe what you need in natural language. 🏠🤖
You describe your goal → AI inspects your Home Assistant → designs a custom solution → and deploys it on-board automatically. 🚀
And if you prefer to handcraft your automations and scripts yourself, the agent can simply act as your DevOps and extra pair of hands: quickly uploading your changes, running tests, and analyzing logs on demand. You stay in control and decide how much you delegate to AI and how deep it should go.
Transform the way you manage your smart home. This add-on enables Cursor, Visual Studio Code (VS Code), or any MCP-enabled IDE to:
No more manual YAML editing or searching through documentation - just describe what you want in natural language!
Example: "Install smart climate control for my radiators" → AI creates 10+ automations, helpers, sensors, and scripts optimized for YOUR TRVs.
Built on Model Context Protocol and powered by HA Vibecode Agent.
✅ Read your full configuration — entities, automations, scripts, helpers
✅ Understand your devices — capabilities, relations, and usage patterns
✅ Learn existing logic — analyze how your current automations and scripts behave
✅ Create complete systems — multiple interconnected automations in seconds
✅ Generate helpers and sensors — tailored to your actual setup and needs
✅ Write optimized scripts — based on real entities, areas, and devices
✅ Refactor existing logic — improve or merge automations instead of starting from scratch
✅ Create and update Lovelace dashboards — fully programmatically
✅ Add, remove, or rearrange cards — stat, graphs, history, custom cards, and more
✅ Control layouts and views — organize rooms, areas, and scenarios
✅ Design and tweak themes — colors, typography, and styles for a personalized UI
✅ Git-based versioning — every change is tracked with meaningful commit messages
✅ Human-readable commits — AI explains what changed and why
✅ Configuration validation — test before apply to reduce breaking changes
✅ One-click rollback — revert to a previous state if something goes wrong
✅ Activity log — full audit trail of what the agent did and when
✅ Install and configure HACS — unlock 1000+ community integrations
✅ Search repositories — themes, plugins, custom components, dashboards
✅ Install integrations — one-command setup for new HACS components
✅ Keep things fresh — update all HACS repositories from a single place
Result:
You describe your goal → AI inspects your Home Assistant → designs a custom solution → and deploys it on-board automatically. 🚀
Most MCP integrations I’ve seen for Cursor, VS Code or Claude work only on your local machine and talk to Home Assistant over SSH and sometimes the REST API.
For serious Home Assistant work, that’s not really enough:
Home Assistant is not just a bunch of YAML files. It exposes multiple internal APIs, and some of the most important ones are only available from inside HA itself over the WebSocket API.
When you access HA only via SSH, the AI usually has to generate and upload a helper script on every request, then execute it blindly on the host. Since that script can be different every time, each request is a bit of a black box — more like playing Russian roulette than doing reliable automation.
Because of that, I chose a different architecture.
This project is split into two modules:
Home Assistant Agent (this module) – runs inside Home Assistant (as an add-on), has native access to all relevant APIs, files and services, and exposes a safe, well-defined interface for external tools.
Home Assistant MCP server – runs on your computer alongside your AI IDE (Cursor, VS Code, etc.) and talks to the Agent over a controlled API instead of SSH hacks (installation steps below)
This design makes working with Home Assistant faster, more predictable, safer and repeatable. Your AI IDE gets exactly the actions and data it needs — through a stable API — instead of constantly inventing ad-hoc scripts and hoping they behave correctly.
Before installing, you need:
The MCP server requires Node.js to run on your computer (where your AI editor is installed):
node --versionnode --version should show v20.0.0 or higher (v24 LTS recommended)Install the agent in your Home Assistant from :
https://github.com/Coolver/home-assistant-vibecode-agentGet configuration from Home Assistant:
Verify everything works:
Open your AI editor (Cursor, VS Code, etc) and send this message to AI:
Connect to my Home Assistant and show me:
1. List of all my climate entities
2. Current status of the HA Vibecode Agent
This will verify the MCP connection is working.
If AI successfully returns your entities and agent status, you're all set! ✅
Troubleshooting: If connection fails:
Just describe what you want in natural language - AI will handle the rest!
If your agent runs on a different URL:
{
"mcpServers": {
"home-assistant": {
"command": "npx",
"args": ["-y", "@coolver/home-assistant-mcp@latest"],
"env": {
"HA_AGENT_URL": "http://<home-assistant-host>:8099",
"HA_AGENT_KEY": "your_api_key_here"
}
}
}
}
mcp.json (under HA_AGENT_KEY)curl http://homeassistant.local:8099/api/healthHA_AGENT_URLThis error means Node.js is not installed or not found in your system PATH.
Solution: Install Node.js (v20.0.0 or higher; v24 LTS recommended) on the computer where Cursor is running:
node --version in a terminalImportant: Node.js must be installed on your computer (where Cursor, VS Code, Claude or other IDE runs), not on the Home Assistant server.
mcp.json with your Agent Key to git!MIT © Vladimir Eremeev
home-assistant-mcp/
├── package.json # NPM package config
├── tsconfig.json # TypeScript config
├── src/
│ ├── index.ts # MCP server entry point
│ ├── ha-client.ts # HA Agent API client
│ ├── handlers.ts # Tool request handlers
│ ├── tools.ts # Legacy tool definitions
│ └── tools/ # Modular tool definitions
│ ├── index.ts # Tool exports
│ ├── files.ts # File operation tools
│ ├── system.ts # System operation tools
│ └── dashboard.ts # Dashboard tools
├── build/ # Compiled JavaScript output
├── README.md
├── CHANGELOG.md
└── QUICK_START.md
MCP Server (index.ts) ← Communication Protocol
↓
Tool Handlers (handlers.ts) ← Business Logic
↓
HA Client (ha-client.ts) ← HTTP API Wrapper
↓
HA Vibecode Agent (https://github.com/Coolver/home-assistant-vibecode-agent) (REST API) ← Home Assistant Integration
Contributions are welcome! Please feel free to submit a Pull Request.
git checkout -b feature/AmazingFeature)git commit -m 'Add some AmazingFeature')git push origin feature/AmazingFeature)Give a ⭐️ if this project helped you control your smart home with AI!
Vibecode your Home Assistant setup from your IDE: automations, dashboards, themes and configs
{ "mcpServers": { "io.github.coolver-home-assistant-mcp": { "command": "npx", "args": [ "-y", "@coolver/[email protected]" ], "env": { "HA_AGENT_URL": "<value>", "HA_AGENT_KEY": "<secret>" } } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: HA_AGENT_URL, HA_AGENT_KEY.
Home Assistant läuft lokal über stdio.
Zuletzt geprüft: 2026-11-09. Vibecode your Home Assistant setup from your IDE: automations, dashboards, themes and configs