Google Home MCP Server

wpnews.pro

Early Access

The Google Home Model Context Protocol (MCP) server allows AI-powered development tools and virtual assistants to interact directly with smart home environments. By exposing standard MCP tools and RPC interfaces, the server enables Large Language Models (LLMs) to inspect home structures, monitor device states, execute control actions, and analyze historical events.

Warning! Connecting a real-life home to an AI agent allows that agent to control devices on your behalf. Home MCP enforces rate limits and safety protections, such as prohibiting sensitive actions like unlocking doors. However, depending on your agent, connecting it to Home MCP can result in unexpected or even undesired behavior. Carefully review developer policies and terms of service.

If you choose to connect a Google Home used by other household members with Home MCP, you should inform them that your agent can control devices and access home data. Alternatively, you can create an additional home and set up devices for development and testing.

Your agent's access to Home MCP can be revoked at any time from the Google Home app (GHA) or your My Accounts page.

Overview #

An MCP server acts as a proxy between smart home infrastructure and AI applications. The Home MCP server exposes executable tools that allow AI clients to query real-time home telemetry and issue commands.

Core capabilities

The Home MCP server provides several core capability areas:

Structure discovery: Retrieve accessible homes and structures usinglist_homes .
Resource discovery: List devices, area layouts, traits, attributes, and command schemas usinglist_home_resources .
State monitoring: Check real-time device connectivity status and trait states usinglist_home_states .
Device control: Execute parameterized action commands on target devices usingrun_home_actions .
Historical analysis: Query past state changes and event logs over specific time ranges usinglist_home_history .

Prerequisites #

Before setting up the Home MCP server, ensure you have the following:

An active smart home setup in Google Home with connected devices.
An active Google Home Premium Advanced subscription.
Access to a Google Cloud project.
An MCP-compatible AI client or application, such as Google Antigravity, Claude Cowork, or OpenClaw.

Configure the MCP server #

Setting up the MCP server requires creating a Google Cloud project, obtaining access approval, enabling the Home API, and generating OAuth credentials.

Create a Google Cloud project

If you don't have a Google Cloud already, you must create one:

Open the Google Cloud console .
Create a new Google Cloud project.

For more information, see Create projects article in the Google Cloud documentation.

Enable the Home API

In the Google Cloud console navigation menu, select APIs & Services >Enabled APIs & Services .
Search for Home API and clickEnable .

Configure OAuth consent and credentials

Configure the OAuth consent screen:
Open APIs & Services >OAuth consent screen .
Select External audience, clickGet started , and fill in the required app information and contact email.
Open
Create an OAuth client ID:
Open APIs & Services >Credentials .
Click + Create credentials and selectOAuth client ID .
Set Application type toWeb application .
Add the authorized redirect URIs corresponding to your target AI clients: - Google Antigravity:https://antigravity.google/oauth-callback - Claude Cowork:https://claude.ai/api/mcp/auth_callback - OpenClaw: Redirect URI specified by your local OpenClaw installation
Click Create and copy yourClient ID andClient Secret to a secure location.
Open
Publish your application:
Open Google Auth Platform >Audience .
Under Publishing status , clickPublish app .
Open

Configure your AI client #

You can configure several AI development environments to connect to the Home MCP server using OAuth authentication. Enter your OAuth Client ID and Client Secret here, then follow your preferred setup instructions.

Enter your Client ID: YOUR_CLIENT_ID
Enter your Client Secret: YOUR_CLIENT_SECRET

Automated setup using a prompt

If your AI assistant supports managing MCP tool configurations directly from chat, you can instruct your assistant to configure the server by pasting the following prompt:

Please configure the Home MCP server for me with these settings:
- Name: home_mcp
- Server URL: https://preprod-home.sandbox.googleapis.com/mcp
- Transport: sse
- OAuth Scope: https://www.googleapis.com/auth/home.platform.v2
- Client ID: YOUR_CLIENT_ID
- Client Secret: YOUR_CLIENT_SECRET

Manual setup

Select your preferred AI tool for manual setup instructions.

Antigravity

Google Antigravity provides built-in integration for MCP servers across its CLI, IDE, and desktop environments.

Open the application configuration menu: Settings >Advanced settings >Customizations >Open MCP Config .
Add the home_mcp entry under themcpServers configuration object:

{
  "mcpServers": {
    "home_mcp": {
      "serverUrl": "https://home.googleapis.com/mcp",
      "oauth": {
        "clientId": "YOUR_CLIENT_ID",
        "clientSecret": "YOUR_CLIENT_SECRET"
      }
    }
  }
}

Complete authentication: Navigate to Settings >Advanced settings >Customizations >home_mcp >Authentication .
Complete the Google Home permissions flow in your web browser, select your home structure, and copy the authorization code back into Antigravity.

For more information, see the Google Antigravity documentation.

Claude

Configure Claude Cowork to connect to your custom home MCP server:

Open Claude Connectors .
Click + and selectAdd custom connector .
Enter the server URL: https://home.googleapis.com/mcp .
Click Advanced settings and enter yourClient ID andClient Secret .
Click Add and complete the OAuth authorization flow in your browser.
In a Cowork chat, click + in the lower-left corner, selectConnectors , and togglehome_mcp on.

For more information, see the Claude Platform documentation.

OpenClaw

Configure OpenClaw to connect to the remote SSE transport with OAuth authentication:

Prepare the configuration patch JSON block:

{
  "mcp": {
    "servers": {
      "home_mcp": {
        "url": "https://home.googleapis.com/mcp",
        "transport": "sse",
        "auth": "oauth",
        "oauth": {
          "scope": "https://www.googleapis.com/auth/home.platform.v2",
          "redirectUrl": "[YOUR_OPENCLAW_REDIRECT_URL]"
        },
        "env": {
          "CLIENT_ID": "YOUR_CLIENT_ID",
          "CLIENT_SECRET": "YOUR_CLIENT_SECRET"
        }
      }
    }
  }
}

Apply the configuration patch in your terminal:

openclaw config patch --stdin

Restart the OpenClaw gateway:

openclaw gateway restart

Initiate the authentication flow:

openclaw mcp login home_mcp

Follow the generated authorization URL to sign in and grant access.

For more information, see the OpenClaw documentation.

To access familiar faces data in the Home MCP, users must explicitly consent to this feature separately.

Prerequisites

The user granting consent must be a manager of the Google Home structure.
The user's structure must have at least one compatible Google Nest camera or doorbell and an active Google Home Premium subscription with Familiar face detection enabled foreach camera or doorbell .
Your application must have an OAuth 2.0 Client ID created in Google Cloud. See Configure your AI client to create an OAuth 2.0 Client if you haven't already done so.

Consent links

To grant your application access, you must visit a consent link personalized with your OAuth 2.0 Client ID and Home Structure ID. There are two ways to get your consent link.

Once you have your link, visit it and provide consent.

Agent creates the link

If your agent is already connected to the Home MCP, it can automatically locate your Home Structure ID and generate a ready-to-click link.

Update the following parameters directly on this page, then copy-paste the customized prompt into your agent's chat.

CLIENT_ID — Your OAuth 2.0 Client ID from Google Cloud. For example, 123456789-xyz.apps.googleusercontent.com.
STRUCTURE_NAME — The name of the target Home structure.

Please query my Home MCP to find the
Structure ID for my home named STRUCTURE_NAME. Once found, display
the structure name and ID, generate my clickable Familiar Faces Consent Link by
replacing <STRUCTURE_ID> in this URL with the structure ID you found:
https://home.google.com/connections/feature_consent?client_id=CLIENT_ID&structure_id=<STRUCTURE_ID>&features=1&continue=https%3A%2F%2Fhome.google.com

You create the link

If your agent is already connected to the Home MCP, it can automatically locate your Home Structure ID and generate a ready-to-click link.

Update the following parameters directly on this page, then open the customized link in a web browser.

CLIENT_ID — Your OAuth 2.0 Client ID from Google Cloud. For example, 123456789-xyz.apps.googleusercontent.com.
STRUCTURE_ID — The UUID of the target Home structure. The easiest way to get this is to ask your agent using the Home MCP, "Tell me the structure ID (UUID) for [Structure Name]."

https://home.google.com/connections/feature_consent?client_id=CLIENT_ID&structure_id=STRUCTURE_ID&features=1&continue=https%3A%2F%2Fhome.google.com

Verify connection and functionality #

Once your client is configured and authenticated, verify the server connection:

Launch your AI assistant or workspace session.
Check active MCP server connections (in Antigravity, run /mcp or inspect tool lists).
Confirm that home_mcp is listed with active tools.
Issue sample prompts to your assistant to test different capabilities:

Entity discovery:How many lights do I have in my house?
Real-time state monitoring:Is my home secured?
Device control:Turn off all the outside lights.
Historical event analysis:What happened while I was out?

Grant tool execution permissions when prompted by your client. The AI assistant can retrieve real-time state data and all responses will be grounded in your home telemetry.

Support #

For Home MCP development support, head to the Smart Home for Developers Help Community There you can post a question to get help, or look through previously posted questions to see if your question has already been answered.

To file a MCP bug or feature request, head to our public issue tracker.

Known Issues

Trait Testing — To provide the broadest set of functionality for your agents we've included some traits that are marked experimental. You may encounter scenarios where these experimental traits don't work as expected. If so, please use the public issue tracker to report.
Latency — At times you may notice longer than expected latency with Home MCP. We are actively working on optimizations. Expect to see latency improvements in future releases.

Coming Soon

Automations — Creating and managing automations with Home MCP is not supported at this time. We are working on this functionality and plan to release automations support in a future release.

source & further reading

developers.home.google.com — original article