CloudeIDE vs io.github.Coolver/home-assistant-mcp
CloudeIDE is an MCP server published by cloudeide.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Coolver/home-assistant-mcp is an MCP server published by Coolver. 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 |  CloudeIDE |  io.github.Coolver/home-assistant-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Downloads/month (npm): 156 Downloads/week (npm): 21 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 3.2.12 Downloads/month (npm): 945 Downloads/week (npm): 177 Forks (GitHub): 7 Stars (GitHub): 58 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 | CloudeIDE | io.github.Coolver/home-assistant-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 58 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 7 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (cloudeide) | On your machine (@coolver/home-assistant-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cloudeide/cloudeide | github.com/coolver/home-assistant-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
CloudeIDE
Deploy from your terminal, and give an AI coding agent the same abilities over MCP.
io.github.Coolver/home-assistant-mcp
Vibecode your Home Assistant setup from your IDE: automations, dashboards, themes and configs
How to run each
CloudeIDE As a local MCP server: npm package
claude mcp add --env "CLOUDEIDE_TOKEN=<YOUR_CLOUDEIDE_TOKEN>" --transport stdio cloudeide -- npx -y cloudeide mcpRequires: CLOUDEIDE_TOKEN (secret)
io.github.Coolver/home-assistant-mcp As a local MCP server: npm package
claude mcp add --env "HA_AGENT_KEY=<YOUR_HA_AGENT_KEY>" --env "HA_AGENT_URL=<YOUR_HA_AGENT_URL>" --transport stdio home-assistant-mcp -- npx -y @coolver/home-assistant-mcpRequires: HA_AGENT_KEY (secret), HA_AGENT_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 CloudeIDE asks for
CLOUDEIDE_API_URLCLOUDEIDE_TOKEN (secret)
Only io.github.Coolver/home-assistant-mcp asks for
HA_AGENT_KEY (secret)HA_AGENT_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: CloudeIDE · What it can do: io.github.Coolver/home-assistant-mcp · Compare two other plugins
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.