Google Home MCP

// Overview

Google Home MCP is Google's official way to put an AI agent in front of a real smart home. It is a hosted Model Context Protocol endpoint at https://home.googleapis.com/mcp, so any client that can call MCP tools — Google names Antigravity, Claude and OpenClaw — connects to it without a Google-specific SDK. Once connected, the agent reaches the devices and event history in the user's Google Home ecosystem, from Nest doorbells and thermostats to Works with Google Home and Matter accessories.

The server exposes five tools that together cover a full read-decide-act loop. `list_homes` returns the homes and structures the caller can reach. `list_home_resources` enumerates devices, areas, traits, attributes and the command schemas each device accepts. `list_home_states` reports live connectivity and trait conditions. `run_home_actions` executes parameterized commands against named devices. `list_home_history` queries past state changes and event logs over a time range — the piece that lets an agent answer questions about what happened rather than only what is true now.

Google ships a second, separate server alongside it. Home Developer MCP, at https://homedevelopers.googleapis.com/mcp, touches nobody's house: it searches Google Home documentation and the Matter 1.5.1 and Thread 1.4.1 specifications so coding tools can ground answers about the protocols. It offers an unauthenticated trial path on a shared public quota, which makes it the easy one to try — no API key and no Google Cloud project — with an API-key path recommended for sustained use.

Access is deliberately narrow at launch. Home MCP entered Early Access on 16 September 2026, in English, for Google Home Premium Advanced subscribers in the United States. Guardrails sit on Google's side of the connection: rate limits apply, sensitive actions such as unlocking doors are prohibited outright, familiar-face data requires the structure manager's consent, and a user can revoke an agent's access at any time from the Google Home app or the My Accounts page.

// What it does

• Hosted MCP endpoint at https://home.googleapis.com/mcp — any MCP-capable client connects, no Google-specific SDK
• Five tools covering the full loop: list_homes, list_home_resources, list_home_states, run_home_actions and list_home_history
• Event-history queries, so an agent can summarise what happened in a home over a time range, not just read current state
• Reaches the whole Google Home ecosystem: Nest devices plus Works with Google Home and Matter accessories
• Home Developer MCP, a second server that searches Home docs and the Matter 1.5.1 and Thread 1.4.1 specifications
• Safety limits enforced server-side: rate limits, prohibited sensitive actions such as unlocking doors, consent-gated familiar-face data
• Per-agent access is revocable at any time from the Google Home app or the My Accounts page

// Getting started

Home Developer MCP is the one to try first — it needs no credentials. Home MCP itself requires a Google Home Premium Advanced subscription and OAuth credentials you create in a Google Cloud project.

{
  "mcpServers": {
    "home-developer": {
      "url": "https://homedevelopers.googleapis.com/mcp"
    }
  }
}

https://home.googleapis.com/mcp

Commands and code are distilled from the project's own documentation — always check the official docs for the latest.

// When to use it

• Reach for it when you want the assistant you already use to run the house, instead of being limited to Google's own
• Reach for it to ask questions that span time and rooms — what happened while you were out, how long a light stayed on
• Reach for it to build a smart home dashboard in plain language rather than wiring up the Home APIs by hand
• Reach for Home Developer MCP when a coding agent needs grounded answers about Matter, Thread or the Home APIs

// How Google Home MCP compares

Google Home MCP alongside other open-source workflow automation tools AI/TLDR tracks, ranked by GitHub stars.