Ext Ops Panel
Open dashboard
Comparison

Atlassian vs io.github.theluckystrike/kanban

Atlassian is an MCP server published by sooperset. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/kanban is an MCP server published by theluckystrike. 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
MarketplaceAtlassianio.github.theluckystrike/kanban
Docker MCP Catalog Listed
Version: sha256:ecec36c62279
Forks (GitHub): 1 402
Pulls (Docker Hub): 167 130
Stars (Docker Hub): 22
Stars (GitHub): 6 007
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.6
Forks (GitHub): 0
Stars (GitHub): 2
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

Atlassian vs io.github.theluckystrike/kanban
FactAtlassianio.github.theluckystrike/kanban
Marketplaces that list it11
Stars (GitHub) (differs)6 007 (better)2 (worse)
Pulls (Docker Hub) (differs)167 130No figure on Docker Hub
Forks (GitHub) (differs)1 402 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/atlassian)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declares (differs)80Not published
Environment variables it asks for (differs)8, secrets among them: 41, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/sooperset/mcp-atlassiangithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)011
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

Atlassian

In its own words, on Docker MCP Catalog:

Tools for Atlassian products (Confluence and Jira). This integration supports both Atlassian Cloud and Jira Server/Data Center deployments.

io.github.theluckystrike/kanban

In its own words, on Official MCP Registry:

A local task board per project: columns, due dates, estimates, priorities, overdue, weekly review.

How to run each

Atlassian As a local MCP server: Docker image

Claude Code
claude mcp add --env "CONFLUENCE_API_TOKEN=<YOUR_CONFLUENCE_API_TOKEN>" --env "CONFLUENCE_PERSONAL_TOKEN=<YOUR_CONFLUENCE_PERSONAL_TOKEN>" --env "JIRA_API_TOKEN=<YOUR_JIRA_API_TOKEN>" --env "JIRA_PERSONAL_TOKEN=<YOUR_JIRA_PERSONAL_TOKEN>" --transport stdio atlassian -- docker run -i --rm -e CONFLUENCE_API_TOKEN -e CONFLUENCE_PERSONAL_TOKEN -e JIRA_API_TOKEN -e JIRA_PERSONAL_TOKEN mcp/atlassian

Requires: CONFLUENCE_API_TOKEN (secret), CONFLUENCE_PERSONAL_TOKEN (secret), JIRA_API_TOKEN (secret), JIRA_PERSONAL_TOKEN (secret)

io.github.theluckystrike/kanban As a remote MCP server

Claude Code
claude mcp add --transport http kanban-todo-tasks-projects-board https://mcp.zovo.one/mcp/kanban --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MCP_LICENSE_KEY (secret), Authorization header

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

Only io.github.theluckystrike/kanban has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.theluckystrike/kanban publish no list of tools, so we do not compare tools.

Settings each asks for

Only Atlassian asks for

  • CONFLUENCE_API_TOKEN (secret)
  • CONFLUENCE_PERSONAL_TOKEN (secret)
  • CONFLUENCE_URL
  • CONFLUENCE_USERNAME
  • JIRA_API_TOKEN (secret)
  • JIRA_PERSONAL_TOKEN (secret)
  • JIRA_URL
  • JIRA_USERNAME

Only io.github.theluckystrike/kanban asks for

  • MCP_LICENSE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Atlassian · What it can do: io.github.theluckystrike/kanban · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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