Workplace

Atlassian MCP: Jira and Confluence for your agent

Atlassian's official hosted MCP server. Sign in with OAuth and agents search, read and create Jira issues and Confluence pages within your existing permissions.

Project and installation docs

View project

https://github.com/atlassian/atlassian-mcp-server

Finish a change, switch to the browser to find the Jira issue, update its status, then dig through Confluence for the spec: tab-switching eats a surprising share of the day. Atlassian’s official MCP server hands those steps to the agent. It’s a cloud service Atlassian hosts; you connect once with OAuth 2.1 or an API token, and the agent works in Jira, Confluence and other Atlassian products with your account’s permissions.

What it does

  • Products covered: Jira, Confluence, Jira Service Management, Bitbucket Cloud, Compass, Loom, plus platform data such as Goals, Projects and Teams.
  • Permission groups: tools are grouped as read, write and search (read_jira, write_jira, search_confluence and so on), and admins can toggle each group. delete_jira and manage_jira are off by default.
  • Tools on demand: only the most-used tools are exposed up front and clients discover the rest as needed, so context isn’t flooded. Gateways can request ?tools=all for a flat list.
  • Typical jobs: turn meeting notes or a spec into issues, summarize a Confluence space, check linked pull requests and deployments.

Who it’s for

  • Developers in Cursor or Claude Code who want the agent to look up issues, move them along and leave comments.
  • Project managers and leads who compile Jira progress or draft Confluence status reports.

Setup

Needs an Atlassian Cloud site. In Claude Code, add it, then run /mcp in a session to sign in:

claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp

Other clients just need the server URL https://mcp.atlassian.com/v2/mcp; the README has one-click installs for most of them.

Our take

There are many community Jira and Confluence servers, and sooperset/mcp-atlassian has more stars, but for Atlassian Cloud customers the official one is the safer pick. OAuth sign-in, permissions that follow the user, and org-level admin controls to audit and revoke access are what corporate IT needs before saying yes. The limits come from the same place: it’s Cloud only, so self-managed Server and Data Center sites still need a community server, and JSM tools accept API tokens only. The agent gets write access, so have it list its plan before bulk-creating or moving issues. Licensed Apache-2.0; about 1,100 stars as of 2026-10-06.