Google Home / Nest MCP Server — device control, camera streams, thermostat management via SDM API
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"google-home-blade-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# google-home-blade-mcp **Security-first, token-efficient MCP server for Google Home and Nest devices via the Smart Device Management API.** Control thermostats, stream cameras, monitor doorbells, and pull device events — all through a hardened MCP interface designed for LLM-driven home automation. ## Why This Exists | | ghome-mcp-server | Google's Cloud MCPs | **google-home-blade-mcp** | |---|---|---|---| | **Device coverage** | Smart plugs only | No Google Home MCP | Full SDM: thermostats, cameras, doorbells, displays | | **Security model** | None | IAM-only | Write gates + confirm gates + credential scrubbing | | **Token efficiency** | Verbose JSON | N/A | Pipe-delimited, null-omission, ~25 tokens/device | | **Thermostat control** | No | No | Mode, setpoint, eco, fan — all with safety gates | | **Camera streams** | No | No | WebRTC/RTSP with 5-min session management | | **Event streaming** | No | No | Pub/Sub integration for motion, person, doorbell events | | **Batch operations** | No | N/A | `ghome_status` dashboard, `ghome_thermostats` overview | | **Marketplace ready** | No | No | `stallari-plugin.yaml`, `home-v1` contract, SKILL.md | ### Design Principles 1. **Security-first** — Every device command requires explicit write enablement. Destructive operations require double confirmation. OAuth tokens never appear in output. Access tokens live in memory only. 2. **Token efficiency** — Compact pipe-delimited output. Null fields omitted. Dashboard views compress entire device fleets into minimal tokens. One `ghome_status` call replaces N individual queries. 3. **Event-driven** — Pub/Sub integration enables webhook-style triggers for motion detection, doorbell presses, and state changes. No polling required. ## Quick Start ```bash # Install git clone https://github.com/groupthink-dev/google-home-blade-mcp.git cd google-home-blade-mcp make install-dev # Set up OAuth (one-time interactive flow) export GOOGLE_HOME_CLIENT_ID="your-client-id" export GOOGLE_HO…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.