Atlassian MCP Server (Jira & Confluence)

What it does

• Read/write Jira issues — create, comment, transition, and assign through natural language
• Confluence page search, read, and update for pulling specs and runbooks into context
• JQL and CQL search exposed as tools — Claude can work a triage queue end to end
• Supports Jira/Confluence Cloud (API token) and Data Center / Server (personal access token)

When to use it

Best for sprint ops from the chat side: standup prep from your assigned queue, turning a discussion into a ticket, pushing release notes into Confluence. A read-only deployment works well for reporting and analytics assistants.

Getting started

uvx mcp-atlassian

Credentials via ATLASSIAN_* environment variables — API token (email + token) for Cloud, personal access token for Data Center/Server. See the README table for the exact variable set per deployment type.

Things to know

Write tools can transition and edit real tickets — start read-only if the agent feeds dashboards rather than doing ops. Token scope maps to the Atlassian user; use a service account rather than a personal admin token.