Google Home MCP Server Google released an early-access Google Home Model Context Protocol (MCP) server that lets AI-powered development tools and virtual assistants inspect home structures, monitor device states, execute control actions, and analyze historical events through standard MCP tools and RPC interfaces. The server exposes five core capabilities — list_homes, list_home_resources, list_home_states, run_home_actions, and list_home_history — and requires an active Google Home Premium Advanced subscription, a Google Cloud project, and an MCP-compatible AI client such as Google Antigravity, Claude Cowork, or OpenClaw. Google enforces rate limits and safety protections such as prohibiting sensitive actions like unlocking doors, and warns that connecting a real home to an AI agent can produce unexpected or undesired behavior and that household members should be informed. 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 https://developers.home.google.com/policies and terms of service https://developers.home.google.com/terms . 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 https://support.google.com/googlehome/answer/17074648 and set up devices for development and testing. Your agent's access to Home MCP can be revoked https://support.google.com/googlehome/answer/14658393 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 using list homes . - Resource discovery: List devices, area layouts, traits, attributes, and command schemas using list home resources . - State monitoring: Check real-time device connectivity status and trait states using list home states . - Device control: Execute parameterized action commands on target devices using run home actions . - Historical analysis: Query past state changes and event logs over specific time ranges using list 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: 1. Open the Google Cloud console https://console.cloud.google.com/ . 2. Create a new Google Cloud project. For more information, see Create projects https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects article in the Google Cloud documentation. Enable the Home API 1. In the Google Cloud console navigation menu, select APIs & Services Enabled APIs & Services . 2. Search for Home API and click Enable . Configure OAuth consent and credentials 1. Configure the OAuth consent screen: 1. Open APIs & Services OAuth consent screen . 2. Select External audience, click Get started , and fill in the required app information and contact email. 2. Open 3. Create an OAuth client ID: 1. Open APIs & Services Credentials . 2. Click + Create credentials and select OAuth client ID . 3. Set Application type to Web application . 4. 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 5. Click Create and copy your Client ID and Client Secret to a secure location. 4. Open 5. Publish your application: 1. Open Google Auth Platform Audience . 2. Under Publishing status , click Publish app . 6. 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. 1. Open the application configuration menu: Settings Advanced settings Customizations Open MCP Config . 2. Add the home mcp entry under the mcpServers configuration object: { "mcpServers": { "home mcp": { "serverUrl": "https://home.googleapis.com/mcp", "oauth": { "clientId": "YOUR CLIENT ID", "clientSecret": "YOUR CLIENT SECRET" } } } } 3. Complete authentication: Navigate to Settings Advanced settings Customizations home mcp Authentication . 4. 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 https://antigravity.google/docs/mcp . Claude Configure Claude Cowork to connect to your custom home MCP server: 1. Open Claude Connectors https://claude.ai/customize/connectors . 2. Click + and select Add custom connector . 3. Enter the server URL: https://home.googleapis.com/mcp . 4. Click Advanced settings and enter your Client ID and Client Secret . 5. Click Add and complete the OAuth authorization flow in your browser. 6. In a Cowork chat, click + in the lower-left corner, select Connectors , and toggle home mcp on. For more information, see the Claude Platform documentation https://platform.claude.com/docs/en/home . OpenClaw Configure OpenClaw to connect to the remote SSE transport with OAuth authentication: 1. 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" } } } } } 2. Apply the configuration patch in your terminal: openclaw config patch --stdin 3. Restart the OpenClaw gateway: openclaw gateway restart 4. Initiate the authentication flow: openclaw mcp login home mcp 5. Follow the generated authorization URL to sign in and grant access. For more information, see the OpenClaw documentation https://docs.openclaw.ai . Familiar face consent 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 for each camera or doorbell . - Your application must have an OAuth 2.0 Client ID created in Google Cloud. See Configure your AI client 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