Atlassian vs io.github.issuecapture/mcp-server
Atlassian is an MCP server published by sooperset. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.issuecapture/mcp-server is an MCP server published by issuecapture. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |   Atlassian | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ecec36c62279 Forks (GitHub): 1 395 Pulls (Docker Hub): 166 045 Stars (Docker Hub): 22 Stars (GitHub): 5 999 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.4 Downloads/month (npm): 126 Downloads/week (npm): 29 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
| Fact | Atlassian | io.github.issuecapture/mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 999 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 166 045 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 395 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/atlassian) | On your machine (@issuecapture/mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 80 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 4 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/sooperset/mcp-atlassian | github.com/issuecapture/issuecapture |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Atlassian
Tools for Atlassian products (Confluence and Jira). This integration supports both Atlassian Cloud and Jira Server/Data Center deployments.
io.github.issuecapture/mcp-server
Install the IssueCapture bug reporting widget for Jira. Auto-detects your framework.
How to run each
Atlassian As a local MCP server: Docker image
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/atlassianRequires: CONFLUENCE_API_TOKEN (secret), CONFLUENCE_PERSONAL_TOKEN (secret), JIRA_API_TOKEN (secret), JIRA_PERSONAL_TOKEN (secret)
io.github.issuecapture/mcp-server As a local MCP server: npm package
claude mcp add --transport stdio io-github-issuecapture-mcp-server -- npx -y @issuecapture/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.issuecapture/mcp-server publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.issuecapture/mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: Atlassian · What it can do: io.github.issuecapture/mcp-server · 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.