claude-swe-workflows vs SHIP
claude-swe-workflows is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑31.
claude-swe-workflows is a plugin bundle for AI coding tools published by Chris Allen Lane. No marketplace we read lists it any more. SHIP is an MCP server published by letsship.ai. 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 |   SHIP | |
|---|---|---|
| Community marketplace chrisallenlane/claude-swe-workflows | Removed on 2026-10-31 Version: 10.1.0 Forks (GitHub): 4 Stars (GitHub): 18 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.24.0 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 | claude-swe-workflowsno longer listed · | SHIP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 18 | 0 |
| Forks (GitHub) (differs) | 4 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.letsship.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 72 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/chrisallenlane/claude-swe-workflows | github.com/letsship/mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 1 h ago, requires authentication |
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 claude-swe-workflows
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Never re-explain your project to Claude again. devpace remembers context across sessions, manages requirement changes, and ensures quality gates — all automatically. Zero setup…
-
Engineering management layer for Claude Code --- structures your session like a real dev team where you're PM and Claude is EM. Provides session workflows, multi-persona code…
-
Session-level orchestration for Claude Code - structures development work into 5 typed waves (Discovery → Core → Polish → Quality → Finalization) with parallel subagent execution…
-
Essential agents and skills for Claude Code workflows - git commits, code simplification, security audits, verified multi-lens code review, thermo-nuclear code-quality review…
-
Production-grade engineering skills covering every phase of software development: spec, plan, build, verify, review, and ship.
-
Skills for common software engineering workflows including git operations, test fixing, code review implementation, and feature planning with plan-implementer agent
What each says it does
claude-swe-workflows
Software engineering workflows with skills for planning, implementation, quality review, and structured thinking, plus a suite of specialist agents
SHIP
Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.
How to run each
claude-swe-workflows
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SHIP As a remote MCP server
claude mcp add --transport http ship https://mcp.letsship.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SHIP 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: claude-swe-workflows · What it can do: SHIP · 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.