Claude CodeCLI

Why use Google Home MCP Server with Claude Code?

Bring Smart Home
to Claude Code

Name: Google Home MCP Server
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Create your Vinkius account to connect Google Home to Claude Code and start using all 12 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

GDPR Free for Subscribers

Generate Camera StreamGet DeviceList DevicesList RoomsList StructuresSet Fan TimerSet Thermostat CoolSet Thermostat EcoSet Thermostat HeatSet Thermostat ModeSet Thermostat RangeStop Camera Stream

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the 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.

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

Subscribe to this server
Obtain OAuth 2.0 access token and Project ID from Google Device Access console
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

Built-in capabilities (12)

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

See what your AI agent can do with Google Home

Why Claude Code?

Claude Code registers Google Home as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Google Home data drives decisions without human intervention.

—
Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart
—
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
—
Claude Code runs headlessly, enabling unattended batch processing using Google Home tools in cron jobs or deployment scripts
—
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

Google Home in Claude Code

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Enterprise Security

Why run Google Home with Vinkius?

The Google Home connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 12 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

View full Google Home details →

Fully ManagedNo server setup

Plug & PlayNo coding needed

SecurePrivacy protected

PrivateYour data is safe

Cost ControlBudget limits

Control1-click disconnect

Auto-UpdatesMaintenance free

High SpeedOptimized for AI

Reliable99.9% uptime

Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents

Complete visibility into every agent action

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect Google Home using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Explore Analytics

Why Vinkius

Google Home and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect Google Home to Claude Code through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations

<40msResponse time

100%Fully managed

	Raw MCP	Vinkius
Ready-to-use MCPs	Find and configure each manually	4,000+ MCPs ready to use
Connection Setup	Manual coding & server setup	1-click instant connection
Server Hosting	You host it yourself (needs 24/7 uptime)	100% hosted & managed by Vinkius
Security & Privacy	Stored in plaintext config files	Bank-grade encrypted vault
Activity Visibility	Blind execution (no logs or tracking)	Live dashboard with real-time logs
Cost Control	Runaway AI token spend risk	Automatic budget limits
Revoking Access	Must delete files or code to stop	1-click disconnect button

View step-by-step setup guide for Claude Code →

The Vinkius Advantage

How Vinkius secures
Google Home for Claude Code

Every request between Claude Code and Google Home is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

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 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.