xiao vs Yeelight IoT MCP Server
xiao is a plugin bundle for AI coding tools published by dacrypt. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Yeelight IoT MCP Server is an MCP server published by Yeelight. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  xiao |  Yeelight IoT MCP Server |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.2 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 10 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | xiao | Yeelight IoT MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 10 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.yeelight.com/apis/mcp_server/v1/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/dacrypt/xiao | github.com/yeelight/yeelight-iot-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-12 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
xiao
Control a Xiaomi Robot Vacuum X20+ (model xiaomi.vacuum.c102gl) via the xiao CLI. Full vacuum control — start, stop, pause, dock, find, room cleaning, zone cleaning, base-station (mop wash/dry, dust collect, tray eject), consumable tracking, and settings (fan speed, water level, DND window). Agent-ready: ships with AGENTS.md, llms.txt, --json output on read commands, and canonical exit codes (2 = not configured, 77 = auth failed) for autonomous error recovery.
Yeelight IoT MCP Server
Yeelight device discovery, state, control, and scene execution.
How to run each
xiao As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install xiao@claude-communityYeelight IoT MCP Server As a remote MCP server
claude mcp add --transport http yeelight-iot-mcp https://api.yeelight.com/apis/mcp_server/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Yeelight IoT MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: xiao · What it can do: Yeelight IoT MCP Server · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.