MCP ConfigsMay 11, 2026·2 min read

Home Assistant MCP — Control Home Assistant from Agents

Home Assistant MCP exposes smart-home actions as MCP tools so agents can query state and trigger automations via a controlled, auditable interface.

MCP Hub
MCP Hub · Community
Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
Mcp Config
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install a49fe6ac-e9c4-4f78-9ac2-2ab526d5d90c --target codex

Stages files first; activation requires review of the staged README and plan.

Intro

Home Assistant MCP exposes smart-home actions as MCP tools so agents can query state and trigger automations via a controlled, auditable interface.

  • Best for: Home Assistant users who want agent-driven status checks and automations without giving the agent full UI access
  • Works with: An MCP-capable agent client + a Home Assistant instance (credentials per repo docs)
  • Setup time: 20 minutes

Practical Notes

  • Setup time ~20 minutes (credentials + run server + connect client)
  • Safety check: keep write actions disabled until read-only calls are stable
  • GitHub stars + forks (verified): see Source & Thanks

Treat smart-home tool calls like production ops. Define ‘safe defaults’ (read-only), then add a small set of allowed writes with guardrails. If your agent can’t explain why it’s turning something on, it shouldn’t be allowed to do it.

FAQ

Q: Can I let an agent control everything? A: You can, but start with read-only tools and explicitly whitelist safe actions.

Q: How do I prevent accidental triggers? A: Require confirmations for writes, and add rate limits / time windows for automations.

Q: Is this better than UI automation? A: Yes for reliability: tool calls are structured and auditable, unlike fragile UI clicks.

🙏

Source & Thanks

Source: https://github.com/homeassistant-ai/ha-mcp > License: MIT > GitHub stars: 2,807 · forks: 114

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

home-assistant-vibecode-agent — MCP Agent for Home Assistant

Home Assistant Vibecode Agent exposes automations, dashboards, configs and HACS via MCP for AI IDEs. Verified 548★; pushed 2026-05-14.

MCP Configs
MCP Hub

Unity MCP — Control Unity Editor from Agents

Unity MCP bridges MCP clients to your Unity Editor so assistants can manage scenes, assets, scripts, and builds via tools instead of manual clicking.

MCP Configs
MCP Hub

MCP Gateway & Registry — Team Tool Control

MCP Gateway & Registry centralizes MCP servers and agent tools with auth, search, and audit, so teams can manage integrations and scan servers before use.

MCP Configs
MCP Hub

AskDB — Safe DB Clone + MCP for Agents

AskDB clones a DB into an isolated container and exposes an MCP endpoint with field-level visibility controls; verified 55★ and pushed 2026-05-04.

MCP Configs
MCP Hub
◈Home🔍Search👤Me