Ext Ops Panel
Open dashboard
Comparison

Atlassian vs Dev Workflow V2

Atlassian is an MCP server published by sooperset. Marketplaces we read that list it: 1 (Docker MCP Catalog). Dev Workflow V2 is a plugin bundle for AI coding tools published by NTCoding. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-11. 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
MarketplaceAtlassianDev Workflow V2
Docker MCP Catalog Listed
Version: sha256:ecec36c62279
Forks (GitHub): 1 449
Pulls (Docker Hub): 178 443
Stars (Docker Hub): 22
Stars (GitHub): 6 112
Not marked · First seen
Not listed
Community marketplace ntcoding/living-architecture Not listed Listed
Version: 0.0.153
Forks (GitHub): 21
Stars (GitHub): 140
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 Dev Workflow V2
FactAtlassianDev Workflow V2
Marketplaces that list it11
Stars (GitHub) (differs)6 112 (better)140 (worse)
Pulls (Docker Hub) (differs)178 443No figure on Docker Hub
Forks (GitHub) (differs)1 449 (better)21 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/atlassian)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)80Not published
Environment variables it asks for (differs)8, secrets among them: 4Not published
Hooks it runs (differs)Not published4
Parts of the bundle (differs)Not a bundle30
LicenceMITMIT
Repository (differs)github.com/sooperset/mcp-atlassiangithub.com/ntcoding/living-architecture
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-30

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.

Dev Workflow V2

In its own words, on Community GitHub marketplaces:

Event-sourced workflow state machine for a structured task lifecycle.

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)

Dev Workflow V2 As a Codex plugin

Codex
codex plugin marketplace add ntcoding/living-architecture

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

Tools each declares

The marketplaces of Dev Workflow V2 publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Atlassian · What it can do: Dev Workflow V2 · Compare two other plugins

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