HA NOVA MCP server
Commit Nov 15, 2026Connects AI clients to Home Assistant to control devices, manage automations, and build dashboards with a safety-first confirmation system.
Also known as markusleben/ha-nova, ha-nova
- Stars
- 20
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.31.0
- Last commit
- Nov 15, 2026
- License
- MIT
What is HA NOVA MCP?
HA NOVA connects AI clients to Home Assistant to control devices, manage automations, and build dashboards with a safety-first confirmation system.
Summary generated from the project's README
How to install HA NOVA MCP
HA NOVA gives each account its own endpoint, so there is no address to copy here. Get yours from the provider, put it in place of the part in braces, and add it to your client as a remote server.
https://{home_assistant_address}/api/ha_nova/mcp
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemarkusleben/ha-nova is public and reachablegithub.com/markusleben/ha-nova ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/markusleben/ha-nova ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeEndpoint did not answer initialize: unreachableFinding
README
View on GitHub"When I get home, set my main lights to a warm welcome scene": you say one sentence and get a checked automation, plus ideas you might not have thought of.
✦ Three steps to connect
- Run the installer. Copy one command. Setup opens a page in your browser and finds your Home Assistant and your AI apps.
- Sign in with Home Assistant. Sign in as the owner: the first account made when Home Assistant was set up. If needed, setup installs and starts the NOVA Relay App for you. Then this computer connects by itself.
- Choose your safety net, then look around. Unlocks and deletes wait for your OK on your linked phone or the NOVA page; the confirmation window on this computer asks for dashboard and room changes. To add a phone, pick whose phone should confirm on this computer: setup lists the phones Home Assistant tracks for an administrator's person. On a re-run, Use another phone moves it: the old phone OKs the move, then the new phone taps "Allow". If you use Claude Code, its rules are on unless you turn them off: they let Claude Code read HA NOVA's files and make changes you already approved, without asking again. You still confirm every unlock or delete. Then you see your home at a glance: things worth a look (like a low battery or devices without a room) and an automation made for your home, to preview and save. Nothing in your home changes unless you save it.
Signed in, but not as the owner? The page asks the owner to sign in here, or to make a six-digit code for you (details). Over SSH or with --no-browser, setup asks in the terminal instead. No browser here? Then setup shows the NOVA Relay App page (click "Add", then Install and Start; skipped when the App already runs). You pair with a six-digit code: the Home Assistant owner clicks "Connect a device" on the NOVA page in the sidebar, and you type the code. Over SSH, this works well on Linux only. On Windows and macOS, run setup in a terminal on that computer's own screen: over SSH, HA NOVA usually can't save its key.
The code works once, for 10 minutes. The sign-in works once too. Each device gets its own connection, and you can cut it off anytime on the NOVA page.
Still young, and growing fast. The main steps are tested end to end on macOS, Linux, and Windows, and your feedback still shapes the product. Back up your setup before you let AI change anything. Hit a problem? Open an issue.
💬 What You Can Do
Say what you want. HA NOVA works out the rest.
| You say | What happens |
|---|---|
| "Check my automations for problems" | Checks them against 40+ rules. Finds conflicts, triggers that never fire, and mistakes that are easy to miss |
| "Why didn't my motion light trigger last night?" | Replays what really happened and tells you where it stopped and why |
| "Turn on the porch light at sunset and off at 11 PM" | Builds the automation, shows it to you, and checks it before anything is saved |
| "What happened to my living room temperature overnight?" | Reads the history and sums it up in plain words |
| "Build a dashboard for the living room" | Builds whole dashboards and views, also with custom cards you installed. It lists every view and card that changes and saves a copy first. "Undo that" brings the old one back |
| "Move all kitchen devices to the Kitchen area" | Moves the devices and entities and shows what will change first. Moving a device with a lock, alarm panel, garage door, or gate takes your own confirmation |
| "Turn off the integration I don't use anymore and fix the open repairs" | Turns integrations on or off, renames or removes them, fixes or ignores repairs, and changes users, general settings, and the backup schedule. Shows what changes first. Deletes and sensitive changes take your own confirmation. Turning off a lock's device or integration, or removing the integration or switch it runs on, is refused. A step that asks for a password, PIN, or key finishes in Home Assistant |
| "Why does my MQTT broker App keep restarting?" | On HA OS, checks the App's state, version, and settings, and asks you for the lines that matter from its log page in Home Assistant: HA NOVA doesn't read logs, which can hold passwords. It can also install or remove an App, or change its settings, after your own confirmation. This needs HA NOVA's local connection, not Home Assistant Link |
| "Turn off the kitchen light" | Turns it off right away and checks that it really is off. A room's lights work the same way, up to 30. Everything else in a room, scenes, and riskier actions show a preview first |
| "Unlock the front door" | Shows what will happen, then waits for your OK: a tap on your linked phone, or Approve on the NOVA page in Home Assistant (in Claude and ChatGPT: the linked phone, or a four-digit code at Manage everything with codes on) |
| "What do I have, and where is this sensor used?" | Counts rooms, devices, automations, and integrations itself. Lists the automations, scripts, scenes, groups, helpers, and dashboard cards that use a sensor, and says what it couldn't check. Exact numbers, never a guess |
| "My door sensor died, I paired a new one" | Moves automations, scripts, scenes, dashboards, helpers, and energy sources to the new device in one plan you check first |
| "Turn this Node-RED flow into an automation" | Lists what the rule does, matches each device to a real entity, and builds a Home Assistant automation. HA NOVA tells you how to turn the old flow off, and never deletes it |
| "Check my ESPHome config for the garage sensor" | Explains the device file in plain words. Flags removed settings, pins that can't do what the file asks, and passwords written in the file |
| "Remind me in 20 minutes to check the oven" | Makes a one-time reminder that turns itself off after it runs |
| "Show me all temperature sensors" | Finds entities by name, room, area, or label |
| "What's the average temperature upstairs?" | Works out averages and totals across rooms in one step. Names the sensors it used and any it couldn't read |
Automations and scripts get the full treatment today: a preview, a review, and a check against 40+ rules. Helpers get a preview and a check afterwards. Dashboards get a preview of every changed view and card, a copy before each save, and undo. Device control runs clear everyday actions right away and checks them afterwards. Everything else shows a preview first. Unlocks, opening gates and garage doors, turning off the alarm, deletes, HACS installs and updates, and dashboard resources need your OK.
🛡️ Safe by Design
We built this because we didn't trust AI with our own setup either.
What happens when AI wants to change something:
-
Looks first. Finds your devices, checks your setup, and finds the right names. No guessing.
-
Shows you the change. A clear before-and-after table of what will change, in plain words with names, before anything is saved. The one exception: clear everyday actions run right away, like "turn off the kitchen light", switching a room's lights, pausing music, or adding to a to-do list. HA NOVA checks them afterwards. The HA NOVA program decides which actions count, never the AI. And it sends nothing if anything changed since a preview.
-
You approve it. Unlocking a door, opening a gate or garage door, turning off the alarm, restarting Home Assistant, and deletes need a real confirmation, not just "yes" in the chat. Before a restart, HA NOVA checks your config first. If something is wrong, it says what before you confirm.
- On your linked phone, a notification shows the action's button. Press and hold it on an iPhone, or pull it down on Android, then tap the button. This needs the Home Assistant Companion app.
- On the NOVA page, open NOVA in the Home Assistant sidebar. Under "Waiting for your OK", choose Open, then Approve or Cancel. Any Home Assistant administrator can approve there, except the user the NOVA App signs in as; other administrators find the link "Requests waiting for your OK" when they open NOVA. The OK covers exactly that change, once. Nothing is sent before it, and a request no one answers ends after 3 minutes.
- The window on your computer only waits. It says where to confirm, opens Home Assistant, or cancels; it can't confirm. Dashboard and room changes still ask on the computer: click Confirm (OK on Windows) or Cancel in the window, or type a four-digit code where no window opens.
- About the phone: you can answer on the phone or its Apple Watch without unlocking it. So whoever holds your phone can answer while a request is open, for up to 3 minutes. It works only for that one action. To link or move phone confirmation, you need the unlocked phone. The phone you linked on a computer moves into Home Assistant once: the first time a change needs your OK, it asks whether it should get HA NOVA's confirmations. To link or change a phone, run
ha-nova setup confirm-phone. Itsoffstops only this computer's own asks: the NOVA App keeps asking that phone for this computer's unlocks and deletes. Chat apps keep their own phone: change or stop it on the NOVA page. When setup links the owner's new phone right after the owner signs in, it offers to move chat apps too. It is never moved to the chat. - In Claude and ChatGPT, the linked phone of whoever asked confirms. With no phone, at Manage everything, you get a four-digit one-time code, in the app's own form where it shows one, or else in the chat. In the chat, the AI sees the code too and HA NOVA can't tell who typed it, so it protects less than your phone.
- Deletes: deleting an automation, script, device, integration, blueprint, helper, scene, area, floor, or label waits for the same OK. A dashboard delete asks on the computer. Up to 20 automation and script changes and deletes can share one confirmation. Other batch deletes you checked take one confirmation for the exact list of items.
- Language: confirmations are in German when Home Assistant is set to German, else in English. In a German home, the window's button reads „Bestätigen“ (OK on Windows), a phone link „Erlauben“, and the phone's button names the action, like „Entriegeln“ or „Löschen“.
- Screen control: anything you let control your screen can click that window too. That means computer use, apps you gave Accessibility access, and on Windows and some Linux desktops, other programs. To turn the window off, run
ha-nova setup confirm-window off.
-
Saves a copy first. Before a covered delete or a full replacement of a config, HA NOVA saves a copy of that item. So "gone" has a way back.
-
Saves and checks. Reads the config back to make sure the change stuck.
-
Checks its own work. Looks for mistakes, conflicts, and things that could fail.
-
Offers a safe test. After you save a new or changed automation or script, you get a test plan that fits the risk. It can be a check that changes nothing, or a real run that names every device that will switch before you say go.
-
Offers a way back, in three steps.
- Reply
revertto undo the latest checked update. - Bring back a deleted automation, script, scene, dashboard, or storage helper from its saved copy (a config snapshot), with the same preview and confirmation. "Undo that" right after a delete works, and so does "restore the kitchen automation you deleted yesterday".
- For everything else, use a Home Assistant backup.
revertand saved copies cover only changes made through HA NOVA. HA NOVA can't undo changes made in the Home Assistant UI, by other tools, or by hand in YAML. A saved copy brings back the item itself, not every place that used it. Home Assistant backups cover the whole system. - Reply
The ground rules, always:
- 🔒 The Relay's login stays out of the AI. The App's Home Assistant login stays inside the Relay. Optional Link access uses a separate Home Assistant OAuth authorization in this computer's native credential store. The AI sees neither of them.
- 🙈 Stored codes stay hidden from the AI. A lock or alarm code saved in its settings, the backup password, and the Thread network key reach the AI only as "hidden", also in HA NOVA's saved copies. Camera and image sign-in tokens stay hidden too. Codes written into automations are not hidden.
- 🔑 Each device is paired on its own. The Home Assistant sign-in and the six-digit code work once and run out fast. They create a separate login for each device, over an encrypted connection that trusts only your own Relay. How it works: safety page. This is for App installs. The standalone container uses one shared token instead.
- 🗑️ Cut off a device in two clicks (App installs). Lost a laptop? Retired a computer? On the NOVA page, choose "Revoke…" next to it, then "Revoke this device". Everything else keeps working.
- 📖 Every skill the AI follows is a Markdown file you can read. Chat apps also get a short guide built into the program.
- 🏠 HA NOVA runs no cloud relay, and the program sends no usage data or install counts. Local mode stays between your computer and Home Assistant. Optional Link mode uses your own Home Assistant Link service, and HA NOVA gets none of that traffic.
🚀 Get Started
One command. One setup page. One sign-in. It even finds your Home Assistant for you.
You need: Home Assistant, any install type. HA OS and Supervised get the NOVA Relay App, and setup helps you install it. Container and Core run the same relay as a standalone container: same skills, but no pairing, no NOVA page (only a linked phone confirms), no chat apps, and no Home Assistant Link. It works with a token instead, so skip the steps below and follow that guide from start to end.
macOS / Linux:
curl -fsSL https://raw.githubusercontent.com/markusleben/ha-nova/main/install.sh | bash
Windows (PowerShell):
irm https://raw.githubusercontent.com/markusleben/ha-nova/main/install.ps1 | iex
The installer selects the latest stable release. Run the command for your system.
On a desktop, setup goes on in your browser. The page shows the Home Assistant it found, or asks for its address. It also shows the AI apps on this computer and sets them up for you. On HA OS and Supervised, choose "Sign in and install NOVA" and sign in as the owner. Setup then installs and starts the NOVA Relay App and connects this computer, all with that one sign-in. An old App is updated the same way. If an up-to-date App already runs, the owner still signs in once, to connect this computer. Then choose how you confirm risky changes, and see your home at a glance.
Only use Claude or ChatGPT in the browser? With no AI app on this computer, choose "I use Claude or ChatGPT in the browser" on the setup page. This needs Home Assistant 2026.10 or newer on HA OS or Supervised, and Home Assistant Link with remote access on, or your own HTTPS address (see Use HA NOVA in Claude and ChatGPT). Right after the owner signs in, setup checks the version, HA OS, and that an internet address is set, before it changes anything. If something is missing, the page says what and offers "Set it up, then check again" or "Use HA NOVA on this computer instead" (on Container or Core, only the second). If all is ready, this computer connects, and chat apps come first.
Not the owner? The page asks the owner to sign in. If the owner can't come to this computer, they make a six-digit code in NOVA in Home Assistant ("Connect a device"), and you type it in the terminal. Can't sign in on this computer at all? Choose "Use a six-digit code instead". The owner can make it on any device. On the browser-only path there is no code: the owner signs in here.
In the terminal. Over SSH or with ha-nova setup --no-browser, setup asks in the terminal instead.
Run setup again any time. "Your setup" then shows what is done and what you can still do, each with a button.
- Want to install the App yourself, or no browser sign-in here (for example over SSH)? Setup takes you to the App page and adds the repository for you. Click "Add", then Install and Start.
- After that, or when the App already runs, setup opens your Home Assistant login. Sign in as the owner, and this computer connects by itself.
- Signed in as another Home Assistant user? Setup offers to sign in again or to use a code. Over SSH on Linux, or when the sign-in didn't work, setup asks for a code. The owner opens NOVA in the sidebar (or "Open Web UI" on the App page) and clicks "Connect a device". You type the six-digit code.
- On Windows and macOS, run setup in a terminal on the computer's own screen, not over SSH.
After pairing, setup asks whose phone should confirm on this computer: pick it, then tap "Allow" on that phone (in the terminal, you OK it in the window first, where one opens). To move it later, the old phone OKs first, then the new one taps "Allow". The phone must be signed in to the Home Assistant app as an administrator. Setup ends with a first look at your home.
Try it first? Try HA NOVA in 1 minute on a shared demo house with no real devices. There is nothing to install. In Claude, a free account works. ChatGPT needs a paid plan that lets you add your own plugins. We tested Pro. The free plan can't. On a phone, ChatGPT can only answer. On your computer,
ha-nova tryconnects your AI app to it (the setup page offers it when it finds no Home Assistant), andha-nova try --stopremoves it. Everyone shares one login, and it resets every hour. So never enter real names, passwords, or tokens there. What the demo keeps: privacy page.
HA NOVA MCP questions
How does HA NOVA ensure safety when making changes?
It uses a multi-step process: it finds exact device names without guessing, shows a before-and-after preview of changes, and requires manual confirmation for risky actions like unlocking doors or deleting items.
Does it require a computer to be running constantly?
No, it can work with the NOVA Relay App so that no computer needs to be running to use it with Claude or ChatGPT.