Ext Ops Panel
Open dashboard
Comparison

vibekanban vs Kagan

vibekanban is a plugin bundle for AI coding tools published by hoarchi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Kagan is an MCP server published by kagan-sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacevibekanbanKagan
Claude Code: claude-plugins-community Listed
Version: 520e6e3
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.11.2
Downloads/month (PyPI): 125
Downloads/week (PyPI): 68
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 12 (last published figure)
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

vibekanban vs Kagan
FactvibekanbanKagan
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub12 (last published figure)
Forks (GitHub) (differs)No figure on GitHub0 (last published figure)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (kagan)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/hoarchi/vibekanbangithub.com/kagan-sh/kagan
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

vibekanban

In its own words, on Claude Code: claude-plugins-community:

VibeKanban is a dev progress kanban board that runs entirely inside Claude Code. When you code with Claude, every task is automatically tracked — started, completed, and reported — on a local kanban board with a browser-based UI. No cloud service, no sign-up, no npm install. Just a Python server on localhost and a single HTML file. Claude creates tasks when you ask for work, moves them through columns as progress happens, records git diff stats on completion, and writes work reports you can review later in the web UI. Multi-project support lets you manage several codebases from one board. Switch between projects with tabs, drag cards between columns, and view completed work grouped by date, category, or development phase.

Kagan

In its own words, on Official MCP Registry:

AI-powered Kanban TUI for autonomous development workflows with agent orchestration

How to run each

vibekanban As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibekanban@claude-community

Kagan As a local MCP server: PyPI package

Claude Code
claude mcp add --env "KAGAN_ANTHROPIC_API_KEY=<YOUR_KAGAN_ANTHROPIC_API_KEY>" --env "KAGAN_OPENAI_API_KEY=<YOUR_KAGAN_OPENAI_API_KEY>" --transport stdio kagan -- uvx kagan

Requires: KAGAN_ANTHROPIC_API_KEY (secret), KAGAN_OPENAI_API_KEY (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 vibekanban publish no settings it asks for, so we do not compare settings.

What it can do: vibekanban · What it can do: Kagan · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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