How do I connect an AI agent to my smart home in 2026?

Use the Model Context Protocol (MCP). Two mainstream servers exist as of September 2026: Google Home MCP (early access from September 16, 2026, for Google Home Premium Advanced subscribers in the US) and Home Assistant's built-in Model Context Protocol Server integration (available since Home Assistant 2025.2). In both cases you add the server URL to an MCP-capable agent — Claude (Cowork/Desktop), ChatGPT, OpenClaw, Hermes or Google Antigravity — authenticate, and the agent gains tools to list devices, read state and history, and execute control actions. Start in read-only or approval mode before allowing autonomous control.

What do I need for Google Home MCP?

A Google Home with connected devices, an active Google Home Premium Advanced subscription ($20/month or $200/year), a Google Cloud project with the Home API enabled, an OAuth consent screen configured for an external audience, a web-application OAuth client ID with redirect URIs for your agent, and an MCP client. The server URL is https://home.googleapis.com/mcp with scope home.platform.v2. Google publishes step-by-step guides for Antigravity, Claude Cowork and OpenClaw. Familiar-face data needs a separate grant from a manager of the home. Rollout is US-only, in English, over the weeks from September 16, 2026.

Is it safe to let an AI agent control my smart home?

It can be, with limits. Google Home MCP enforces rate limits and blocks sensitive actions such as unlocking doors, but Google itself warns that depending on the agent, the connection 'can result in unexpected or even undesired behavior.' Home Assistant imposes no such blacklist — you choose which entities to expose. Practical rules: expose only what the agent needs, keep locks, garage doors and alarm panels out of the exposed set, run the agent in approval mode (Claude's Manual permission setting or equivalent), review the agent's tool-call log for the first weeks, and tell other household members before connecting.

Can I use both Google Home MCP and Home Assistant MCP with one agent?

Yes. MCP clients can register several servers at once. A common 2026 setup is Home Assistant for local, vendor-agnostic device control (Zigbee, Z-Wave, Matter, Hue, Shelly and Nest via the Smart Device Management API) plus Google Home MCP for the camera event summaries and searchable video history that only Google computes. The agent sees both tool sets and picks the right one per request.

Quick Answer

How to Connect AI Agents to Your Smart Home (2026 Guide)

Published: September 17, 2026

What you are building

By the end of this guide an AI agent you already use — Claude, ChatGPT, OpenClaw, Hermes or Google Antigravity — will be able to answer “is the house secured?”, summarise what the cameras saw while you were out, turn things on and off, and build a dashboard, all through the Model Context Protocol (MCP). MCP is the open standard (created by Anthropic in November 2024, now under the Linux Foundation’s Agentic AI Foundation) that lets an agent discover and call tools from an external server. Two smart-home servers matter in 2026:

Google Home MCP — Google-hosted, covers Nest, Works with Google Home and Matter devices, early access from September 16, 2026.
Home Assistant MCP Server — runs on your own Home Assistant hub, covers thousands of integrations, shipping since Home Assistant 2025.2.

Pick one or run both.

Step 1 — Choose your agent (the MCP client)

Any client that supports remote MCP servers with OAuth works. As of September 2026 the documented options are:

Agent	Notes
Claude (Cowork / Desktop / web)	Google publishes a Home MCP setup guide for Claude Cowork; Claude’s Manual permission mode asks before every action — ideal for the first weeks
OpenClaw	Google publishes a setup guide; runs as a local agent on your own machine, so no third-party cloud between the agent and your home
Google Antigravity	Google’s own agent suite; the first-party path
ChatGPT	Supports MCP connectors; listed by TechCrunch among Home MCP clients
Hermes	Named by Google as a supported client

If you are unsure, start with the agent you already pay for. The tools are the same; the difference is how the agent decides when to call them.

Step 2A — Set up Google Home MCP

Prerequisites: a Google Home with devices, a Google Home Premium Advanced subscription ($20/month or $200/year; the $10 Standard tier does not qualify), US location, English.

Create a Google Cloud project (or reuse one) at console.cloud.google.com.
Enable the Home API in that project.
Configure an OAuth consent screen for an external audience.
Create a web-application OAuth client ID and add the redirect URIs your agent requires (Google’s guide lists them per client for Antigravity, Claude Cowork and OpenClaw).
Publish the app so the consent screen is usable outside test mode.
In your agent, add a remote MCP server with URL https://home.googleapis.com/mcp and scope home.platform.v2, supplying the client ID and secret.
Ask the agent to set it up; it will prompt you to sign in with your Google account and grant permissions.
Test read-only first: “How many lights are in the house?” and “What happened while I was out today?” exercise entity enumeration and historical analysis without touching a device.

Optional: if you want the agent to use familiar-face data, a manager of the home must explicitly grant it, and you need at least one compatible Nest camera or doorbell with familiar face detection on.

Google also offers Home Developer MCP, a separate documentation server for coding tools (Claude Code, Cursor, GitHub Copilot, Antigravity). It never touches your home — use it only if you are building integrations.

Step 2B — Set up Home Assistant MCP

Prerequisites: a running Home Assistant instance (2025.2 or newer; any modern 2026 release qualifies).

Settings → Devices & services → Add integration → Model Context Protocol Server. Install it.
Expose entities to Assist (Settings → Voice assistants → Expose). Only exposed entities are visible to MCP. Leave locks, garage doors and alarm panels unexposed until you trust the setup.
Create a long-lived access token for the agent (your profile → Security).
In your agent, add the MCP server at http://<your-ha-host>:8123/mcp (Streamable HTTP; older clients may use the SSE endpoint) with the token as a bearer credential. Some stdio-only clients need a small proxy; Home Assistant’s docs cover it.
For remote access without opening ports, use Home Assistant Cloud (Nabu Casa, $6.50/month) or a VPN/tunnel of your choice.
Test: “List the exposed devices” then “Which lights are on right now?”

Home Assistant’s server exposes the same Assist API its own voice assistant uses, so anything Assist can do, the agent can do — including calling services and, if you allow it, creating automations.

Step 3 — Lock down what the agent can do

Approval mode first. In Claude use the Manual permission setting; in OpenClaw and other agents, enable tool-call confirmation. Switch individual workflows to autonomous only after you have read the logs.
Keep sensitive actions out. Google Home MCP already blocks door unlocks. On Home Assistant, do not expose locks, garage openers, alarm panels or anything that spends money.
Scope the account. Use a dedicated Home Assistant user with limited rights, not your admin account. On Google, the agent acts as the signed-in user with that user’s permissions — so use the least-privileged household member account that still has what you need.
Write a short system prompt. “Only act on explicit instructions; never change security devices; ask before any action affecting more than one room” cuts most misfires.
Inform the household. Google’s guide explicitly recommends talking to other occupants before connecting an agent to a shared home.

Step 4 — Useful first tasks

Morning brief: “Summarise overnight events from the doorbell and back-garden camera, and tell me if any door opened after midnight.”
Energy audit: “Using device-state history, how many hours were the office lights on this week versus last week?”
Laundry log: “Count washer cycles in the last 7 days from the smart-plug power history.”
Dashboard: “Build me a single-page dashboard showing every light, the two thermostats and the last three camera events.”
Completion ping: “When the download finishes, say ‘done’ on the kitchen speaker” — Google Home MCP can send an audio message to a Nest speaker.

Troubleshooting

OAuth redirect error (Google): the redirect URI in your OAuth client does not match the one your agent uses; copy it exactly from Google’s per-client guide.
Agent sees no devices (Home Assistant): nothing is exposed to Assist; check Settings → Voice assistants.
Rate-limit errors (Google): Home MCP throttles bursts; ask the agent to batch queries rather than poll.
Unexpected action: revoke the OAuth grant (Google account → Security → Third-party access) or delete the Home Assistant token, review the tool log, then re-enable with approval mode.