Mcp Homeassistant
Control and inspect your Home Assistant instance from an AI agent via REST so automations, entities, and states are queryable in natural language.
Overview
io.github.daedalus/mcp-homeassistant is a MCP server for the Operate phase that proxies Home Assistant REST API calls to your coding agent.
What is this MCP server?
- MCP server wrapping Home Assistant REST API for agent-driven reads and actions
- PyPI package `mcp-homeassistant` v0.1.0 with stdio transport
- GitHub source: daedalus/mcp-homeassistant
- Bridges smart-home ops into the same MCP config as your coding agents
- Integration server—requires your own HA URL and long-lived access token
- PyPI package identifier: mcp-homeassistant
- Published server version: 0.1.0
- Transport: stdio MCP
What problem does it solve?
You toggle devices and read sensors through dashboards and curl, but your agent cannot safely reach your HA instance during debugging or ops chats.
Who is it for?
Builders who self-host Home Assistant and want MCP-driven visibility and control from Claude Code or Cursor while iterating on automations or hardware demos.
Skip if: People without a Home Assistant deployment, or teams that need official cloud-only smart-home SaaS with no self-hosted API.
What do I get? / Deliverables
After registration, your agent can query and act on Home Assistant through MCP tools backed by your REST token and base URL.
- MCP tools mapped to Home Assistant REST operations
- Agent-accessible entity/state inspection and service calls
- Documented connection using your HA base URL and token
Recommended MCP Servers
Journey fit
Home Assistant is live home or lab infrastructure you run day to day—Operate fits better than one-off Build spikes unless you are only prototyping integrations. Infra subphase matches self-hosted automation stacks, entity/state ops, and keeping personal or office smart environments running alongside your product.
How it compares
Home Assistant REST MCP bridge, not a generic IoT firmware flasher or HA blueprint authoring skill.
Common Questions / FAQ
Who is io.github.daedalus/mcp-homeassistant for?
Indie makers and operators who already run Home Assistant and use MCP agents to inspect entities, run services, or troubleshoot automations.
When should I use io.github.daedalus/mcp-homeassistant?
During Operate when you maintain live automations, debug entity states, or script repetitive HA tasks from your agent workspace.
How do I add io.github.daedalus/mcp-homeassistant to my agent?
Install `mcp-homeassistant` from PyPI, configure stdio MCP with your Home Assistant URL and long-lived access token, then reload your MCP client.