Ext Ops Panel
Open dashboard
Comparison

Atlassian vs Linear MCP by usefulapi

Atlassian is an MCP server published by sooperset. Marketplaces we read that list it: 1 (Docker MCP Catalog). Linear MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceAtlassianLinear MCP by usefulapi
Docker MCP Catalog Listed
Version: sha256:ecec36c62279
Forks (GitHub): 1 392
Pulls (Docker Hub): 165 218
Stars (Docker Hub): 22
Stars (GitHub): 5 991
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.10.1
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

Atlassian vs Linear MCP by usefulapi
FactAtlassianLinear MCP by usefulapi
Marketplaces that list it11
Stars (GitHub) (differs)5 991 (better)0 (worse)
Pulls (Docker Hub) (differs)165 218No figure on Docker Hub
Forks (GitHub) (differs)1 392 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/atlassian)Remote server (linear.usefulapi.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)80Not published
Environment variables it asks for (differs)8, secrets among them: 4Not published
Licence (differs)MITNot stated
Repository (differs)github.com/sooperset/mcp-atlassiangithub.com/m190/usefulapi-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

Linear MCP by usefulapi

In its own words, on Official MCP Registry:

Search, read and create Linear issues, projects, teams and cycles.

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)

Linear MCP by usefulapi As a remote MCP server

Claude Code
claude mcp add --transport http linear https://linear.usefulapi.io/mcp

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

Tools each declares

The marketplaces of Linear MCP by usefulapi publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Linear MCP by usefulapi publish no settings it asks for, so we do not compare settings.

What it can do: Atlassian · What it can do: Linear MCP by usefulapi · 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