Skip to content

Summary

Free, no-setup MCP server that grounds your coding agent in the Google Home API reference plus the Matter 1.5.1 and Thread 1.4.1 specifications.

Features

  • search_documents — retrieval over the full Google Home Developer Center documentation
  • Indexes the Matter specification v1.5.1 and the Thread specification v1.4.1
  • Covers the OpenThread project documentation
  • Unauthenticated trial path on a shared public quota — no Cloud project needed to start
  • API-key auth via the X-Goog-Api-Key header for production quota
  • Read-only: it answers questions, it never touches a device
  • Documented configs for Claude Code, Cursor, VS Code Copilot and Antigravity

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Google Home Developer MCP" tools will be available.
{
  "mcpServers": {
    "google-home-developer-mcp": {
      "command": "claude",
      "args": [
        "mcp",
        "add",
        "HomeDevelopers",
        "--transport",
        "http",
        "https://homedevelopers.googleapis.com/mcp",
        "--header",
        "X-Goog-Api-Key: YOUR_API_KEY"
      ]
    }
  }
}

Description

Google Home Developer MCP is the documentation half of Google's smart-home MCP release of 16 September 2026, and it is the one most developers will actually reach for. It exposes a single tool, search_documents, backed by indexed corpuses covering the complete Google Home Developer Center documentation, the OpenThread project, the Matter specification v1.5.1 and the Thread specification v1.4.1.

The value is grounding. Matter and Thread are large, versioned specifications that a general-purpose model will happily paraphrase from a stale memory of an older revision — cluster IDs, attribute semantics and commissioning flows all move between versions. Pointing the agent at a live index of the current specs means the answer it writes into your firmware or integration code is retrieved rather than recalled.

Unlike the companion Google Home MCP server, this one has no subscription gate and no Google Cloud project requirement to get started: there is an unauthenticated trial path on a shared public quota, so you can attach it to a coding assistant immediately. For production use you enable the Home Developers API on a Cloud project and pass an API key in the X-Goog-Api-Key header, which moves you off the shared quota.

The server is HTTP-transport at https://homedevelopers.googleapis.com/mcp and Google documents configuration for Claude Code, Cursor, GitHub Copilot in VS Code and Antigravity. It reads only — nothing here touches a device, which makes it safe to leave attached to an agent by default.

Related MCP Servers

New

Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.

MCP: ripwire

by Red Hat

New

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

MCP: Graft

by Trail

New

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

New

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Browse all MCP servers →