hames vs MagicChat
hames is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
hames is a plugin bundle for AI coding tools published by Baek Labs. No marketplace we read lists it any more. MagicChat is an MCP server published by theindianappguy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 | ||
|---|---|---|
| Community marketplace baek-labs/hames | Removed on 2026-10-20 Version: 3.0.0 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | hamesno longer listed · | MagicChat |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (www.magicchat.ai/api/mcp/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/baek-labs/hames | Not stated |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-17 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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 hames
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Swarm orchestration workflows, curated knowledge skills, tiered worker agents, and fail-soft guardrail hooks.
-
Cross-model AI agent communication protocol. Connect Claude, Codex, and Gemini agents through a shared file-based messaging layer. Features include: control tower orchestration…
-
Structured thinking, evidence-first planning, diagnosis, technical research, and documentation capture for AI agents.
-
A personal RAG database you build from chat, so AI creates work that sounds like you.
-
Build and maintain a persistent AI-tended research wiki. Includes MCP server with 49 tools, slash commands, sub-agents, and an auto-context-injection hook.
-
EverOS memory for Claude Code - automatic recall, capture and session seal against a local EverOS server.
What each says it does
hames
A user-shaped AI workspace with automatic indexes and built-in workflows
MagicChat
Manage AI support chatbots: train on webpages and text, search knowledge, view leads and questions.
How to run each
hames
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MagicChat As a remote MCP server
claude mcp add --transport http magicchat-mcp https://www.magicchat.ai/api/mcp/mcp
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
Neither one's marketplaces publish the settings it asks for.
What it can do: hames · What it can do: MagicChat · 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.