Fo MCP lets agents control smart home devices
Fo MCP launched, letting an agent trigger a robot vacuum, have your CLI call you, or turn a lamp into a physical notification; the post also compares Google Home and Home Assistant MCP servers and flags security risks.
My smart lamp might start reminding me about meetings by shaking its head. That's not a joke, it's literally the pitch behind Fo MCP, launched this week: point an agent at Fo and it can nudge a vacuum cleaner into a deep clean, make your CLI call you with updates, or turn a lamp into a physical notification. Silly surface, real signal underneath. MCP just walked out of the terminal and into your living room. It's not the only one doing it. Google began rolling out an MCP server for Google Home on September 16, limited for now to its 20 dollar a month Premium Advanced tier in the US. Point Claude, ChatGPT, Hermes, OpenClaw or Google's own Antigravity at it and the agent can read camera summaries, control Nest and Matter devices by request, and build dashboards out of your event history, no YAML required. Home Assistant's open source MCP server does the same job for the DIY crowd: entities, automations and sensors exposed as a queryable model, with role based access control and sandboxed execution so an agent can dim your lights without being handed your front door lock. That's the detail I keep coming back to. Engadget flagged it the same week Google's rollout started: security researchers are already warning about weak points in MCP as adoption climbs, and a protocol built for reading code and calling APIs is now being wired directly into door locks, cameras and thermostats. The attack surface didn't shrink when MCP left the sandbox of a coding agent. It grew, and most of the guardrails being built around it, role based access, scoped permissions, explicit authorization for anything irreversible, are arriving after the fact, not before. I think this is the real test of MCP as a standard. Reading a repo and botching a function call is recoverable. Misreading a permission scope on a smart lock is not the same category of mistake, and the protocol is heading there faster than the safety work is. https://x.com/shivanipod/status/2112233722846355593
This post quotes another post: “Fo MCP lets AI agents control physical devices”