deco-mcp vs Homebridge
deco-mcp is a plugin bundle for AI coding tools published by fullo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Homebridge is an MCP server published by mp-consulting. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  deco-mcp |  Homebridge |
|---|---|---|
| Community marketplace fullo/claude-plugins-marketplace | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.1.0 Forks (GitHub): 2 Stars (GitHub): 7 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 | deco-mcp | Homebridge |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 7 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@mp-consulting/homebridge-ai-kit) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 5, secrets among them: 2 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/fullo/deco-mcp | github.com/mp-consulting/homebridge-ai-kit |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-19 | 2026-10-18 |
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
deco-mcp
Manage TP-Link Deco mesh routers from Claude Code over the local API. Bundles an MCP server, three read-only diagnostic agents, and the deco-network skill.
Homebridge
Control Homebridge accessories and scenes, manage plugins and config.json, and read logs
How to run each
deco-mcp As a Claude Code plugin
/plugin marketplace add fullo/claude-plugins-marketplace
/plugin install deco-mcp@fullo-pluginsHomebridge As a local MCP server: npm package
claude mcp add --env "HOMEBRIDGE_PASSWORD=<YOUR_HOMEBRIDGE_PASSWORD>" --env "HOMEBRIDGE_TOKEN=<YOUR_HOMEBRIDGE_TOKEN>" --env "HOMEBRIDGE_URL=<YOUR_HOMEBRIDGE_URL>" --transport stdio homebridge-ai-kit -- npx -y @mp-consulting/homebridge-ai-kit mcpRequires: HOMEBRIDGE_PASSWORD (secret), HOMEBRIDGE_TOKEN (secret), HOMEBRIDGE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only deco-mcp asks for
DECO_HOSTDECO_PASSWORD (secret)
Only Homebridge asks for
HOMEBRIDGE_PASSWORD (secret)HOMEBRIDGE_READ_ONLYHOMEBRIDGE_TOKEN (secret)HOMEBRIDGE_URLHOMEBRIDGE_USERNAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: deco-mcp · What it can do: Homebridge · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.