hydra-swarm vs io.github.GoatInAHat/toolfactory
hydra-swarm is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
hydra-swarm is a plugin bundle for AI coding tools published by Tommy Cheung. No marketplace we read lists it any more. io.github.GoatInAHat/toolfactory is an MCP server published by GoatInAHat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 1tommycheung/hydra-swarm | Removed on 2026-10-18 Version: 0.6.8.5 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.6 Downloads/month (npm): 1 834 Downloads/week (npm): 631 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
| Fact | hydra-swarmno longer listed · | io.github.GoatInAHat/toolfactory |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (toolfactory) |
| 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) | 2 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/1tommycheung/hydra-swarm | github.com/goatinahat/toolfactory |
| Changes in the last 7 days | 4 | 4 |
| First seen (differs) | 2026-10-14 | 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 hydra-swarm
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Full Agent Swarm API and MCP server with local SQLite storage for multi-agent orchestration.
-
Endor Labs workflow agents and setup for Claude Code.
-
claude-flow io.github.ruvnet/claude-flow
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
-
agent-comm io.github.keshrath/agent-comm
Agent intercommunication - messaging, channels, shared state, and real-time events
-
Automated code review and swarm remediation for large changesets. Spawns adversarial reviewer agents, presents findings interactively, then dispatches fixer agents to remediate…
-
Bio-inspired swarm orchestrator for Claude Code. Breaks tasks into parallel subtasks, coordinates agents through stigmergy, learns across sessions with pheromone scoring, and…
What each says it does
hydra-swarm
Multi-agent (Claude, Codex, OpenCode/GLM, Kimi) local dev harness: worktree-isolated dispatch, trust-boundary promotion, cross-vendor review, evidence-gated integration.
io.github.GoatInAHat/toolfactory
Build an agent tool once; ship it as Agent Skills, MCP servers, Agent Plugins / Claude / Codex
How to run each
hydra-swarm
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.GoatInAHat/toolfactory As a local MCP server: npm package
claude mcp add --transport stdio toolfactory -- npx -y toolfactory
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: hydra-swarm · What it can do: io.github.GoatInAHat/toolfactory · 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.