Skip to content

Comparison

Side-by-side comparison

Compare up to three connection records. “Not verified” or “Not confirmed” means the detail has not been documented in the sources we reviewed — never that it is unavailable. Records are reviewed against official documentation, not hands-on tested.

Comparison of selected connection records
AttributeAtlassian (Jira and Confluence) on ChatGPTAtlassian (Jira and Confluence) on ClaudeAtlassian (Jira and Confluence) on Gemini
AvailabilityVerified availableVerified availableVerified available
Connection typeAtlassian Rovo MCP connector with supported Jira write actionsAtlassian-built Rovo connector covering Jira and ConfluenceTwo separate Google Cloud connectors for Gemini Enterprise — Jira Cloud and Confluence Cloud — not a single Atlassian connector and not a connected app in the Gemini app
Capabilities
  • Read: Supported
  • Search: Supported
  • Create: Supported
  • Update: Limited / conditional
  • Delete: Not confirmed
  • Send: Not confirmed
  • Sync: Not supported
  • Search: Supported
  • Read: Supported
  • Create: Supported
  • Update: Supported
  • Delete: Not confirmed
  • Interactive: Not confirmed
  • Sync: Not confirmed
  • Send: Not confirmed
  • Search: Supported
  • Read: Supported
  • Create: Supported
  • Update: Supported
  • Delete: Not confirmed
Setup methodChatGPT Settings → Apps & ConnectorsClaude Connectors DirectorySeparate Gemini Enterprise Jira Cloud and Confluence Cloud data stores, each configured by an administrator
Admin involvementOpenAI 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.Anthropic documents that Team and Enterprise organization 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.Required for each connector separately. An administrator creates and authorizes a Jira Cloud data store and, independently, a Confluence Cloud data store inside a Gemini Enterprise app; there is no user-level toggle in the Gemini app and enabling one does not enable the other.
LimitationsWrite 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.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.Google documents Jira Cloud and Confluence Cloud as two separate Gemini Enterprise connectors; there is no single combined Atlassian or Rovo connector, so a site missing one connection will not surface that product's content.; This is a Gemini Enterprise connector; Google does not document Jira or Confluence as connected apps in the Gemini app at gemini.google.com.; Neither connector documents a delete action for issues, pages, projects or spaces.; Available actions depend on what an administrator enables per connector, so end users may see a narrower set than Google's full documented list for either product.
Documentation review
Verification status: Review overdue — The scheduled documentation review date has passed (or, without a schedule, the last review is over 90 days old). Re-check the official source before relying on details.

Last reviewed 9 Sept 2026

Next review 9 Oct 2026

Verification status: Review overdue — The scheduled documentation review date has passed (or, without a schedule, the last review is over 90 days old). Re-check the official source before relying on details.

Last reviewed 9 Sept 2026

Next review 9 Oct 2026

Verification status: Review overdue — The scheduled documentation review date has passed (or, without a schedule, the last review is over 90 days old). Re-check the official source before relying on details.

Last reviewed 9 Sept 2026

Next review 9 Oct 2026