Labsco
MCP SERVER · OFFICIAL PROJECT

Atlassian MCP Server

by atlassian ↗

Ask about a Jira issue or a Confluence page, and move it forward, from whatever assistant you already use.

Project & Task Management✓ Official source
Summary
Your Atlassian permissions, handed to an assistant unchanged.

Signing in over OAuth 2.1 means the server can do what you can do, creating and transitioning issues included. The split worth knowing before you connect is that the authentication method decides the product list — a token gets you Jira Service Management and Bitbucket, OAuth gets you Compass, and neither gets you both.

What it is

Atlassian's hosted MCP server. It connects an assistant to your Atlassian Cloud site — Jira, Jira Service Management, Confluence, Bitbucket and Compass — with your own permissions in force on every call, including your organisation's IP allowlist.

What you get
  • Jira issues read with getJiraIssue, searched with searchJiraIssuesUsingJql, and created, edited, transitioned and commented on through createJiraIssue, editJiraIssue, transitionJiraIssue and addCommentToJiraIssue
  • The metadata an agent needs before it can create or move an issue: getVisibleJiraProjects, getJiraProjectIssueTypesMetadata, getJiraIssueTypeMetaWithFields, getIssueLinkTypes and getTransitionsForJiraIssue
  • Time logged with addWorklogToJiraIssue, and a person resolved to an account with lookupJiraAccountId
  • Confluence spaces and pages through getConfluenceSpaces, getPagesInConfluenceSpace, getConfluencePage and getConfluencePageDescendants, with searchConfluenceUsingCql for the search itself
  • Pages written and revised with createConfluencePage and updateConfluencePage, and discussion through createConfluenceInlineComment, createConfluenceFooterComment and the calls that read existing comments back
  • Compass components read and created — getCompassComponents, createCompassComponent, createCompassComponentRelationship — with component types, labels, activity events and custom field definitions
  • Jira Service Management operations through getJsmOpsAlerts, updateJsmOpsAlert, getJsmOpsTeamInfo and getJsmOpsScheduleInfo, for acknowledging, closing or escalating an alert and reading who is on call
  • Bitbucket Cloud through bitbucketRepository, bitbucketPullRequest, bitbucketRepoContent, bitbucketPipeline, bitbucketDeployment, bitbucketEnvironment, bitbucketWorkspace and bitbucketUser — pull requests read, created, approved, commented and merged, branches and commits made, pipelines run
  • searchAtlassian across products, and getTeamworkGraphContext, getTeamworkGraphObject and addTeamworkGraphContext on the platform layer
  • getAccessibleAtlassianResources for the cloudId every other call needs, and atlassianUserInfo for who the session is acting as
  • Permission groups an organisation admin grants or revokes as a unit — read, write and search per product — with every tool inheriting its group's access
Requirements

An Atlassian Cloud site and an account on it. Clients connect to https://mcp.atlassian.com/v1/mcp/authv2 and sign in over OAuth 2.1; an IDE or local client also needs Node.js v18 or newer, because it reaches the endpoint through the mcp-remote proxy. Which products you get depends on how you authenticate: Jira Service Management and Bitbucket Cloud tools work only with a scoped API token, which an organisation admin has to switch on first, and Compass works only over OAuth. Every tool call needs a cloudId, so getAccessibleAtlassianResources is the first call any client makes.

Setup effort

One command — claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2