Skip to content
Connector Scout
–saved records

ChatGPT · Atlassian (Jira and Confluence)

Does Atlassian (Jira and Confluence) connect to ChatGPT?

Yes. OpenAI's ChatGPT Business release notes announce Atlassian Rovo as an MCP connector that brings Jira, Compass and Confluence information into chats and supports write actions in Jira such as creating issues and triggering workflows. OpenAI states that all actions are initiated, approved and completed in chat, and that the connector is available to Enterprise, Edu, Business, Pro and Plus customers with connectors enabled.

Verified availableDocumentation verifiedLast verified 8 Aug 2026MCP server
Compare connections

Quick answer

Yes — Atlassian (Jira and Confluence) connects to ChatGPT as a mcp server, verified against official documentation on 8 Aug 2026. Documentation confirms read, search, create and update access, while delete, sync and send remain not confirmed — which is different from unavailable. OpenAI's ChatGPT Business release notes announce Atlassian Rovo as an MCP connector that brings Jira, Compass and Confluence information into chats and supports write actions in Jira such as creating issues and triggering workflows.

Relationship
Official and documentation-verified
Confirmed access
Read, Search, Create and Update · delete, sync and send not confirmed
Plan or account
An Atlassian account with access to the relevant Jira, Compass and Confluence content
Setup and admin
ChatGPT Settings → Apps & Connectors
Last verified
8 Aug 2026
Best fit or limit
Write support is documented for Jira — creating issues and triggering workflows — not for Confluence or Compass.

What it is

OpenAI added Atlassian Rovo to its list of MCP connectors. The release note describes it as bringing Jira, Compass and Confluence information into ChatGPT to supply project context, and as enabling supported write actions in Jira — creating issues and triggering workflows — based on the request and on patterns identified in the project data. All actions are initiated, approved and completed directly in chat. Administrators review actions and basic connector information in Workspace settings, and users add the connector from ChatGPT's apps and connectors settings. OpenAI's own apps documentation adds the surrounding permission model: ChatGPT asks before taking actions that have a meaningful effect outside ChatGPT by default, and workspace admins can configure which actions an app may take.

Connection type Atlassian Rovo MCP connector with supported Jira write actions

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

OpenAI states the Atlassian Rovo connector is available to Enterprise, Edu, Business, Pro and Plus customers with connectors enabled for their workspace. Varies by app, plan, workspace, role, surface, and region; confirm in the current Plugin Directory.

Account requirements

  • An Atlassian account with access to the relevant Jira, Compass and Confluence content
  • A ChatGPT Enterprise, Edu, Business, Pro or Plus account with connectors enabled

How to connect

Setup path ChatGPT Settings → Apps & Connectors

  1. 1. Confirm workspace enablement

    Connectors must be enabled for the workspace; admins manage this centrally.

  2. 2. Add the connector

    Users add Atlassian Rovo from Settings → Apps & Connectors.

  3. 3. Authenticate Atlassian

    Authorise the Atlassian account whose permissions should apply.

  4. 4. Set the approval level

    Confirm the app permission setting so Jira write actions require approval before they run.

  5. 5. Review admin controls

    Admins review actions and connector information in Workspace settings.

Permissions, privacy, and admin controls

OpenAI documents that admins review actions and basic connector information in Workspace settings, and that workspace admins can configure which actions an app is allowed to take and when members must approve them.

  • Triggering a workflow changes shared delivery state; keep ChatGPT's approval prompt for important actions rather than disabling it.
  • One authorisation spans Jira, Compass and Confluence context, which is broader than a single project.
  • OpenAI documents that suspicious or hidden instructions in app content can cause ChatGPT to ask for approval or block a request — treat issue text as untrusted.

Platform context

  • OpenAI’s Plugin Directory is now the main discovery surface, while apps remain the integrations that connect ChatGPT to external data and actions. App capabilities and availability can vary by app, plan, workspace, role, surface, model, and region. Business workspace admins can manage apps; apps are enabled by default for Business and disabled by default for Enterprise/Edu. Enterprise/Edu can use role-based access controls. ChatGPT permissions do not give an app new provider permissions; they govern when ChatGPT asks before using access already granted. Voice mode does not currently support apps.

Documented limitations

  • Write support is documented for Jira — creating issues and triggering workflows — not for Confluence or Compass.
  • The set of supported Jira actions is not exhaustively enumerated in the release note.
  • Deletion is not documented.
  • Availability depends on plan and on connectors being enabled for the workspace.
  • Release-note capabilities change; re-verify before delivery reporting depends on this connector.

Best use cases

  • Bringing Jira and Confluence project context into a planning conversation
  • Creating Jira issues from an agreed decision, with approval in chat
  • Triggering a supported Jira workflow
  • Reviewing sprint context alongside documentation

Example prompts

  • “Summarise the open Jira issues in this project and the Confluence page that documents the release process”
  • “Create a Jira issue for the login defect we just discussed, and show it to me before you create it”
  • “What project context do you have from Jira and Compass for this workstream?”

Troubleshooting

  • The connector is not available to add

    Check the plan and that connectors are enabled for the workspace; OpenAI lists Enterprise, Edu, Business, Pro and Plus with connectors enabled.

  • ChatGPT will not perform a Jira action

    Only supported write actions are available, and admins can restrict which actions an app may take in Workspace settings.

  • An action ran without an explicit prompt

    Review the app permission setting; the default asks before actions with a meaningful effect outside ChatGPT, and 'Never ask' removes that confirmation.

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 OpenAI's ChatGPT Business release notes entry for the Atlassian Rovo MCP connector.

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 OpenAI or Atlassian. Confirm security-sensitive details against the vendor’s own documentation before rolling out access.