BYO-UI
Atlassian

Atlassian Jira / Confluence

Curated anchor platform in work management and knowledge with material relevance to the Marcom operating stack and a first-party developer surface.

Work & collaborationSystem of coordinationBYO-UI-ready platform
Representative source ↗Product site ↗
System roleSystem of coordination
Access maturityBYO-UI-ready platform
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Search, read, create and update Jira, Confluence, Bitbucket, Compass and Teamwork Graph information, including selected linked third-party development data, under existing product permissions

02 · Data you can retrieve

Search, read, create and update Jira, Confluence, Bitbucket, Compass and Teamwork Graph information, including selected linked third-party development data, under existing product permissions

03 · Actions and write paths

Atlassian Jira / Confluence's first-party MCP/agent surface includes state-changing tools in the documented capability area: Search, read, create and update Jira, Confluence, Bitbucket, Compass and Teamwork Graph information, including selected linked third-party development data, under existing product permissions. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

Official Atlassian docs confirm OAuth 2.1 as the primary method, optional admin-enabled API tokens, connected-product permission inheritance and admin control over allowed tools/domains. Official Atlassian docs confirm OAuth 2.1 as the primary method, optional admin-enabled API tokens, connected-product permission inheritance and admin control over allowed tools/domains.

05 · Monitoring, approval, and recovery

Official Atlassian docs confirm OAuth 2.1 as the primary method, optional admin-enabled API tokens, connected-product permission inheritance and admin control over allowed tools/domains. Official Atlassian docs confirm OAuth 2.1 as the primary method, optional admin-enabled API tokens, connected-product permission inheritance and admin control over allowed tools/domains. High-impact changes require review and audit monitoring.

06 · Gaps and implementation limits

Official Atlassian docs confirm OAuth 2.1 as the primary method, optional admin-enabled API tokens, connected-product permission inheritance and admin control over allowed tools/domains. High-impact changes require review and audit monitoring.

First-party access

Documented surfaces

Jira JQL ↗Jira Query Language supports structured issue search and query metadata through Jira Cloud APIs. Results remain constrained by Jira permissions and endpoint limits.Source: Jira Cloud JQL REST APIConfluence CQL ↗Confluence Query Language supports structured content search through Confluence Cloud APIs. JQL and CQL are distinct product query languages and inherit the requesting user's permissions.Source: Confluence Cloud search APIMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPAtlassian-hosted Rovo MCP ServerCurrent cloud service

Role: provider

Read scope: Search, read, create and update Jira, Confluence, Bitbucket, Compass and Teamwork Graph information, including selected linked third-party development data, under existing product permissions

Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.

Authentication: Official Atlassian docs confirm OAuth 2.1 as the primary method, optional admin-enabled API tokens, connected-product permission inheritance and admin control over allowed tools/domains.

Approval boundary: Official Atlassian docs confirm OAuth 2.1 as the primary method, optional admin-enabled API tokens, connected-product permission inheritance and admin control over allowed tools/domains.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability4
Observability3
Documentation5

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Atlassian ships these experiences.

Single-platform patterns

  • Campaign delivery, issue, and decision-log cockpit
  • Marketing launch room
  • Agent supervision inbox
  • Cross-functional approval workspace
Use in the brief composer →

Multi-platform compositions

  • Atlassian Jira / Confluence + campaign or CRM system: marketing launch room
  • Atlassian Jira / Confluence + content-production platform + analytics or automation system: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

7 recorded sources
Developer docsSource inventory
https://developer.atlassian.com/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Webhooks / extensionsSource inventory
https://developer.atlassian.com/cloud/jira/platform/webhooks/ ↗

First-party webhook, event, SDK, embedded-app, or extension documentation.

Publisher updated
Jul 10, 2026
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.atlassian.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Jira JQLTargeted review
Jira Cloud JQL REST API ↗

Jira Query Language supports structured issue search and query metadata through Jira Cloud APIs. Results remain constrained by Jira permissions and endpoint limits.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party access review

Confluence CQLTargeted review
Confluence Cloud search API ↗

Confluence Query Language supports structured content search through Confluence Cloud APIs. JQL and CQL are distinct product query languages and inherit the requesting user's permissions.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party access review

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.