Port OS vs Google Home MCP: which one fits your home?
Published November 2, 2026 · By Port OS Team
Use Google Home MCP if your devices already live in Google Home, you subscribe to Google Home Premium Advanced and you are in the US. Consider Port OS if you want one connection across brands such as Philips Hue, Sonos and Roborock, or if Google's early access does not cover you yet.
Port OS publishes this comparison. It is based on Google's developer documentation, launch coverage and the current Port OS alpha integration catalog, all checked on November 2, 2026. Google's server is in early access, so its requirements can change. We have not benchmarked the two products against each other.
Compare the two setups
| Decision | Port OS | Google Home MCP |
|---|---|---|
| Who can use it | A Port OS account (Port OS is in alpha) | Google Home Premium Advanced subscribers in the US, during early access |
| What you set up | A Port OS account, then each device provider you connect | A Google Cloud project with the Home API enabled and your own published OAuth web client |
| Devices | The providers in the Port OS catalog, across brands | Devices in your Google Home, with the actions Google exposes for each |
| Google Nest | Thermostats and camera live views through your own Device Access project | Through Google Home |
| History | Fresh state on request; Nest events are not available on this connection | A history tool for past states and events |
| AI clients | Any client that supports remote MCP with OAuth sign-in, including ChatGPT and Claude | Google lists Google Antigravity, Claude Cowork and OpenClaw |
How Google Home MCP works
Google's Home MCP documentation gives the server address https://home.googleapis.com/mcp and the OAuth scope https://www.googleapis.com/auth/home.platform.v2. Before an agent can connect, you create a Google Cloud project, enable the Home API, and set up a web application OAuth client with an external consent screen published under Google Auth Platform.
The server offers five tools: list_homes, list_home_resources, list_home_states, run_home_actions and list_home_history. Google says it enforces rate limits and blocks sensitive actions such as unlocking doors.
Access requires an active Google Home Premium Advanced subscription. TechCrunch reported the rollout starting on September 16, 2026, for US subscribers to the $20-per-month tier, and that Google would not say when it might expand.
Google also runs a separate Home Developer MCP server that searches its developer documentation and the Matter specifications. It is for building integrations and does not control devices.
How Port OS works
Port OS is a hosted MCP server at https://api.portoperatingsystem.com/mcp. You connect device providers once in Add a Device, then link your assistant from Link to AI and choose what it can read or control. The same devices are also available over the REST API.
For Google devices, Port OS connects to Nest through Google's Smart Device Management service, using a Device Access project you create. It can read temperatures, set supported thermostat targets and modes, and open live views on supported cameras and doorbells. It does not import every device in your Google Home. The Google Nest page lists the requirements and limits.
Port OS is in alpha, and its catalog does not cover every brand. Check that your exact model and the actions you need are listed before you rely on it. Contact the team for current pricing.
When to pick which
Pick Google Home MCP when Google Home already connects most of your devices, you have the Premium Advanced subscription in the US, and you are comfortable creating a Google Cloud project and OAuth client. Its history tool is useful if you want an agent to answer questions about what happened earlier.
Pick Port OS when your devices span brands that are in its catalog, when you want the same devices from ChatGPT, Claude and your own scripts, or when Google's early access is not available to you. You can also use both: Port OS for Hue, Sonos or Roborock, and Google Home MCP for the rest. Avoid sending conflicting commands to the same device from two systems while you test.
Whichever you choose, grant only the access the task needs, start with one named device, and check a fresh state reading after each change.
To set up Port OS, start with the smart home MCP overview. For Home Assistant and Homey as well, read smart home MCP servers compared.
References
- Google. “Google Home MCP Server.” Google Home Developers, developers.home.google.com/mcp/home. Accessed 2 Nov. 2026.
- Google. “Google Home Developer MCP Server.” Google Home Developers, developers.home.google.com/mcp/developer. Accessed 2 Nov. 2026.
- TechCrunch. “Your AI Agents Can Now Control Your Google Home Devices.” TechCrunch, 16 Sept. 2026, techcrunch.com. Accessed 2 Nov. 2026.
- Port OS. “Control Google Nest Thermostats and Cameras with AI.” Port OS, portoperatingsystem.com/integrations/google-nest. Accessed 2 Nov. 2026.