Claude Atlassian connectorWhat Claude can do in your Atlassian account.
The Claude Atlassian connector exposes 21 tools. 12 read Jira, Confluence, Loom and Teamwork Graph, 9 create, update or delete. Below: what Claude can find, what it can change, which actions stay off until an admin opens them, and where calls are logged.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for teams that live in Jira and Confluence
Atlassian's server gives Claude a core set of Jira, Confluence, Loom, Rovo search and Teamwork Graph tools, and lets it discover more on demand, from Bitbucket to Goals and Teams. You ask a question or give an instruction in plain words; Claude finds the tickets, pages or videos, and acts with your existing Atlassian permissions.
From a vague memory to the right page. search looks across Jira, Confluence and connected apps in natural language, and getConfluenceContent reads the page it finds so Claude can summarise it.
Tickets handled from the chat. createJiraIssue files a bug from a conversation, transitionJiraIssue moves it along the workflow and addOrEditJiraIssueComment posts the update where the team will see it.
The whole story around an incident. getTeamworkGraphContext follows the links from a ticket to pull requests, deployments, Loom recordings and meetings, and getLoomVideo pulls the action items from the recording.
What Claude will not do here, unless your admin allows it. Jira deletions and project administration are off by default, and every action runs with your own Atlassian permissions. Each tool call is recorded in your organisation's audit log. Nothing runs on its own either: no tool fires when a ticket changes status. Rules of that kind belong to an automation tool, a different job, gathered on the Integrations hub. For another project tool, see the Claude asana connector.
Five words before you plug it in
The vocabulary you will meet while connecting Atlassian.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use later. Given once per person, and taken back the same way.
- Approval
- The confirmation Claude waits for before it goes through with a change to your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Atlassian.
Connecting Atlassian to Claude in three steps
- 01
Find Atlassian in Claude
In Claude's settings, open Customize, then Connectors, and look for Atlassian in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Atlassian in the window the service opens itself. If the link breaks later, Disconnect and connect again from the same row.
- 03
Read the authorization screen
Read Atlassian's screen before you accept it. It belongs to the service, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Atlassian account itself.
The 21 tools, sorted by what they do
Atlassian MCP gives Claude 21 tools: 12 that read your account, 9 that change something in it.
Two groups: what Claude reads, and what it creates, changes or deletes. Tool names stay as Claude shows them.
- 12 read
- 9 write
What Claude reads (12)
12 toolsTwelve tools that find and read Jira, Confluence, Loom and Teamwork Graph items without touching them.
atlassianUserInfo
Returns the account details of the person who connected. It tells Claude whose account, and so whose permissions, sit behind the connection.
getAccessibleAtlassianResources
Lists every Atlassian site and app your account can reach, with the identifier each one needs. Since your requests are aimed at a specific site, this list is what lets Claude point them at the right place.
discover
Searches, in plain language, the wider catalogue of Atlassian tools that are not loaded by default, and returns the ones that match with how to run them. It is how Claude reaches Bitbucket, Goals, Teams or Focus when a question needs them.
executeRead
Runs a reading tool that discover has found, outside the default set. Atlassian relies on which of the three execute tools is picked to apply confirmation at the agent level.
getJiraIssue
Fetches one Jira work item by its key or ID, with its fields. It is the quickest route when you already know which ticket you mean.
searchJiraIssuesUsingJql
Searches Jira work items with JQL, Jira's own query language. Claude builds the query from your plain question and brings back the matching tickets.
getConfluenceContent
Reads any piece of Confluence content: page, blog post, live doc, comment, whiteboard, database, embed or folder. Claude can then summarise it or answer questions about it.
searchConfluence
Searches Confluence content with CQL, Confluence's query language, built by Claude from what you ask. You never have to learn the syntax yourself.
getTeamworkGraphContext
Follows the links around any Atlassian item through Teamwork Graph: related work, people, pull requests, deployments, Loom videos, calendar events and third-party connections, in one pass.
getTeamworkGraphObject
Pulls all available data for one or more objects, Atlassian or third-party, from their identifiers or URLs. Where the context lookup shows links, this one opens the objects themselves, whether they live in Atlassian or elsewhere.
search
Runs a natural-language search across Jira, Confluence and connected apps through Rovo, Atlassian's search layer. Atlassian still labels it beta.
getLoomVideo
Reads a Loom video's core details and, on request, its transcript, comments, AI briefs, meeting action items or attached links.
What Claude creates, changes or deletes (9)
9 toolsNine tools that act on your Atlassian sites. No source describes a Claude-side confirmation for them: the general rule below applies.
executeWrite
Approval: see the ruleCarries out a change through a writing tool that discover has turned up. Writes get their own execute tool, and Atlassian uses that choice to apply agent-level confirmation.
executeDestructive
Approval: see the ruleHandles the deletion operations among the tools discover finds. The Jira delete group that feeds it is switched off by default.
createJiraIssue
Approval: see the ruleOpens a new Jira work item in the project you name, with the fields you give. Claude can draft the summary and description from the conversation first.
editJiraIssue
Approval: see the ruleChanges the fields of an existing Jira work item, limited to the fields that item allows editing.
transitionJiraIssue
Approval: see the ruleMoves a Jira work item to a new status, and can also place it in a sprint or back in the backlog.
addOrEditJiraIssueComment
Approval: see the ruleAdds a comment to a Jira work item, or edits one that already exists. Claude can write the text from the discussion you just had.
createConfluenceContent
Approval: see the ruleCreates Confluence content: a page, blog post, live doc, whiteboard, database, embed, smart link or folder, in the space you choose.
updateConfluenceContent
Approval: see the ruleUpdates pages, live docs, whiteboards or databases, either by replacing the whole body or through targeted edits.
addTeamworkGraphContext
Approval: see the ruleAdds a relationship between two objects in Teamwork Graph, so later searches and context lookups see them as connected.
What Claude checks with you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the chat, right when it matters.
On Team and Enterprise, the owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping reading open and closing writing, for instance. That setting applies to everyone and nobody works around it from their own account. On Atlassian's side, organisation admins grant or revoke each permission group, deletion and project administration stay off until they enable them, and every call lands in the audit log. Claude only has your Atlassian rights.
Which Claude plans include it
Out of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state of this one, check the connector's sheet in the official directory. Atlassian's own licensing, and Rovo credits, stay on Atlassian's side.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a ticket moves, a page is edited or a sprint closes.
Everything here comes from Atlassian's own support documentation and the directory description: neither Claude's help centre nor Anthropic's developer docs have a page on this connector. The tool list is an observed floor, not a promise, since an admin can open actions no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic writes on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. Here the floor is visible: Atlassian documents many more tools behind discover, each gated by the permission groups your admin opens.
Need help connecting Atlassian MCP to Claude?
A person reads every message.
