Home Assistant MCP Server vs three.ws Home
Home Assistant MCP Server is an MCP server published by jarahkon. Marketplaces we read that list it: 1 (Official MCP Registry). three.ws Home is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Home Assistant MCP Server |  three.ws Home |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.6 Downloads/month (npm): 672 Downloads/week (npm): 180 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 75 Downloads/week (npm): 16 Forks (GitHub): 76 Stars (GitHub): 273 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Home Assistant MCP Server | three.ws Home |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 273 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 76 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@jarahkon/hass-mcp-server) | On your machine (@three-ws/home-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 2 | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/jarahkon/hass-mcp-server | github.com/nirholas/three.ws |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Home Assistant MCP Server
MCP server for full Home Assistant control — dashboards, files, automations, add-ons, and more
three.ws Home
Read and safely act on a real Home Assistant house: rooms, live state, scenes, gated actions.
How to run each
Home Assistant MCP Server As a local MCP server: npm package
claude mcp add --env "HA_SSH_PASSWORD=<YOUR_HA_SSH_PASSWORD>" --env "HA_TOKEN=<YOUR_HA_TOKEN>" --env "HA_URL=<YOUR_HA_URL>" --transport stdio hass-mcp-server -- npx -y @jarahkon/hass-mcp-serverRequires: HA_SSH_PASSWORD (secret), HA_TOKEN (secret), HA_URL
three.ws Home As a local MCP server: npm package
claude mcp add --env "HOME_ASSISTANT_TOKEN=<YOUR_HOME_ASSISTANT_TOKEN>" --env "HOME_ASSISTANT_URL=<YOUR_HOME_ASSISTANT_URL>" --transport stdio home-mcp -- npx -y @three-ws/home-mcpRequires: HOME_ASSISTANT_TOKEN (secret), HOME_ASSISTANT_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Home Assistant MCP Server asks for
HA_SSH_HOSTHA_SSH_KEY_PATHHA_SSH_PASSWORD (secret)HA_SSH_PORTHA_SSH_USERHA_TOKEN (secret)HA_URL
Only three.ws Home asks for
HOME_ALLOWED_ENTITIESHOME_ASSISTANT_TOKEN (secret)HOME_ASSISTANT_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Home Assistant MCP Server · What it can do: three.ws Home · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.