Integrations · Smart home
Home Assistant agents via MCP on VegaDūta
VegaDūta connects AI agents to Home Assistant through a first-party open MCP connector — a zero-dependency stdio MCP server that exposes three tools: list entities, get entity state, and call service. With those three, an agent can discover your smart-home devices, read what they are doing, and act on them — turn things on and off, adjust settings, run any Home Assistant service. Because it speaks Model Context Protocol, it plugs into the same MCP connector registry as every other MCP server on the platform.
Three tools, full coverage
The connector is deliberately small: three tools that map onto how Home Assistant itself is organized, which together cover read and control of the whole installation.
- List entities — discover every device and sensor Home Assistant knows about.
- Get entity state — read the current state of any entity.
- Call service — invoke any Home Assistant service to control devices.
Zero-dependency, first-party, open
The connector is a zero-dependency stdio MCP server built and maintained as part of VegaDūta — no third-party bridge to trust, nothing extra to install alongside it. It registers through the platform's MCP connector flow like any other server.
Smart home meets messaging channels
The interesting part is the combination: the agent that controls your home is the same agent reachable over WhatsApp or Telegram. Ask it what the temperature is, tell it to switch something off — from a chat. Tool calls run under the platform's guardrails, and you can put device control behind human approval gates.
Frequently asked questions
Can an AI agent control Home Assistant devices?
Yes. VegaDūta's first-party MCP connector gives agents three tools — list entities, get entity state, and call service — which cover discovering devices, reading their state, and invoking any Home Assistant service to control them.
What is the Home Assistant MCP connector, technically?
A zero-dependency stdio MCP server, built first-party and open, that bridges the Model Context Protocol to Home Assistant's entity and service model. It registers in VegaDūta's MCP connector registry like any other MCP server.
Can I control my smart home from WhatsApp?
Yes, indirectly by design: attach the Home Assistant connector to an agent, attach that agent to WhatsApp, and you can read states and call services from a chat. Approval gates can require confirmation before the agent acts on devices.
Is smart-home control by an AI agent safe?
Tool calls run under VegaDūta's guardrails, and human approval gates let you require sign-off before a service call executes. You choose which agents carry the connector and which actions need a person in the loop.
See it working in two minutes
The sandbox provisions a real tenant — describe an agent in one sentence and test it, no account, no card. Or browse ~90 industry workflow recipes to see what teams build.
