2,500+ MCP servers ready to use
Vinkius
MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED
Google Home
Built by Vinkius GDPR ToolsFree for Subscribers

Control Google Nest devices — thermostats, cameras, and doorbells via Smart Device Management (SDM) API.

Vinkius supports streamable HTTP and SSE.

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Google Home
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

What is the Google Home / Nest MCP Server?

The Google Home / Nest MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to Google Home / Nest via 12 tools. Control Google Nest devices — thermostats, cameras, and doorbells via Smart Device Management (SDM) API. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.

Built-in capabilities (12)

generate_camera_streamget_devicelist_deviceslist_roomslist_structuresset_fan_timerset_thermostat_coolset_thermostat_ecoset_thermostat_heatset_thermostat_modeset_thermostat_rangestop_camera_stream

Tools for your AI Agents to operate Google Home / Nest

Ask your AI agent "List all my Nest devices and show me what thermostats I have." and get the answer without opening a single dashboard. With 12 tools connected to real Google Home / Nest data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.

Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.

Why teams choose Vinkius

One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.

Build your own MCP Server with our secure development framework →

Vinkius works with every AI agent you already use

…and any MCP-compatible client

CursorClaudeOpenAIVS CodeCopilotGoogleLovableMistralAWSCursorClaudeOpenAIVS CodeCopilotGoogleLovableMistralAWS

Google Home MCP Server capabilities

12 tools
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

What the Google Home MCP Server unlocks

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.

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

How it works

1. Subscribe to this server
2. Obtain OAuth 2.0 access token and Project ID from Google Device Access console
3. Start controlling your Nest devices from Claude, Cursor, or any MCP-compatible client

Your AI becomes a smart home assistant, helping you manage climate, security, and monitoring.

Who is this for?

  • Smart Home Owners — control thermostats, view cameras, and manage Nest devices from AI assistants
  • Home Automation Enthusiasts — integrate Nest devices into broader automation workflows
  • Property Managers — monitor and adjust climate across multiple properties remotely
  • Security-Conscious Users — check camera feeds and doorbell streams on demand
  • Energy-Conscious Users — optimize thermostat settings and eco mode for energy savings

Frequently asked questions about the Google Home MCP Server

01

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.

02

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

Visit the Google Device Access console 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.

03

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.

04

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.

More in this category

You might also like

Give your AI agents the power of Google Home / Nest MCP Server

Production-grade Google Home MCP Server. Verified, monitored, and maintained by Vinkius. Ready for your AI agents — connect and start using immediately.