MCP server for the Yandex Smart Home (IoT) API: list and control devices, run scenarios, power-cycle smart sockets
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"yandex-iot-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# yandex-iot-mcp MCP ([Model Context Protocol](https://modelcontextprotocol.io)) server for the [Yandex Smart Home IoT API](https://yandex.ru/dev/dialogs/smart-home/) ([API reference](https://yandex.ru/dev/dialogs/smart-home/doc/en/concepts/platform-user-info)). Lets AI assistants (Claude Code, Claude Desktop, and any other MCP client) inspect and control devices connected to Yandex Smart Home / Alice. ## Tools | Tool | Description | | --- | --- | | `list_devices` | All devices with rooms, types, capabilities and sensor values | | `list_groups` | Device groups from the Yandex Home app | | `get_device` | Full state of one device, including online/offline | | `turn_on` / `turn_off` | On/off for sockets, lights, switches | | `power_cycle` | Off → wait N seconds → on. Hard-reset gear plugged into a smart socket | | `device_action` | Any capability action (range, mode, toggle, color_setting…) | | `list_scenarios` / `run_scenario` | Inspect and trigger scenarios | ## Getting an OAuth token 1. Create an app at [oauth.yandex.ru](https://oauth.yandex.ru): platform **Web services**, redirect URI `https://oauth.yandex.ru/verification_code`. 2. Grant it the **iot:view** and **iot:control** permissions ("Умный дом"). 3. Open `https://oauth.yandex.ru/authorize?response_type=token&client_id=<CLIENT_ID>` in a browser, authorize, and copy `access_token` from the address bar. ## Usage ### Claude Code ```bash claude mcp add yandex-iot --env YANDEX_IOT_TOKEN=<token> -- uvx yandex-iot-mcp ``` ### Claude Desktop ```json { "mcpServers": { "yandex-iot": { "command": "uvx", "args": ["yandex-iot-mcp"], "env": { "YANDEX_IOT_TOKEN": "<token>" } } } } ``` ### Example > "The server is frozen again — power-cycle the socket it's plugged into." The assistant finds the socket via `list_devices` and calls `power_cycle(device_id, off_seconds=10)`. ### From source ```bash uvx --from git+https://github.com/ssubbotin/yandex-iot-mcp yandex-iot-mcp ```…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.