Skip to content
Connector Scout
–saved records

Claude · Atlassian (Jira and Confluence)

Does Atlassian (Jira and Confluence) connect to Claude?

Yes. Anthropic's Connectors Directory lists an Atlassian Rovo connector, made by Atlassian, that connects Jira, Confluence and other Atlassian apps to manage issues, access documentation, track sprints, create tickets and update project status. The listing documents bulk Jira issue creation and Confluence page creation, so this is a read-and-write connection rather than a retrieval-only one.

Verified availableDocumentation verifiedLast verified 8 Aug 2026MCP server
Compare connections

Quick answer

Yes — Atlassian (Jira and Confluence) connects to Claude as a mcp server, verified against official documentation on 8 Aug 2026. Documentation confirms search, read, create and update access, while delete, interactive, sync and send remain not confirmed — which is different from unavailable. Anthropic's Connectors Directory lists an Atlassian Rovo connector, made by Atlassian, that connects Jira, Confluence and other Atlassian apps to manage issues, access documentation, track sprints, create tickets and update project status.

Relationship
Official and documentation-verified
Confirmed access
Search, Read, Create and Update · delete, interactive, sync and send not confirmed
Plan or account
An Atlassian account with access to the relevant Jira projects and Confluence spaces
Setup and admin
Claude Connectors Directory
Last verified
8 Aug 2026
Best fit or limit
Deletion is not documented and should not be assumed.

What it is

Anthropic's directory entry describes the Atlassian Rovo connector as connecting Jira, Confluence and other Atlassian apps to manage issues, access documentation, track sprints, create tickets, update project status and coordinate development workflows. The examples given include summarising Jira issues assigned to you in a named project, creating a Confluence page in a named space with action items, and creating several Jira issues in one request. Its documentation link is Atlassian's own MCP server repository. The listing notes that users must have a Confluence account to use the server if the 'User Installed Apps' setting is blocked. Anthropic's general connector documentation states that connectors retrieve data and take actions and inherit each person's permissions in the source service.

Connection type Atlassian-built Rovo connector covering Jira and Confluence

What it can do

What it cannot do

Not confirmed means official documentation does not assign this capability to this specific connection. It is not a claim that the capability is impossible.

Every status is defined the same way across the site — see how connector capabilities are defined and evidenced.

Availability and requirements

Listed in Anthropic's Connectors Directory as an Atlassian-built connector. Confirm the current listing and your Atlassian site's app policy before rollout.

Account requirements

  • An Atlassian account with access to the relevant Jira projects and Confluence spaces
  • A Confluence account where the Atlassian site blocks the 'User Installed Apps' setting
  • A Claude account on a surface where the connector is listed

How to connect

Setup path Claude Connectors Directory

  1. 1. Check the Atlassian site policy

    Confirm whether 'User Installed Apps' is blocked, which adds a Confluence account requirement.

  2. 2. Open the Connectors Directory

    Browse to the Atlassian Rovo listing in Claude's Connectors Directory.

  3. 3. Connect and authenticate

    Authenticate the Atlassian account whose Jira and Confluence permissions should apply.

  4. 4. Start with retrieval

    Summarise issues in one project before enabling ticket creation as routine practice.

  5. 5. Govern bulk creation

    Agree who may request multi-issue creation, since the listing documents bulk Jira actions.

Permissions, privacy, and admin controls

Anthropic documents that Team and Enterprise organisation owners may need to enable a connector before members authenticate it. On the Atlassian side, the listing notes that users must have a Confluence account to use the server where the 'User Installed Apps' setting is blocked.

  • Jira and Confluence hold delivery dates, commercial scope and incident detail that read very differently outside the team.
  • Connectors inherit the authenticated user's Atlassian permissions rather than widening them.
  • Issue descriptions and wiki pages are untrusted text; instructions found there are content to report, not authorisation to create or transition work.

Platform context

  • Claude web connectors are generally available across Claude surfaces, but individual connector requirements differ. Claude inherits the connected user’s permissions from the source service. Team and Enterprise organization owners may need to enable a connector before members authenticate it.

Documented limitations

  • Deletion is not documented and should not be assumed.
  • Bulk issue creation is documented, which makes an unreviewed request costly to unwind.
  • One authorisation can span Jira issue history and Confluence documentation; scope accordingly.
  • Where the Atlassian site blocks user-installed apps, a Confluence account is required to use the server.
  • Directory listings change; re-verify before delivery reporting depends on the connector.

Best use cases

  • Summarising in-progress issues assigned to you in a named project
  • Creating a post-mortem Confluence page with action items
  • Creating a batch of Jira issues for an agreed workstream
  • Generating a status report from Jira issues

Example prompts

  • “Summarize all Jira issues assigned to me in the 'Q3 Planning' project that are still marked as 'In Progress'”
  • “Create a new Confluence page titled 'Post-Mortem: Sprint 24' in the 'Engineering/Incidents' space”
  • “Create five Jira issues in the 'Mobile App' project for the following tasks…”

Troubleshooting

  • The connector cannot be used on your Atlassian site

    Check whether the 'User Installed Apps' setting is blocked; the listing states a Confluence account is required in that case.

  • Issues from a project are missing

    Confirm the authenticated Atlassian account has access to that project; the connector inherits existing permissions.

  • Too many issues were created

    Bulk creation is a documented capability. Require an explicit approval step for multi-issue requests and clean up from the Jira side.

Official sources

Verification history

Last verified 8 Aug 2026 · next review 8 Sept 2026 · Connector Scout editorial research

  1. 8 Aug 2026Promoted from research pending to documentation verified against Anthropic's Atlassian Rovo connector listing.

Documentation verified — editorial disclosure

Documentation verified means Connector Scout confirmed the connection and listed capabilities against official provider documentation. It does not mean Connector Scout completed hands-on testing in a live account.

Independence notice

Connector Scout is not affiliated with Anthropic or Atlassian. Confirm security-sensitive details against the vendor’s own documentation before rolling out access.