Home Assistant MCP Server
Control Home Assistant dashboards, automations, add-ons, and config files from your agent while you build or tune a smart-home stack.
Overview
Home Assistant MCP is a MCP server for the Build phase that gives agents full control over dashboards, automations, add-ons, and HA files.
What is this MCP server?
- Broad Home Assistant control: dashboards, automations, add-ons, and related HA surfaces
- File management on the HA host via optional SSH (root user, key-based)
- Authenticated REST access with HA_URL and long-lived HA_TOKEN
- npm stdio package @jarahkon/hass-mcp-server (v1.0.6)
- Suited to home-lab operators automating repeat HA changes through MCP clients
- Package version 1.0.6 (@jarahkon/hass-mcp-server)
- Required env: HA_URL, HA_TOKEN
- Optional SSH env vars: host, port, user, key path
What problem does it solve?
Tweaking Home Assistant automations and configs through the UI is slow when you already live in an AI coding workflow.
Who is it for?
Solo builders with a self-hosted Home Assistant instance who want agent-driven automation and dashboard iteration.
Skip if: People without Home Assistant, or anyone uncomfortable granting agents token (and optional SSH) access to their instance.
What do I get? / Deliverables
You can inspect and change HA entities, automations, and optional host files from the same MCP session as your code.
- Automations and dashboard changes applied via agent tool calls
- Queryable HA entity and add-on state in agent context
- Optional file edits on the HA host when SSH is configured
Recommended MCP Servers
Journey fit
Most builders wire HA while integrating hardware and automations during build; ongoing tuning also spans operate, so primary shelf is integrations. The server is a deep Home Assistant integration (entities, automations, files), not generic monitoring or launch distribution.
How it compares
Deep Home Assistant control plane, not a generic smart-plug SDK or cloud-only IoT dashboard.
Common Questions / FAQ
Who is Home Assistant MCP for?
Home lab owners and indie developers who run Home Assistant and want MCP clients to manage automations, dashboards, and files programmatically.
When should I use Home Assistant MCP?
Use it when you are integrating or operating HA—building automations, fixing dashboards, or editing config— and want the agent in the loop instead of only the HA frontend.
How do I add Home Assistant MCP to my agent?
Install @jarahkon/hass-mcp-server, set HA_URL and HA_TOKEN, optionally configure HA_SSH_* for file tools, add the stdio server to your MCP settings, then call HA tools from your client.