Cette page est affichée en anglais. Une traduction française est en cours.
MCP ConfigsMay 11, 2026·2 min de lecture

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
Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Stage only · 29/100Stage only
Surface agent
Tout agent MCP/CLI
Type
Mcp Config
Installation
Single
Confiance
Confiance : Established
Point d'entrée
README.md
Commande CLI universelle
npx tokrepo install a49fe6ac-e9c4-4f78-9ac2-2ab526d5d90c
contrat d'installationJSON metadataplan adaptateurcontenu raw
Introduction

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 et remerciements

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

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires

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

Surf CLI — Control Chrome for AI Agents (No MCP)

Surf CLI lets agents control Chrome via a local extension + native host, offering agent-agnostic browser control without running an MCP server.

CLI Tools
Script Depot

WhatsApp MCP Server — Chat with WhatsApp via AI Agents

MCP server connecting Claude and AI agents to your personal WhatsApp. Search contacts, read messages, send replies and media via natural language.

MCP Configs
MCP Hub

WinRemote MCP — Remote Windows Control Server

WinRemote MCP is a Windows MCP server you run on the target machine, exposing desktop automation, process control, and file operations to MCP clients.

MCP Configs
MCP Hub
◈Accueil🔍Rechercher👤Moi