Atlassian's Official MCP Server: Jira, Confluence, and More via OAuth

Atlassian runs an official remote MCP server (github.com/atlassian/atlassian-mcp-server) that went generally available in February 2026, with Anthropic as its first official launch partner. It's a cloud-hosted bridge, not something you self-host, running on Cloudflare's infrastructure.

Everything It Connects, Not Just Jira

Despite the common shorthand of "Jira MCP," Atlassian's official server actually covers five products through one connection: Jira, Confluence, Jira Service Management, Bitbucket, and Compass. An agent connected once can read and write across all five, following whatever access the authenticating user already has.

Authentication: OAuth 2.1 or API Tokens

Every action taken through the server respects the connecting user's existing access controls — it authenticates via OAuth 2.1 or API tokens, and doesn't grant any elevated permission beyond what that person could already do directly in Jira or Confluence.

Real Uses This Actually Enables

With Claude connected to Atlassian's MCP server, genuinely useful real workflows include: reading a Jira ticket's full history and linked Confluence spec before drafting a fix, searching across Confluence documentation for prior art on a bug, or cross-referencing a Bitbucket pull request against its originating Jira ticket — all through natural language rather than manually opening each tool.

Community Alternatives Still Exist

Before Atlassian's official server reached GA, community projects like sooperset/mcp-atlassian filled the gap and remain available — worth knowing about if you need self-hosted control rather than depending on Atlassian's managed, cloud-hosted endpoint.