What Google Nest devices are supported by this API?

The SDM API supports: Nest Thermostats (Nest Learning Thermostat, Nest Thermostat E, Nest Thermostat 2020), Nest Cameras (legacy, battery, wired, with spotlight), Nest Doorbells (legacy battery, wired, battery), and Nest Hub displays. Each device exposes specific traits (e.g., ThermostatMode, CameraLiveStream) that can be queried and controlled.

How do I get OAuth 2.0 credentials for the Google SDM API?

Visit the [**Google Device Access console**](https://console.nest.google.com/device-access/) and create a project. You'll receive a Project ID. Then, set up OAuth 2.0 credentials in Google Cloud Console, link them to your Device Access project, and complete the OAuth flow to obtain an access token. The token expires after 1 hour and must be refreshed.

Can I control multiple thermostats in different locations?

Yes! The API returns all devices across all structures and rooms in your project. Use `list_devices` to see all thermostats with their room assignments, then use each device's unique ID to control them individually. You can set different modes and temperatures for each thermostat.

How long do camera stream URLs last?

Camera stream URLs (both RTSP and WebRTC) are temporary and typically expire after 5 minutes. The stream token returned in the response should be used immediately and the stream should be stopped with `stop_camera_stream` when no longer needed to free up device resources.

Google Home MCP Server for Claude Desktop 12 tools — connect in under 2 minutes

Name: Google Home
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 12 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Google Home and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "google-home": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Google Home MCP Server

Connect to Google Nest devices via the Smart Device Management (SDM) API and control your smart home from any AI agent. Manage thermostats, view camera feeds, and interact with doorbells.

Claude Desktop is the definitive way to connect Google Home to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

List Devices — See all your Nest thermostats, cameras, doorbells, and displays
Thermostat Control — Set mode (Heat/Cool/Off), adjust temperatures, enable eco mode, and control fan timer
Camera Streaming — Generate live RTSP or WebRTC stream URLs from Nest cameras and doorbells
Doorbell Management — View doorbell camera feeds and stream events
Structure & Rooms — Browse your home's structures and room organization
Device Details — Get full device state including all traits and current settings

The Google Home MCP Server exposes 12 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Google Home to Claude Desktop via MCP

Follow these steps to integrate the Google Home MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Google Home

Look for the 🔌 icon in the chat — your 12 tools are now available

Why Use Claude Desktop with the Google Home MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Google Home through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Google Home + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Google Home MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Google Home MCP Tools for Claude Desktop (12)

These 12 tools become available when you connect Google Home to Claude Desktop via MCP:

generate_camera_stream

The stream token is temporary and should be used immediately. Stop the stream when done. Generate a live camera stream URL from a Nest camera or doorbell

get_device

Use device ID from list_devices or device name. Get details for a specific Google Nest device

list_devices

Shows device types, traits, and room assignments. USE WHEN: - User wants to see all their Nest devices - User needs to find device IDs for other commands - User is exploring their smart home setup - User asks "what Nest devices do I have" EXAMPLES: - "List all my Nest devices" → call with no params - "Show my smart home devices" → call with no params - "What Nest devices are connected?" → call with no params List all Google Nest devices in your home

list_rooms

Useful for understanding device locations and room organization. List all rooms in a specific structure

list_structures

Each structure contains rooms and devices. List all structures (homes) in your Google Nest account

set_fan_timer

Turns the fan on for a specified duration. Duration is optional and defaults to the thermostat setting. Set the fan timer on a Nest thermostat

set_thermostat_cool

Use this when the thermostat is in COOL or HEATCOOL mode. Set the cooling temperature on a Nest thermostat

set_thermostat_eco

This is a manual override of the eco/eco-friendly temperature settings. Set Nest thermostat to eco mode for energy savings

set_thermostat_heat

Use this when the thermostat is in HEAT or HEATCOOL mode. Set the heating temperature on a Nest thermostat

set_thermostat_mode

Supported modes: HEAT, COOL, HEATCOOL, OFF. Use device ID from list_devices to target a specific thermostat. USE WHEN: - User wants to change thermostat mode - User asks to turn heating/cooling on or off - User wants to switch thermostat operating mode - User says "set thermostat to heat/cool/off" PARAMETERS: - device_id (REQUIRED): Thermostat device ID - mode (REQUIRED): One of HEAT, COOL, HEATCOOL, or OFF EXAMPLES: - "Set thermostat to heat mode" → call with device_id, mode="HEAT" - "Turn off the thermostat" → call with device_id, mode="OFF" - "Set thermostat to cool" → call with device_id, mode="COOL" Set the mode of a Nest thermostat

set_thermostat_range

Useful for HEATCOOL mode to define the comfort range. Set both heating and cooling temperatures on a Nest thermostat

stop_camera_stream

Use the stream token returned from generate_camera_stream to properly terminate the stream session. Stop an active camera stream from a Nest camera or doorbell

Example Prompts for Google Home in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Google Home immediately.

"List all my Nest devices and show me what thermostats I have."

"Set my living room thermostat to 22°C heating mode."

"Show me the live feed from my front door camera."

Troubleshooting Google Home MCP Server with Claude Desktop

Common issues when connecting Google Home to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Google Home + Claude Desktop FAQ

Common questions about integrating Google Home MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.