An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Google Home to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn your AI agent into a smart home controller.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 12 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 12 available through Google Home / Nest.

  1. 01

    List rooms

    This capability lists all rooms within a specific home structure. It helps your agent understand where your devices are located.

  2. 02

    List structures

    This capability retrieves all home structures linked to your Google Nest account. It is the first step for your agent to see your different properties.

  3. 03

    Set fan timer

    This capability sets the fan duration on a Nest thermostat. You can specify a custom time or use the default setting.

  4. 04

    Generate camera stream

    This capability creates a temporary RTSP or WebRTC URL for a Nest camera or doorbell. Use this to view live video through your agent.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 12 available through Google Home / Nest.

  1. 05

    Get device

    This capability pulls the full state and settings for a specific Nest device. It uses the device ID or name to find the right hardware.

  2. 06

    List devices

    This capability shows every Nest device connected to your account. It provides details on device types, current settings, and room assignments.

  3. 07

    Set thermostat range

    This capability defines the heating and cooling temperature boundaries. It is used when your thermostat is in HEATCOOL mode.

  4. 08

    Stop camera stream

    This capability ends an active video session from a Nest camera or doorbell. It uses the token from the stream generation capability to close the connection.

Capability set03 / 03

09-12

4 capabilities in this set.

Part of 12 available through Google Home / Nest.

  1. 09

    Set thermostat cool

    This capability sets the cooling temperature on a Nest thermostat. It works when the device is in COOL or HEATCOOL mode.

  2. 10

    Set thermostat eco

    This capability triggers the eco mode on a Nest thermostat. It is used to manually override settings for energy savings.

  3. 11

    Set thermostat heat

    This capability sets the heating temperature on a Nest thermostat. It is used when the device is in HEAT or HEATCOOL mode.

  4. 12

    Set thermostat mode

    This capability changes the operating mode of a Nest thermostat. You can switch between HEAT, COOL, HEATCOOL, or OFF.

Real work

What teams actually run

01

Remote Climate Adjustment

Tell your agent to turn up the heat in the living room before you get home.

02

Security Checks

Ask your agent to show you the live feed from your front door camera.

03

Energy Optimization

Switch your thermostat to eco mode when you are leaving for the day.

04

Device Inventory

Ask your agent to list all devices to see what is currently connected to your home.

Automate a task

Put Google Home / Nest to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Google Home / Nest works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Google Home / Nest to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

994ms average. Fast in production.

Google Home / Nest is checked daily against the live service.

Daily averagePeak 1190ms
Oct 3Today
Fastest day
818ms
Slowest day
1190ms
14-day trend
Slowing+29%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 12 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Google Home / Nest, so you can see the experience inside your AI.

It does not authenticate your account with Google Home / Nest. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Google Home / Nest Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_1fBsfzIThZdptHTYBS877gg1lz5jvHIrx5SxHDyC/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Google Home / Nest capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "google-home-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_1fBsfzIThZdptHTYBS877gg1lz5jvHIrx5SxHDyC/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Google Home / Nest in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Google Home / Nest owners hand off.

This MCP is for anyone who wants to move smart home management from dedicated apps into their AI chat interface.

  • 01

    Smart Home Owners

    People who want to control their thermostats and view cameras using natural language.

  • 02

    Property Managers

    Users who need to remotely monitor climate and security across multiple properties.

  • 03

    Automation Enthusiasts

    Users building complex workflows that require Nest device data as input.

FAQ

Questions Google Home / Nest owners ask.

  • 01

    What do I need to use this MCP?

    You need an OAuth 2.0 access token and a Project ID from the Google Device Access console to authenticate your Nest account.

  • 02

    Which AI clients can I use with this?

    You can use any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 03

    Can I see live video from my Nest cameras?

    Yes. Your agent can generate a temporary RTSP or WebRTC stream URL that you can use in a compatible video player.

  • 04

    How do I stop a camera stream?

    You can tell your agent to stop the camera stream, which uses the stream token to terminate the session.

  • 05

    Does this work with all Nest devices?

    This MCP works with Nest thermostats, cameras, doorbells, and displays supported by the Smart Device Management API.

  • 06

    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.

  • 07

    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.

  • 08

    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.

  • 09

    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.

Explore

More in The Unthinkable

Suggestions

Connect Google Home / Nest to Claude, Cursor, ChatGPT & more