Ext Ops Panel
Open dashboard
Comparison

vibekanban vs Baton

vibekanban is a plugin bundle for AI coding tools published by hoarchi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Baton is an MCP server published by dudko.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplacevibekanbanBaton
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.1.3
Downloads/month (npm): 439
Downloads/week (npm): 78
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

vibekanban vs Baton
FactvibekanbanBaton
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@dudko.dev/baton-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/hoarchi/vibekanbangithub.com/dudko-dev/baton-mcp-setup
Changes in the last 7 days (differs)04
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.

Baton

In its own words, on Official MCP Registry:

Local MCP server for Baton: edit git-native API requests, collections, environments and scripts.

How to run each

vibekanban As a Claude Code plugin

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

Baton As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio baton -- npx -y @dudko.dev/baton-mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: vibekanban · What it can do: Baton · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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