Ext Ops Panel
Open dashboard
Comparison

yakanban vs Atlassian MCP

yakanban is a plugin bundle for AI coding tools published by Antoine Ramponi. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Atlassian MCP is a plugin bundle for AI coding tools published by atlassian. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceyakanbanAtlassian MCP
Community marketplace aramponi/yakanban Not seen in the last pass
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: eb9a595
Forks (GitHub): 142
Stars (GitHub): 1 099
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 2.0.0
Forks (GitHub): 142
Stars (GitHub): 1 099
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 94a3043
Forks (GitHub): 142
Stars (GitHub): 1 099
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 Atlassian MCP
FactyakanbanAtlassian MCP
Marketplaces that list it (differs)1 (worse)4 (better)
Stars (GitHub) (differs)1 (worse)1 099 (better)
Forks (GitHub) (differs)0 (worse)142 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.atlassian.com/v2/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)27
Licence (differs)MITNot stated
Repository (differs)github.com/aramponi/yakanbangithub.com/atlassian/atlassian-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

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.

Atlassian MCP

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

Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.

How to run each

yakanban As a Claude Code plugin

Claude Code
/plugin marketplace add aramponi/yakanban
/plugin install yakanban@yakanban

Atlassian MCP As a Claude Code plugin

Claude Code
/plugin install atlassian@claude-plugins-official

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Atlassian MCP 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: Atlassian MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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