crew vs StoriesOnBoard - structured specifications for AI Agents
crew is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
crew is a plugin bundle for AI coding tools published by Aradaev. No marketplace we read lists it any more. StoriesOnBoard - structured specifications for AI Agents is an MCP server published by storiesonboard.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 alex-radaev/engineering-os | Removed on 2026-10-15 Version: 0.2.0 Forks (GitHub): 1 Stars (GitHub): 0 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 | crewno longer listed · | StoriesOnBoard - structured specifications for AI Agents |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 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 (api.storiesonboard.com/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) | 10 | Not published |
| Parts of the bundle (differs) | 29 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/alex-radaev/engineering-os | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 3 days ago returned HTTP 401 |
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 crew
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Standalone Markdown-only Agent Team plugin for Claude Code and Codex. Coordination happens through ordinary Markdown files in the current project: agent-team/ ├──…
-
Shared task wall, memory, reports, channels and Dashboard for Claude Code and Codex; Claude Code plugin installation and an independent Codex adapter
-
Universal multi-agent project harness for Claude Code — run any project through a structured AI team from discovery to release.
-
Swarm orchestration workflows, curated knowledge skills, tiered worker agents, and fail-soft guardrail hooks.
-
Conductor v3 — Multi-agent orchestration with Evaluate-Loop, parallel execution, Board of Directors, and bundled SupaConductor skills for Claude Code
-
Hooks-based workflow orchestration for solo product development with Claude Code
What each says it does
crew
Structured multi-agent workflow plugin for Claude Code with explicit ownership and observability
StoriesOnBoard - structured specifications for AI Agents
Turn PRDs and product ideas into structured specs so coding agents build your intent, not theirs.
How to run each
crew
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
StoriesOnBoard - structured specifications for AI Agents As a remote MCP server
claude mcp add --transport http storiesonboard https://api.storiesonboard.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only StoriesOnBoard - structured specifications for AI Agents has a remote endpoint we check. How we check endpoints
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: crew · What it can do: StoriesOnBoard - structured specifications for AI Agents · 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.