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 VS Code Copilot 12 tools — connect in under 2 minutes

Name: Google Home
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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": {
      "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.

GitHub Copilot Agent mode brings Google Home data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Google Home MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Google Home

Ask Copilot: "Using Google Home, help me...". 12 tools available

Why Use VS Code Copilot with the Google Home MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Google Home through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Google Home + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Google Home MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Google Home MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect Google Home to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Google Home to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Google Home + VS Code Copilot FAQ

Common questions about integrating Google Home MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.