Ghome MCP Server

Simple CLI for Google Home & Mini

Local serverstdioPython

What is the Ghome MCP server?

Simple CLI for Google Home & Mini. That is what the ghome mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This also includes following importantly Download Build Tools for Visual Studio 2019. In the installer, select the C++ build tools, the Windows 10 SDK, and the latest version of MSVC v142 x64/x86 build tools.

Getting it running

Installation goes through your MCP client rather than a global install: point it at ghome on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 11 tools. What each one is for:

  • auth — The auth tool exposed by this server
  • device_list — This tool generates a list of all google home devices connected to your network and prints the name and ip address of each. This is a quick way to
  • device_info — This tool uses device name or ip addrss to get all information available for said device and prints it out as a json object
  • reboot — This is a powerful tool since the only current way of rebooting a device is to physically unplug and plug the device back in. This also allows you to
  • alarm_list — This tool will simply list all alarms currently on your device including date , time and time zone
  • alarm_volume — Set the alarm volume for a device, this only changes the alarm volume and nothing else. Alarm volumes can be set for values 0-1 which represents
  • alarm_delete — Delete all alarms on a google home device based on ip or name
  • bluetooth_status — The bluetooth status prints whether the device discovery is enabled, whether scanning is enabled and whether it is connected to a device
  • bluetooth_paired — Check if device is paried via bluetooth to any current device as well as history of all deviced connected, last connected and whether or not they are
  • bluetooth_discovery — This is to enable or disable bluetooth discovery to allow for pairing as needed. The action can be to enable or disable coupled with the ip or device
  • saved_network — This tool allows you to print any saved network on the device and nothing else it may provide only information on current network being used if there

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ghome.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ghome's toolset — auth, device_list, device_info and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Samapriya Roy; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
authThe auth tool exposed by this server.
device_listThis tool generates a list of all google home devices connected to your network and prints the name and ip address of each. This is a quick way to check specific name or ip address to use for a device.
device_infoThis tool uses device name or ip addrss to get all information available for said device and prints it out as a json object.
rebootThis is a powerful tool since the only current way of rebooting a device is to physically unplug and plug the device back in. This also allows you to do a factory reset so **Use reset with CAUTION**.
alarm_listThis tool will simply list all alarms currently on your device including date , time and time zone.
alarm_volumeSet the alarm volume for a device, this only changes the alarm volume and nothing else. Alarm volumes can be set for values 0-1 which represents volume from 0-100% so 0.1 means 10% volume and so on.
alarm_deleteDelete all alarms on a google home device based on ip or name.
bluetooth_statusThe bluetooth status prints whether the device discovery is enabled, whether scanning is enabled and whether it is connected to a device.
bluetooth_pairedCheck if device is paried via bluetooth to any current device as well as history of all deviced connected, last connected and whether or not they are currently connected.
bluetooth_discoveryThis is to enable or disable bluetooth discovery to allow for pairing as needed. The action can be to enable or disable coupled with the ip or device name.
saved_networkThis tool allows you to print any saved network on the device and nothing else it may provide only information on current network being used if there is only a single network it was connected to .

How to install the Ghome MCP server

{
  "mcpServers": {
    "ghome": {
      "command": "uvx",
      "args": ["ghome"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Ghome to auth.
  • Use Ghome to device list.
  • Use Ghome to device info.

Frequently asked questions

It connects Ghome to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (auth, device_list, device_info, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ghome directly.