The community gold standard for Jira + Confluence in Claude — search by JQL, file/transition tickets, read/write Confluence pages, all behind one stdio server.
MCP Atlassian is the most-starred third-party Atlassian connector, supporting both Cloud and Server/Data Center. It exposes JQL search, issue CRUD, transitions, comments, attachments, and the full Confluence Storage API. Auth via API token (cloud) or PAT (server). Scoped read-only mode is supported when you don't want write tools exposed.
claude mcp add mcp-atlassian-sooperset -- uvx mcp-atlassian
One-liner. Verify with claude mcp list. Remove with claude mcp remove.
Use Cases
Real-world ways to use MCP Atlassian
Triage a production error into a Jira ticket with linked Confluence runbook
👤 On-call engineers⏱ ~10 minintermediate
When to use: Sentry alert fired — you want a triaged Jira ticket and a runbook link, fast.
Prerequisites
API tokens — Atlassian → My Account → Security → API tokens
Flow
Search related
Atlassian: search Jira for issues containing 'NullPointerException OrderService' in the last 30 days. Also search Confluence for runbook pages mentioning OrderService.✓ Copied
→ Both result sets returned
Decide: dup or new
If there's an open BUG issue in last 14 days, comment on it with the new stack trace. Otherwise create a new BUG, link the runbook page, set priority High.✓ Copied
→ Either jira_add_comment or jira_create_issue called once
Hand off
Tell me the ticket key and short summary so I can post it in Slack.✓ Copied
→ ABC-1234 + 1-line summary
Outcome: Triaged ticket with runbook link in <2 minutes; no double-filing of duplicates.
Pitfalls
Stack trace pasted into Jira as plain text loses formatting — Wrap in {code} markers; the MCP forwards as-is
JQL injection via user input — Always quote string params; the tool escapes but be explicit
When to use: You've debated an approach in chat; want a Confluence page out of it.
Flow
Find the parent space
Atlassian: find the 'Engineering RFC' space. List its top-level pages.✓ Copied
→ Space + parent page identified
Compose
Create a new page under it titled 'RFC: switch from Redis to Valkey'. Sections: context, goals/non-goals, options considered, decision, plan. Use the discussion above as raw material.✓ Copied
→ confluence_create_page returns a URL
Outcome: Drafted RFC ready for review.
Pitfalls
Wrong parent page ID — Always confluence_search by space first
Bulk-clean stale tickets
👤 Eng managers⏱ ~30 minintermediate
When to use: Backlog has 200 zombies; you want them sorted.
Flow
Identify stale
JQL: project = PLAT AND status = Open AND updated < -90d. Limit 50.✓ Copied
→ List of stale issues
Propose action
For each, propose: close-stale, reassign-to-triage, or keep. Show me 10 at a time before transitioning.✓ Copied
→ Per-issue recommendation; you approve in batches
Apply
Close the ones I approved with a 'closing as stale' comment.✓ Copied
→ jira_transition_issue + jira_add_comment called per issue
Outcome: Backlog cleaned with audit trail per issue.
Pitfalls
Auto-closing legitimate-but-quiet tickets — Always batch + confirm before transition