Ext Ops Panel
Open dashboard
Comparison

Home Assistant Config vs three.ws Home

Home Assistant Config is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑05.

Home Assistant Config is a plugin bundle for AI coding tools published by ESJavadex. No marketplace we read lists it any more. 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-08. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceHome Assistant Configthree.ws Home
Community marketplace esjavadex/claude-homeassistant-plugins Removed on 2026-11-05
Version: 2.1.3
Forks (GitHub): 1
Stars (GitHub): 28
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (npm): 75
Downloads/week (npm): 16
Forks (GitHub): 73
Stars (GitHub): 270
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

Home Assistant Config vs three.ws Home
FactHome Assistant Configno longer listed · three.ws Home
Marketplaces that list it (differs)01
Stars (GitHub) (differs)28270
Forks (GitHub) (differs)173
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@three-ws/home-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/esjavadex/claude-homeassistant-pluginsgithub.com/nirholas/three.ws
Changes in the last 7 days (differs)100
First seen (differs)2026-10-172026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of Home Assistant Config

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • home-assistant-plugin

    Home Assistant configuration management - YAML configuration, automations, scripts, scenes, and entity management for Home Assistant installations

    by Lauri Gates · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • home-assistant-manager

    Expert-level Home Assistant configuration management: deploy workflows, SSH/hass-cli access, automation verification, and Lovelace dashboard development

    by komal-SkyNET · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • home-assistant-skills

    Best practices for Home Assistant automations, helpers, scripts, scenes, blueprints, device control, dashboards, AppDaemon apps, and backups

    by homeassistant-ai · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • hermitd-homeassistant

    Build, manage, monitor, and troubleshoot your Home Assistant setup with Hermit.

    by gtapps · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • hermitd-homeassistant

    Build, manage, monitor, and troubleshoot your Home Assistant setup with Hermit.

    by gtapps · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • @orellbuehler/homeassistant-mcp

    Model Context Protocol server for Home Assistant: introspect entities, services, events, registries, render templates and validate configuration to help AI agents author HA…

    by OrellBuehler · MCP server

    Listed on: npm registry (MCP servers) · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Home Assistant Config

In its own words, on Community GitHub marketplaces:

Write, check and modernise Home Assistant YAML (automations, scripts, templates, blueprints, dashboards) with the syntax of Home Assistant 2026

three.ws Home

In its own words, on Official MCP Registry:

Read and safely act on a real Home Assistant house: rooms, live state, scenes, gated actions.

How to run each

Home Assistant Config

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

three.ws Home As a local MCP server: npm package

Claude Code
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-mcp

Requires: 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

The marketplaces of Home Assistant Config publish no settings it asks for, so we do not compare settings.

What it can do: Home Assistant Config · What it can do: three.ws Home · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built