What it does
Shelly Smart Home is an MCP server for Shelly smart-home devices across Gen1 to Gen4, and it can be used from MCP clients such as Claude Desktop, Claude Code and Cursor. It runs local-first, with cloud access as a fallback for devices off the local network. It provides one tool surface for Gen1 and Gen2+ devices, with read tools, control tools for switches, lights and covers, energy monitoring, and automation covering schedules, scripts, webhooks and KVS. It also offers a generic RPC engine, named scenes and auto-discovery of device capabilities.
It suits users who want an MCP client to query or switch Shelly devices, review energy readings, or run the same multi-device routine by name. Reads are marked read-only, every mutation is audit-logged, and destructive or irreversible operations require explicit confirmation flags, with a second gate for irreversible methods such as factory reset.
Setup starts with auto-discovery over mDNS on the local subnet. Named devices, devices on other subnets, passwords and cloud fallback are configured in a YAML file, which must be restricted to owner-only permissions when it holds a secret. Cloud access covers control, status and live energy only, while automation requires a local connection. Data is sent only to the user's own devices and, if enabled, their own Shelly Cloud account, with no telemetry.
Limitations and requirements
Unofficial community project, not affiliated with or endorsed by Allterco Robotics or Shelly; the project is in alpha and under development. Devices with a password need that password set in the configuration. mDNS discovery usually does not work under WSL or in containers, so devices must be configured by IP address there. Cloud-only devices cannot use schedules, scripts, webhooks or KVS. A configuration file containing a secret must have chmod 600 permissions or it will not load. Dedicated BLU tools are listed on the roadmap and are not yet available; BLU devices are reached through the gateway or the generic RPC engine. Cloud features require a personal Shelly Cloud account.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Shelly Smart Home
Local-first MCP server for Shelly smart-home devices (Gen1-Gen4): control, energy, automation.
v0.1.3As shown on registry.modelcontextprotocol.io when we last read it