1. Conduid
  2. IoT
  3. Shelly MCP Server
MCP server · IoT

Shelly MCP Server

MCP server for Shelly Plug

Unclaimed iot
37Low

Scored 16 days ago · breakdown

About Shelly MCP Server

Shelly MCP Server is an MCP server in the IoT category: mCP server for Shelly Plug.

Install

Claude Code
claude mcp add shelly-mcp-server -- npx -y shelly-mcp-server
npx
npx -y shelly-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (9)

shelly_cover_controlOpen, close, stop, or set position

Parameters not published.

shelly_discover_and_save_devicesDiscover devices and save to JSON

Parameters not published.

shelly_discover_save_and_validateDiscover, save, and validate connectivity

Parameters not published.

shelly_get_device_infoGet model and firmware info

Parameters not published.

shelly_get_statusGet full device status

Parameters not published.

shelly_list_devicesList configured devices

Parameters not published.

shelly_rpc_callCall any Shelly RPC method

Parameters not published.

shelly_switch_setTurn a relay on or off

Parameters not published.

shelly_update_device_credentialsBatch-apply credentials to saved devices

Parameters not published.

Ask AI

✦

Ask AI about Shelly MCP Server

Powered by Claude · Grounded in docs

I know everything about Shelly MCP Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

Shelly Local MCP Server

npm version npm downloads license github repo

MCP server for controlling Shelly Gen2+ devices over your local network.

Features:

  • automatic LAN discovery
  • strongly typed tools for status, switches, covers, and raw RPC calls

Requirements

  • Node.js 20+
  • npm 10+
  • Shelly Gen2+ devices reachable on your LAN

Install and run

You can run this server in two common ways.

Option A: standalone clone (recommended while developing)

git clone https://github.com/jdgoeij/shelly-mcp-server.git
cd shelly-mcp-server
npm install
npm run build

MCP client config example:

{
  "mcpServers": {
    "shelly-local": {
      "command": "node",
      "args": ["./dist/index.js"],
      "cwd": "/absolute/path/to/shelly-mcp-server",
      "env": {
        "SHELLY_DEVICES_FILE": "./devices.local.json",
        "SHELLY_DISCOVERY_CONFIG_FILE": "./discovery.config.json",
        "SHELLY_TIMEOUT_MS": "5000"
      }
    }
  }
}

Option B: run from npm with npx

Now that the package is published, users can run it without cloning:

  • latest release:
{
  "mcpServers": {
    "shelly-local": {
      "command": "npx",
      "args": ["-y", "shelly-mcp-server"],
      "cwd": "/absolute/path/to/shelly-config",
      "env": {
        "SHELLY_DEVICES_FILE": "./devices.local.json",
        "SHELLY_DISCOVERY_CONFIG_FILE": "./discovery.config.json",
        "SHELLY_TIMEOUT_MS": "5000"
      }
    }
  }
}
  • pinned version (recommended for reproducible setups):
{
  "mcpServers": {
    "shelly-local": {
      "command": "npx",
      "args": ["-y", "shelly-mcp-server@0.1.0"],
      "cwd": "/absolute/path/to/shelly-config",
      "env": {
        "SHELLY_DEVICES_FILE": "./devices.local.json",
        "SHELLY_DISCOVERY_CONFIG_FILE": "./discovery.config.json",
        "SHELLY_TIMEOUT_MS": "5000"
      }
    }
  }
}

Important:

  • keep cwd pointed at a persistent folder where config/data files live
  • the server reads and writes relative paths from that folder

First-time setup for either option

Create local config files in your chosen cwd folder:

discovery.config.json

{
  "cidr": "192.168.1.0/24",
  "merge": true,
  "timeoutMs": 1500,
  "concurrency": 32,
  "maxHosts": 512,
  "validateTimeoutMs": 5000
}

Then ask your MCP client assistant:

Discover and validate my Shelly devices on 192.168.1.0/24

This creates or updates devices.local.json.

Environment variables

Variable Default Description
SHELLY_DEVICES_FILE ./devices.local.json Path to persisted device inventory
SHELLY_DISCOVERY_CONFIG_FILE ./discovery.config.json Path to discovery defaults
SHELLY_TIMEOUT_MS 5000 RPC timeout in milliseconds

Available tools

Tool Description
shelly_list_devices List configured devices
shelly_get_status Get full device status
shelly_get_device_info Get model and firmware info
shelly_switch_set Turn a relay on or off
shelly_cover_control Open, close, stop, or set position
shelly_rpc_call Call any Shelly RPC method
shelly_discover_and_save_devices Discover devices and save to JSON
shelly_discover_save_and_validate Discover, save, and validate connectivity
shelly_update_device_credentials Batch-apply credentials to saved devices
  • Run this server only on trusted machines.
  • Never commit .env, devices.local.json, or cloud credentials.
  • Review MCP client config before sharing screenshots or logs.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Shelly MCP Server

How do I install Shelly MCP Server?

Run claude mcp add shelly-mcp-server -- npx -y shelly-mcp-server, then add the server to your MCP client's configuration.

Is Shelly MCP Server safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Shelly MCP Server still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.