Home Assistant runs on your own machine — the client starts it, so there is no endpoint to ping. 563 installs a week from npm. Last commit 7 Nov 2026.
Read your Home Assistant's states, areas and history, and run its actions, approving locks first.
We read the source, 19 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add home-assistant -e 'HOME_ASSISTANT_URL=<HOME_ASSISTANT_URL>' -e 'HOME_ASSISTANT_TOKEN_FILE=<HOME_ASSISTANT_TOKEN_FILE>' -- npx -y @foreverworks/mcp-home-assistant
{
"mcpServers": {
"home-assistant": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-home-assistant"
],
"env": {
"HOME_ASSISTANT_TOKEN_FILE": "<HOME_ASSISTANT_TOKEN_FILE>",
"HOME_ASSISTANT_URL": "<HOME_ASSISTANT_URL>"
}
}
}
}
[mcp_servers.home-assistant]
command = "npx"
args = ["-y", "@foreverworks/mcp-home-assistant"]
env = { HOME_ASSISTANT_URL = "<HOME_ASSISTANT_URL>", HOME_ASSISTANT_TOKEN_FILE = "<HOME_ASSISTANT_TOKEN_FILE>" }
{
"mcpServers": {
"home-assistant": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-home-assistant"
],
"env": {
"HOME_ASSISTANT_TOKEN_FILE": "<HOME_ASSISTANT_TOKEN_FILE>",
"HOME_ASSISTANT_URL": "<HOME_ASSISTANT_URL>"
}
}
}
}
{
"servers": {
"home-assistant": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-home-assistant"
],
"env": {
"HOME_ASSISTANT_TOKEN_FILE": "<HOME_ASSISTANT_TOKEN_FILE>",
"HOME_ASSISTANT_URL": "<HOME_ASSISTANT_URL>"
}
}
}
}
Put your own values in place of
<HOME_ASSISTANT_URL> (The address you open Home Assistant at, such as http://homeassistant.local:8123), <HOME_ASSISTANT_TOKEN_FILE> (Path of a file holding a long-lived access token made in an administrator's Home Assistant profile).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
HOME_ASSISTANT_CONFIRM_DOMAINS (Action domains you approve call by call, comma-separated (default lock,alarm_control_panel,cover,valve; none for none)).
Give any AI assistant real-time access to your phone's GPS and location history.
Query your Logspot analytics, companies, and revenue from any AI assistant, and run your actions.
Read and safely act on a real Home Assistant house: rooms, live state, scenes, gated actions.
Training log for coaches: your AI assistant finds clients, reads history, logs and plans workouts.
Shared, living memory for you and your people — coves your AI assistant can read and write.
Read your Spellar meetings, transcripts and action items from an AI assistant, and update them.
Lets AI assistants read your Softspoken meetings and tick off, snooze or set due dates on actions.
Your AI assistant reads today's one action to find customers, your context, and logs results.
Answers built from our own checks of this server.