Ext Ops Panel
Open dashboard
Comparison

xiao vs Chirp Home Automation

xiao is a plugin bundle for AI coding tools published by dacrypt. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Chirp Home Automation is an MCP server published by chirpwireless.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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

Where each is published
MarketplacexiaoChirp Home Automation
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: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

xiao vs Chirp Home Automation
FactxiaoChirp Home Automation
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp-auth.chirpwireless.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/dacrypt/xiaogithub.com/chirpwireless/chirp-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 16 h 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

In its own words, on Claude Code: claude-plugins-community:

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.

Chirp Home Automation

In its own words, on Official MCP Registry:

Check, add and control the smart home sensors and automations in your own Chirp home.

How to run each

xiao As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install xiao@claude-community

Chirp Home Automation As a remote MCP server

Claude Code
claude mcp add --transport http chirp https://mcp-auth.chirpwireless.io/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Chirp Home Automation 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: Chirp Home Automation · 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.

Where the data comes from: how the catalog is built