Shelly Smart Home
PYPI · SHELLY-MCP
Local-first MCP server for Shelly smart-home devices (Gen1-Gen4): control, energy, automation.
Available components
Last scanned (16 hours ago)
Scores higher than 92% of PyPI servers
Category IoT and Hardware
Recent critical change
CVE-2026-32871 affects this package (3 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 27 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Buggy1111/shelly-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3215 tokens (~66/item across 48 items; 47 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −5
- Stability: pass → 0.63 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/shelly-mcp@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Buggy1111/shelly-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Buggy1111/shelly-mcp/.github/workflows/release.yml@refs/tags/v0.1.3 |
| Rekor log index | 3278463116 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:7c40b83c458a00dfb75628383de0c993679dfbfeeac33303a540d113e3e58614 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 27 packages
| Packages resolved | 27 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
shelly_cover_move ~80
Move a roller/cover: ``action`` is open|close|stop, or pass ``position`` (0-100) to go to it. Returns the post-action ``CoverState``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| channel | integer | – | – |
| device | string | yes | – |
| position | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_discover ~84
Discover Shelly devices on the LAN via mDNS, merged with the cloud account list. ``timeout_s`` is the mDNS browse window. Set ``use_cloud=false`` to skip the cloud list (LAN-only). Safe, read-only; returns lightweight identities (probe for detail).
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_s | number | – | – |
| use_cloud | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_energy_history ~99
Best-effort energy history: lifetime totals plus any per-minute series the device exposes in its status; notes when richer history needs a local connection. Detailed historical queries (Pro 3EM ``EMData``/CSV, Gen1 ``em_data.csv``) land with the local backends (M2) — over cloud only totals + recent by-minute are available.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | – | – | – |
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_energy_live ~77
Live power/energy per channel: power_w, voltage, current, pf, freq, totals. ``None`` where a device can't report it (e.g. Gen1 plugs have no voltage/current). Pass ``channel`` to narrow to one. Safe, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | – | – | – |
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_get_config ~87
Get a device's configuration, with credential fields masked as ``***`` (Gen1 ``/settings`` returns Wi-Fi/MQTT secrets in the clear — they must not reach the model). Local-first — the Shelly Cloud API can't expose config, so this returns an actionable error for cloud-only devices.
| Name | Type | Req | Description |
|---|---|---|---|
| component | – | – | – |
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_get_info ~49
Identify one device (generation, model, firmware, online state, capabilities). ``device`` is a device id or a configured name. Safe, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_get_status ~87
Get a device's **normalized** live status (Gen1/Gen2/Cloud folded into one shape). Returns canonical channels/lights/covers plus the raw per-generation payload. Pass ``component`` (e.g. ``"switch:0"``) to narrow to a single component. Safe, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| component | – | – | – |
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_kvs_delete ~48
Delete a KVS key. Requires ``confirm:true``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| device | string | yes | – |
| key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_kvs_get ~39
Get one KVS value (with its etag) by key.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_kvs_list ~46
List KVS keys (with their etags). ``match`` is a wildcard pattern (default all).
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| match | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_kvs_set ~44
Set a KVS key to a JSON value. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| key | string | yes | – |
| value | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_light_set ~136
Set a light/dimmer/RGB(W)/CCT channel (Gen1 /color,/light ↔ Gen2 Light/RGB/RGBW/CCT.Set). Only the provided fields are changed. ``brightness`` 0-100, ``rgb`` three 0-255 values, ``temp_k`` white colour temperature. Returns the post-action ``LightState``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| brightness | – | – | – |
| channel | integer | – | – |
| device | string | yes | – |
| on | – | – | – |
| rgb | – | – | – |
| temp_k | – | – | – |
| transition_s | – | – | – |
| white | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_list_components ~62
List the component keys present on a device (e.g. ['switch:0', 'input:0']). Safe, read-only. Use this to discover what a specific device exposes before reading status or controlling it.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_list_devices ~59
List every Shelly device known to this server (configured + cloud account). Safe, read-only. Returns each device's canonical identity (id, name, generation, model, online state) — the starting point before any status or control call.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
shelly_list_methods ~50
List the RPC methods a device supports (Gen2+ ``Shelly.ListMethods``). Returns an actionable error on Gen1/cloud where the device can't enumerate methods.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_rpc ~93
Call any **read-only** RPC method (``*.Get*``/``*.List*``/``*.Check*``) on a device. Mutating methods are refused here — use ``shelly_rpc_write``. The method name is classified server-side; unknown methods are treated as writes and rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| method | string | yes | – |
| params | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_rpc_write ~98
Call any **mutating** RPC method. Requires ``confirm:true``; audit-logged. Read methods are rejected (use ``shelly_rpc``). Destructive methods (factory reset, wipe-all, reset-wifi) need a second gate: ``params.i_understand_data_loss = true``.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| device | string | yes | – |
| method | string | yes | – |
| params | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_scene_create ~114
Define (save) a named scene from an ordered list of ``{device, method, params}``. Every method must be a non-destructive mutating method; every device must be known. Fails if the name already exists unless ``overwrite=true``. Prefer absolute ``Set`` methods over ``Toggle`` so the scene is safe to run twice (you'll get a warning otherwise).
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| description | – | – | – |
| name | string | yes | – |
| overwrite | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_scene_delete ~35
Delete a named scene. Requires ``confirm:true``.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_scene_get ~31
Show a scene's full definition (its ordered actions). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_scene_list ~24
List defined scenes (name, description, action count). Read-only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
shelly_scene_run ~111
Run a named scene: attempt every action in order, report per-action results. Best-effort and sequential — a failing action does **not** abort the rest. ``status`` is ``ok`` (all succeeded), ``partial`` (some failed), or ``failed`` (none succeeded). A partial run can simply be re-run later to finish it (scenes use absolute states, so re-running is safe). Every action is audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_schedule_create ~194
Create a schedule: ``timespec`` + ``calls`` (1-5 × {method, params}). ``timespec``: cron ``"sec min hour day month dow"`` (e.g. ``"0 0 22 * * MON-THU"``; 5 or 7 fields also accepted), a shorthand (``@daily``), or sun-relative ``"@sunset"``, ``"@sunset+30m"``, ``"@sunrise-1h * * MON-FRI"`` (offset max ±12 h; the device needs its location set). Validates the timespec, ≤5 calls, the ≤20-per-device limit, and each call's method. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | yes | – |
| device | string | yes | – |
| enable | boolean | – | – |
| timespec | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_schedule_delete ~49
Delete a schedule by ``id``. Requires ``confirm:true``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_schedule_list ~33
List the schedules configured on a device. Local-only (cloud can't manage schedules).
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_schedule_update ~55
Update fields of an existing schedule by ``id``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | – | – | – |
| device | string | yes | – |
| enable | – | – | – |
| id | integer | yes | – |
| timespec | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_create ~62
Create an empty script (optionally named). Returns its ``id``. Audit-logged. Use ``shelly_script_put_code`` to give it code (that step is confirm-gated).
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_delete ~49
Delete a script by ``id``. Requires ``confirm:true``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_eval ~66
Evaluate an expression inside a running script. **Arbitrary code** → ``confirm:true``. Returns the stringified result. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| confirm | boolean | – | – |
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_get_code ~45
Get a script's full source, reassembling the device's paginated ``GetCode``.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_list ~34
List scripts on a device (id, name, enable, running). Local-only.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_put_code ~99
Upload code into a script (chunked). **Arbitrary code on the device** → ``confirm:true``. ``append=false`` replaces the script body; ``true`` appends. Large code is split into ≤1 KB chunks automatically. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| append | boolean | – | – |
| code | string | yes | – |
| confirm | boolean | – | – |
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_start ~42
Start a script by ``id``. Returns ``was_running``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_script_stop ~42
Stop a script by ``id``. Returns ``was_running``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_switch_set ~70
Turn a switch/relay channel on or off (optionally auto-revert after N seconds). Returns the post-action ``ChannelState``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | – | – |
| device | string | yes | – |
| on | boolean | yes | – |
| toggle_after_s | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_switch_toggle ~44
Toggle a switch/relay channel. Returns the post-action ``ChannelState``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | – | – |
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_system_reboot ~46
Reboot a device. Requires ``confirm:true``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| delay_ms | – | – | – |
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_system_set_auth ~66
Enable/rotate the device login password (≥12 chars). Requires ``confirm:true``. The password is write-only — never returned, and redacted in the audit log.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| device | string | yes | – |
| password | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_system_update ~50
Trigger a firmware update (``channel`` = stable|beta). Requires ``confirm:true``.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | – |
| confirm | boolean | – | – |
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_version ~21
Return the shelly-mcp server version (health check).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
shelly_virtual_add ~75
Add a virtual component of ``type`` (boolean/number/text/enum/button/group). Optional ``config`` and ``id`` (200-299). Returns the new component id. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| config | – | – | – |
| device | string | yes | – |
| id | – | – | – |
| type | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_virtual_delete ~55
Delete a virtual component by ``key`` (``<type>:<cid>``). Requires ``confirm:true``.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| device | string | yes | – |
| key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_virtual_list ~34
List the device's virtual (dynamic) components via ``Shelly.GetComponents``.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_webhook_create ~120
Create a webhook: ``event`` (e.g. 'switch.on'), ``cid`` component id, ``urls`` 1-5. Optional ``condition`` (JS expression) and ``repeat_period`` (seconds; 0=always, negative=once). Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| cid | integer | yes | – |
| condition | – | – | – |
| device | string | yes | – |
| enable | boolean | – | – |
| event | string | yes | – |
| name | – | – | – |
| repeat_period | – | – | – |
| urls | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_webhook_delete ~50
Delete a webhook by ``id``. Requires ``confirm:true``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| device | string | yes | – |
| id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_webhook_list ~29
List webhooks configured on a device. Local-only.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
shelly_webhook_update ~66
Update fields of an existing webhook by ``id``. Audit-logged.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | – | – | – |
| device | string | yes | – |
| enable | – | – | – |
| id | integer | yes | – |
| name | – | – | – |
| repeat_period | – | – | – |
| urls | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Shelly Smart Home MCP server?
Shelly Smart Home runs locally as a PyPI package, launched with uvx shelly-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · shelly-mcp
claude mcp add buggy1111-shelly-mcp -- uvx shelly-mcp
What is the Shelly Smart Home MCP server?
Shelly Smart Home is an MCP server listed in the public MCP registry as io.github.Buggy1111/shelly-mcp. Local-first MCP server for Shelly smart-home devices (Gen1-Gen4): control, energy, automation. This page covers its PyPI package (shelly-mcp).
Is the Shelly Smart Home MCP server safe to use?
Shelly Smart Home scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Shelly Smart Home MCP server expose?
Shelly Smart Home exposes 47 tools: shelly_switch_set, shelly_switch_toggle, shelly_light_set, shelly_cover_move, shelly_energy_live, and 42 more. Their descriptions and schemas cost roughly 3,049 tokens of context every time the server is loaded.
Is the Shelly Smart Home MCP server still maintained?
Shelly Smart Home is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Shelly Smart Home MCP server under?
Shelly Smart Home declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.