LabscoMCP early access ↗
atlassianMCP SERVER · OFFICIAL PROJECT

Atlassian MCP Server

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

by atlassian ↗Project & Task Management✓ Official

These plugins include connection settings for this server:

LABSCO 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 part of the tool list — Jira Service Management needs an API token, Compass and code search need OAuth, and no single connection gets you both.

What it is

Atlassian's hosted MCP server. It connects an assistant to your Atlassian Cloud site — Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom, and platform data such as Goals, Projects, Teams, Focus and Talent — 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 addOrEditJiraIssueComment
  • The metadata an agent needs before it can create or move an issue: listJiraProjects, listJiraProjectIssueTypesMetadata, getJiraIssueTypeMetaWithFields, listJiraIssueLinkTypes and listJiraIssueTransitions
  • Time logged with addOrEditJiraIssueWorklog, sprints run with manageJiraSprint, and a person resolved to an account with lookupJiraAccountId
  • Confluence spaces and content — pages, blogs, live docs, whiteboards and databases — through listConfluenceSpaces, listConfluenceContent and getConfluenceContent, with searchConfluence for the search itself
  • Content written and revised with createConfluenceContent and updateConfluenceContent, and discussion through createConfluenceComment, updateConfluenceComment and listConfluenceComments
  • Loom videos, meeting action items and folders read, and videos uploaded, shared and commented on — getLoomVideo, getLoomMeetingActionItems, createLoomVideoUpload, shareLoomVideo, createLoomVideoComment
  • 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 getBitbucketRepoPullRequest, getBitbucketRepoPullRequestDiff, approveBitbucketRepoPullRequest, mergeBitbucketRepoPullRequest, createBitbucketRepoBranch, createBitbucketRepoCommit and runBitbucketRepoPipeline — pull requests read, created, approved, commented and merged, branches and commits made, pipelines run
  • search across Jira, Confluence and connected apps through Rovo, 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; Jira delete and manage stay off until an admin enables them

Requirements

An Atlassian Cloud site and an account on it. Clients connect to https://mcp.atlassian.com/v2/mcp and sign in over OAuth 2.1, or send an API token for headless setups; an IDE or local client that cannot reach a remote server directly also needs Node.js v18 or newer for the mcp-remote proxy. Jira Service Management tools work only with a scoped API token, which an organisation admin has to switch on first, and the Compass and code search tools work 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/v2/mcp