ha-mcp
The Unofficial and Awesome Home Assistant MCP Server
Runs with mockssource: GitHubhomepagePythonMITcommit 58e31c7176fa
Python, MIT licensed. The project labels itself: ai, claude, hacs, home assistant, home automation, llm, mcp and model context protocol.
ha-mcp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, smoke test passes, and the full unit test suite passes (11,790 passed, 357 skipped, 0 failed).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- git submodule 'skills-vendor' not initialized — caused 3 test_helper_response_shape tests to fail1 minute
- Install time
- 7 minutes
- Cold machine to finish
- 70 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- Model tokens used
- 290,831
- Exact commit tested
- 58e31c7176fa
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **Server launch**: Requires real Home Assistant credentials (HOMEASSISTANT_URL + HOMEASSISTANT_TO… tokens used 290,831 Here's my full report. **Environment**: Container has Python 3.12, but the project requires >=3.13. I installed Python 3.1… **Install**: Ran `uv sync --group dev` successfully. All 129 dependencies resolved and installed in… **Error found & fixed**: `git submodule update --init` was needed for `src/ha_mcp/resources/skills-… **Verification**: - **Smoke test**: All 6 critical libraries imported, server instantiated, 78 tools discovered — pas… - **Unit tests**: 11,790 passed, 357 skipped, 0 failed in 413s (2 workers). - **Skipped tests**: 240 JS (jsdom not installed), 12 locale completeness (env var), 1 numpy, 1 Win… - **Server launch**: Requires real Home Assistant credentials (HOMEASSISTANT_URL + HOMEASSISTANT_TO…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 4 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 7 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, ha-mcp was the 22nd fastest to reach a running state, and 30 of 37 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.19 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.19 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.06 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.09 |
Topics (from GitHub)
aiclaudehacshome-assistanthome-automationllmmcpmodel-context-protocol
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ha-mcp)Questions
- Does ha-mcp run?
- ha-mcp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test ha-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 58e31c7176fa. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ha-mcp?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ha-mcp take to install?
- 7 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ha-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ha-mcp?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ha-mcp compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, ha-mcp was the 22nd fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for ha-mcp?
- All 4 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.