rokha vs io.github.homeassistant-ai/ha-mcp
rokha is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
rokha is a plugin bundle for AI coding tools published by Rokha. No marketplace we read lists it any more. io.github.homeassistant-ai/ha-mcp is an MCP server published by homeassistant-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.homeassistant-ai/ha-mcp | |
|---|---|---|
| Community marketplace aetherbytes/rokha-sdk | Removed on 2026-10-16 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 8.7.0 Downloads/month (PyPI): 229 725 Downloads/week (PyPI): 55 228 Forks (GitHub): 240 Stars (GitHub): 5 136 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 | rokhano longer listed · | io.github.homeassistant-ai/ha-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 5 136 |
| Forks (GitHub) (differs) | 0 | 240 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ha-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 10 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aetherbytes/rokha-sdk | github.com/homeassistant-ai/ha-mcp |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of rokha
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
mcp-gera-skills io.github.geraservicesuk/mcp-gera-skills
GeraSkills MCP — search and install robot capability packs on behalf of an operator.
-
dossier ai.imboard/dossier
MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers
-
Agent skills for Claude, Codex and Cursor: find, install and load skills from one connector.
-
skillmd com.skillmd/skillmd
Search, fetch, lint, and install Agent Skills (SKILL.md) from the SkillMD registry.
-
Search a registry of agent skills and MCP servers, then run them for real. No install, traced.
-
Build an MCP server and bundle your tools into a shareable plugin, end to end. Two skills: build-mcp scaffolds one server; build-plugin packages skills, hooks, agents, and MCP…
What each says it does
rokha
The Rokha MCP server plus the first-party skills: find a capability, run it, keep the trace.
io.github.homeassistant-ai/ha-mcp
Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
How to run each
rokha
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.homeassistant-ai/ha-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio ha-mcp -- uvx ha-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: rokha · What it can do: io.github.homeassistant-ai/ha-mcp · 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.