Ext Ops Panel
Open dashboard
Comparison

yakanban vs io.github.kenzotp/mcp-server-zuuna

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. io.github.kenzotp/mcp-server-zuuna is an MCP server published by kenzotp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
Marketplaceyakanbanio.github.kenzotp/mcp-server-zuuna
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.3.0
Downloads/month (npm): 920
Downloads/week (npm): 30
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

yakanban vs io.github.kenzotp/mcp-server-zuuna
Factyakanbanno longer listed · io.github.kenzotp/mcp-server-zuuna
Marketplaces that list it (differs)01
Stars (GitHub) (differs)10
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-server-zuuna)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/aramponi/yakanbangithub.com/kenzotp/mcp-server-zuuna
Changes in the last 7 days00
First seen (differs)2026-10-142026-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 yakanban

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • SHIP

    Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.

    by letsship.ai · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • agentics-beyond-code

    Assess team workflows, build an operating repo, and design GitHub, Claude-native, Productboard, Atlassian, Google Workspace, or Microsoft 365 workflows.

    by Chris Butler · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • greentrain-dev

    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…

    by crazynomad · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • backlogd

    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…

    by nicolai-bernsen · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • agent-tasks io.github.keshrath/agent-tasks

    Pipeline task management for AI agents - stages, dependencies, artifacts, claiming

    by keshrath · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

  • issue

    Work on issues from GitHub, Linear, or GitLab

    by Ben Drucker · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

yakanban

In its own words, on Community GitHub marketplaces:

Claims so two AI agents never grab the same ticket — on the GitHub or GitLab board your team already uses. Requires the yakanban CLI.

io.github.kenzotp/mcp-server-zuuna

In its own words, on Official MCP Registry:

MCP server for Zuuna: coding agents work your git-truth kanban board via the v1 API. 73 tools.

How to run each

yakanban

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.kenzotp/mcp-server-zuuna As a local MCP server: npm package

Claude Code
claude mcp add --env "ZUUNA_API_TOKEN=<YOUR_ZUUNA_API_TOKEN>" --transport stdio mcp-server-zuuna -- npx -y mcp-server-zuuna

Requires: ZUUNA_API_TOKEN (secret)

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

The marketplaces of yakanban publish no settings it asks for, so we do not compare settings.

What it can do: yakanban · What it can do: io.github.kenzotp/mcp-server-zuuna · 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.

Where the data comes from: how the catalog is built