yakanban vs SHIP
yakanban is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
yakanban is a plugin bundle for AI coding tools published by Antoine Ramponi. 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-10-27. 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 aramponi/yakanban | Removed on 2026-10-16 Version: not stated Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.24.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | yakanbanno longer listed · | SHIP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 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) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aramponi/yakanban | github.com/letsship/mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago, requires a key |
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 yakanban
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Assess team workflows, build an operating repo, and design GitHub, Claude-native, Productboard, Atlassian, Google Workspace, or Microsoft 365 workflows.
-
Green Train dev-workflow skills: GitHub backlog governance as a manager loop (backlog-manager) — triage labels, append-only description completion, bounded ready queue (Todo ≤ 5…
-
agent-tasks io.github.keshrath/agent-tasks
Pipeline task management for AI agents - stages, dependencies, artifacts, claiming
-
Turn Claude Code into a problem-driven scrum team. You file problems as Linear issues; an agent team runs the empirical Scrum loop (scope, solve, review, adapt) and owns the…
-
Work on issues from GitHub, Linear, or GitLab
-
mcp-server-zuuna io.github.kenzotp/mcp-server-zuuna
MCP server for Zuuna: coding agents work your git-truth kanban board via the v1 API. 73 tools.
What each says it does
yakanban
Claims so two AI agents never grab the same ticket — on the GitHub or GitLab board your team already uses. Requires the yakanban CLI.
SHIP
Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.
How to run each
yakanban
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: yakanban · 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.