Atlassian (Jira/Confluence)
Last tested 2026-10-22
Score 83/100 · Last tested 2026-10-22 · Version tested 0.23.1 · Package mcp-atlassian · Repo sooperset/mcp-atlassian
Summary: Atlassian (Jira/Confluence) requires credentials or a backing service before it will list tools.
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install mcp-atlassian (Python venv, Linux) succeeded in 0s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 0 tools listed in 5.2s. |
| maintenance | partial | 15 | Repo pushed 32 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (PyPI long_description (package README)). |
| license | partial | 3 | License not machine-detected as OSI (None). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
Not tested
We did not test behavior with real credentials, security, or performance under load. These are planned; see methodology.
Tools listed
Not available (handshake did not complete without credentials).
Config used in our test
{
"mcpServers": {
"atlassian-jira-confluence": {
"command": "uvx",
"args": [
"mcp-atlassian"
]
}
}
}FAQ
Is Atlassian (Jira/Confluence) deprecated?
No. mcp-atlassian was not deprecated or archived when we last tested it on 2026-10-22.
What replaces Atlassian (Jira/Confluence)?
Nothing; Atlassian (Jira/Confluence) is not deprecated as of 2026-10-22.
Does Atlassian (Jira/Confluence) need an API key?
No. It completed an MCP handshake with no credentials and listed 0 tools.
Embed the badge
The badge always shows the current score; payment never changes it.