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

Name: Google Home
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Google Home through the Vinkius — pass the Edge URL in the `mcps` parameter and every Google Home tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Google Home Specialist",
    goal="Help users interact with Google Home effectively",
    backstory=(
        "You are an expert at leveraging Google Home tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Google Home "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, Google Home becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Google Home tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

Follow these steps to integrate the Google Home MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 12 tools from Google Home

Why Use CrewAI with the Google Home MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Google Home through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Google Home + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Google Home MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Google Home for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Google Home, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Google Home tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Google Home against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Google Home MCP Tools for CrewAI (12)

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

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

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Google Home + CrewAI FAQ

Common questions about integrating Google Home MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.