Google Home MCP. Control your entire house, from climate to security.
Google Home MCP connects your AI agent directly to all your Nest smart devices, giving you hands-free control over climate, security, and monitoring. Use it to set temperatures, view live camera feeds from doorbells and cameras, or check device status across multiple properties.
Give Claude and any AI agent real-world access
List and view all structures, rooms, and connected Nest devices in your home.
Change the operating mode (heat/cool/off) or set specific temperatures for any linked thermostat.
Generate temporary streaming URLs so your agent can display real-time feeds from cameras and doorbells.
Set fan timers or place the thermostat in energy-saving eco mode manually.
Ask an AI about this
Waiting for input…
What AI agents can do with Google Home MCP with 12 Tools
Use these tools to list devices, adjust thermostats, set fan timers, generate live camera feeds, and manage the physical structure of your smart home.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Google Home MCPGenerate Camera Stream
This tool provides a temporary live stream URL so your agent can display video feeds from any Nest camera or doorbell.
Get Device
Fetch detailed status and information for one specific Google Nest device using its...
List Devices
Retrieves a complete list of every Nest device, showing their type, room assignment...
List Rooms
Shows the physical organization of your home by listing all structured rooms within...
List Structures
Lists every building or structure connected to your Google Nest account.
Set Fan Timer
Sets the fan timer on a thermostat, turning the fan on for a specified period of time.
Set Thermostat Range
Defines both the heating and cooling comfort temperature range for a Nest thermostat in HeatCool mode.
Stop Camera Stream
Properly terminates an active camera stream session using the token provided by...
Set Thermostat Cool
Adjusts the cooling temperature setting on a Nest thermostat when it's in Cool or...
Set Thermostat Eco
Manually forces your Nest thermostat into energy-saving eco mode to reduce...
Set Thermostat Heat
Sets the desired heating temperature on a Nest thermostat when it's in Heat or...
Set Thermostat Mode
Changes the overall operating mode of the thermostat, setting it to HEAT, COOL, HEATCOOL, or OFF.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Google Home, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Google Home / Nest. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Juggling multiple smart home apps is exhausting.
Today, managing your house means logging into the Nest app for cameras, the separate thermostat portal for climate control, and maybe a third dashboard just to check overall device status. Every time you want to know if the front door camera saw anything while also adjusting the temperature in the back bedroom, it's a sequence of clicks, tabs, and context switches.
With this MCP, those steps vanish. You tell your agent what you need—'Check the backyard and turn up the heat.' The system handles the entire flow: it pulls live video from the doorbell using generate_camera_stream, confirms the status with get_device, and adjusts the climate using set_thermostat_mode. It’s all done conversationally.
Control your whole house with Google Home MCP
Manual tasks like listing every connected device or determining which structure needs attention are tedious and prone to error. You have to navigate the system just to get a complete inventory of what’s working.
This MCP lets your agent run list_devices instantly, providing you with a definitive, structured map of every piece of hardware in use. It gives clarity where there used to be complexity.
What Google Home MCP does for your AI
This connector turns your smart home into a fully controllable system through natural conversation. Instead of opening separate apps for the thermostat, checking video feeds, and managing room data, your AI agent handles it all. You can ask it to adjust the heat in the living room or check if the front door camera sees movement.
Need to know what devices you have? The MCP lists every Nest device, including cameras, thermostats, and doorbells across all structures. If you're building complex home automation routines, connecting through Vinkius gives your agent access to a centralized catalog of capabilities, making it easy for your AI client to manage everything from setting the optimal cooling temperature to streaming live video feeds on demand.
019d75a8-c0b5-70b0-af00-197965d676c9 How to set up Google Home MCP
The bottom line is that your AI client treats your entire smart home system like a single, controllable unit.
First, subscribe to this MCP and obtain your OAuth 2.0 token and Project ID from the Google Device Access console.
Next, point your AI client—like Cursor or Claude—to the Vinkius catalog using these credentials.
Your agent then uses the available tools to interact with your home's devices based on natural language commands.
Who uses Google Home MCP
This connector is for anyone who manages physical properties or lives in an advanced smart home setup. If you're tired of juggling multiple manufacturer apps and manually checking feeds, this MCP gives your agent the central brain it needs.
Monitoring climate control and security across several buildings remotely, making sure every unit is set to the right temperature or that cameras are recording.
Asking their agent simple questions like, 'It's getting cold in here, switch the living room thermostat to heat mode,' instead of physically adjusting a dial.
Building complex workflows that combine camera monitoring with automated climate adjustments based on detected activity or time of day.
Benefits of connecting Google Home MCP
Full Security Visibility: Use generate_camera_stream and stop_camera_stream to get live RTSP/WebRTC feeds instantly. You don't have to open a separate app just to check the front door camera feed.
Precise Climate Control: Need to raise or lower the temperature? The MCP lets you set_thermostat_mode, set_thermostat_heat, and set_thermostat_cool directly through your agent, regardless of which room you're in.
Energy Management: Don't waste power. You can use set_thermostat_eco to place the system in energy-saving mode, or use set_fan_timer if you just need fresh air for a while.
System Mapping: Before changing anything, list_devices lets your agent map out every single component—cameras, thermostats, and doorbells—so you know exactly what you're controlling.
Structured Monitoring: By using list_structures and list_rooms, your agent understands the physical layout of your home, ensuring commands like 'Set the living room thermostat...' hit the right target.
Google Home MCP use cases
Checking on a vacant property after hours
A property manager asks their AI client to check if anything is unusual. The agent runs list_devices first, then uses generate_camera_stream for the main entrance feed and set_thermostat_mode to ensure the HVAC system doesn't waste energy by running at full blast.
Preparing a home before guests arrive
A homeowner asks their agent to get ready. The MCP automatically runs list_rooms, checks the current settings using get_device, and then uses set_thermostat_range to dial in the perfect comfort zone for both heating and cooling.
Quickly adjusting climate when running late
You walk in the door and ask your agent to make it warmer. The system identifies the local thermostat using list_devices and executes set_thermostat_heat, reporting back on the current temperature status.
Troubleshooting a camera feed issue
A security expert wants to check multiple feeds quickly. They ask the agent to generate_camera_stream for all available doorbells and then stop_camera_stream once they've finished reviewing the live data.
Google Home MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Assuming device location
Telling your agent, 'Turn off the thermostat,' when the system has multiple thermostats across different floors or wings of the house.
Always start by calling list_devices to see all available devices. Then, use get_device and specify the exact ID or room name to ensure you're targeting the correct unit before running set_thermostat_mode.
Forgetting to stop streams
The agent keeps generating live feeds for cameras indefinitely, causing resource overload and billing issues.
After generate_camera_stream provides the stream URL, remember to use the corresponding stop_camera_stream tool. This cleanly releases the stream token and frees up resources.
Mixing temperature commands
Trying to set both the heat and cool temperatures using separate tools without defining a clear comfort range.
If you're in HeatCool mode, use set_thermostat_range. This tool lets your agent define a single comfort envelope for both heating and cooling simultaneously.
When to use Google Home MCP
Use this MCP if your goal is to centrally manage multiple physical systems—specifically climate control (heat/cool) and security monitoring—from one conversational interface. You need the deep device knowledge provided by list_devices, set_thermostat_mode, and generate_camera_stream. Don't use it if you just need simple scheduling; for that, a dedicated calendar or routine automation tool is better. Also, don't use it to manage non-Google branded smart devices—it only works with Nest via the SDM API. If your task involves coordinating actions across completely separate systems (e.g., lights and sprinklers), you might need an integration layer that acts as a middleware connector, rather than just focusing on one brand.
Frequently asked questions about Google Home MCP
How do I check what Nest devices are connected using the Google Home MCP? +
You run list_devices. This tool retrieves a full inventory of every piece of hardware, including cameras, thermostats, and doorbells across your entire property.
Can the Google Home MCP adjust the temperature if I'm away? +
Yes, you can use set_thermostat_mode or set_thermostat_eco. This lets your agent put the system into energy-saving mode when no one is home.
What do I need to view a live feed with generate_camera_stream? +
The tool generates a temporary stream URL (RTSP). You must use this link immediately, and remember that you'll need to call stop_camera_stream when you are done viewing.
Does the Google Home MCP understand different rooms in my house? +
Yes. By using list_rooms, your agent understands the physical layout of your home and can target specific devices within a structure.
What if I want to change both heat and cool settings at once? Do I use set_thermostat_range? +
Yes, set_thermostat_range is the correct tool. It lets your agent define a single comfort envelope that covers both heating and cooling parameters simultaneously.
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.