Three.ws Home MCP Server

Three.ws Home is an MCP integration. Read and safely act on a real Home Assistant house: rooms, live state, scenes, gated actions.

Packages and local setup

The published npm package is @three-ws/home-mcp, version 0.1.0. Its declared MCP transport is stdio.

The package declares HOME_ASSISTANT_URL (required): Base URL of the Home Assistant instance, e.g. https://abc123.ui.nabu.casa. It has to be a URL this process can actually reach: a server outside the house cannot route to 192.168.x.x, so a LAN-only home needs Home Assistant Cloud or the household's own reverse proxy.; HOME_ASSISTANT_TOKEN (required): A Home Assistant long-lived access token (Home Assistant, your profile, Security, Long-lived access tokens, Create token). It carries the full rights of the account that minted it, so mint it from an account with only the access this agent should have.; HOME_ALLOWED_ENTITIES: Comma-separated entity ids the person running this server has pre-approved for guarded actions, e.g. lock.office_door. This is the ONLY way an action that opens the house runs over stdio, and it is deliberately a human, out-of-band decision: no tool can add to it. Per entity, never per domain. Leave unset to refuse every such action..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related hardware & iot MCP servers for tools that cover the same kind of work.