get_state
Get the current state of a Home Assistant entity
LABSCO SUMMARY
Four operations, no ceremony.
This is the minimum surface that makes a smart home addressable from a chat window, and the smallness is the point — there is no device model to learn, only entity ids and states. What it does not give you is anything Home Assistant does beyond entities and automations: no scenes, no scripts, no history, no service calls with arbitrary payloads.
What it is
A small MCP server that talks to a Home Assistant instance over its REST API using a long-lived access token. It covers the four operations a household assistant actually needs: look up an entity's state, turn something on or off, run an automation, and enumerate the entities available.
What you get
- The current state of one entity by its entity id, such as a light or a sensor —
get_state - An entity switched on or off by id —
toggle_entity - An existing Home Assistant automation fired by its automation id —
trigger_automation - The entities on the instance listed, optionally narrowed to one domain such as lights —
list_entities
Requirements
A running Home Assistant instance and a long-lived access token from it: HA_URL points at the instance, HA_TOKEN carries the token. The npm package name is homeassistant-server (0.1.0) and it is marked private, so the install path is a clone plus npm install and npm run build, then pointing your client at the built index.js. Serve Home Assistant over HTTPS before handing the token to anything, since the token grants whatever your account can do.
Setup effort
Add the configuration to your client
USE CASES
01
Checking whether something is on before you leave
Ask for the state of a specific entity id and get Home Assistant's own answer back, rather than opening the app.
02
Turning devices on and off by name
List the entities in the light or switch domain to find the id you want, then set it on or off.
03
Running a routine on demand
Fire an automation you already built in Home Assistant — a morning routine, a leaving-the-house sequence — without waiting for its trigger.
04
Finding out what the house actually exposes
Enumerate entities, filtered to one domain, to see which ids exist before writing anything that depends on them.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list_entities
List all available entities in Home Assistant
toggle_entity
Toggle a Home Assistant entity on/off
trigger_automation
Trigger a Home Assistant automation
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. toggle_entity switches entities on or off and trigger_automation runs existing automations; setting temperature or brightness, calling arbitrary Home Assistant services and editing automations are not supported.
Requires
- node on PATH
- HA_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
MCP Clients
Cline
CLINE · JSON
{
"mcpServers": {
"homeassistant": {
"command": "node",
"args": [
"<YOUR_PATH_TO_HOMEASSISTANT_MCP>/homeassistant-server/build/index.js"
],
"env": {
"HA_URL": "http://<YOUR_HOMEASSISTANT_URL>:8123",
"HA_TOKEN": "<YOUR_HA_TOKEN>"
}
}
}
}
