Atlassian vs Project Context
Atlassian is an MCP server published by sooperset. Marketplaces we read that list it: 1 (Docker MCP Catalog). Project Context is an MCP server published by sandovalrr. 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
| Marketplace |   Atlassian |  Project Context |
|---|---|---|
| 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: 0.4.0 Downloads/month (npm): 220 Downloads/week (npm): 43 Forks (GitHub): 0 Stars (GitHub): 1 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 | Project Context |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 991 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 165 218 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 392 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/atlassian) | On your machine (@sandovalrr/project-context-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 80 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 4 | 3, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/sooperset/mcp-atlassian | github.com/sandovalrr/project-context |
| 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.
Project Context
Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.
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)
Project Context As a local MCP server: npm package
claude mcp add --transport stdio project-context -- npx -y @sandovalrr/project-context-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Project Context 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_URLCONFLUENCE_USERNAMEJIRA_API_TOKEN (secret)JIRA_PERSONAL_TOKEN (secret)JIRA_URLJIRA_USERNAME
Only Project Context asks for
PROJECT_CONTEXT_CONFIG_DIRPROJECT_CONTEXT_CWDPROJECT_CONTEXT_STATE_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Atlassian · What it can do: Project Context · 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.