01 · Records and state owned
Atlassian sites and cloud IDs, Jira work items and workflows, Confluence pages and spaces, Bitbucket repositories, Compass components, and Teamwork Graph objects and relationships.
Atlassian
AtlassianJira / Confluence
Atlassian Rovo MCP joins Jira work, Confluence knowledge, Bitbucket context, and Teamwork Graph relationships in one permissioned search, reading, and action surface.
Work & collaborationSystem of coordinationBYO-UI-ready platform
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.
02 · Data you can retrieve
Search and summarize Jira, Jira Service Management, Confluence, and Bitbucket; inspect workflow metadata; and retrieve linked Atlassian or third-party context through Teamwork Graph.
03 · Actions and write paths
Create or update Jira work items and Confluence pages, transition or comment on work, and add Teamwork Graph relationships when the relevant permission group is allowed.
04 · Authentication and permissions
OAuth 2.1 is primary; admins may enable personal API tokens or service-account keys for noninteractive use. Product permissions, OAuth scopes, and organization permission groups all apply.
05 · Monitoring, approval, and recovery
Organization admins can allow or block read, write, and search permission groups, including narrower actions. Existing product access remains authoritative; monitor audit logs for high-impact changes.
06 · Limits and caveats
Every product tool call requires a cloud ID discovered from the user's accessible resources. Tool availability varies by authentication method, scopes, products, and admin permission groups.
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 support
Official MCP serverAtlassian-hosted Rovo MCP ServerCurrent cloud service
Support: Official MCP server
Read scope: Expose only admin-allowed search and read groups across accessible cloud IDs, preserving product, project or space, entity type, and linked Teamwork Graph provenance.
Write scope: Allow only approved Jira, Confluence, or Teamwork Graph write groups; distinguish creation, content edits, workflow transitions, comments, and relationship changes in the interface.
Authentication: Interactive clients use OAuth 2.1 at Atlassian's hosted endpoint. Admin-enabled noninteractive clients may use a personal token with Basic auth or service-account key with Bearer auth.
Approval boundary: Confirm cloud site, project or space, target object, current state, and proposed diff before creation, page edits, issue transitions, comments, or graph relationship writes.
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 customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Atlassian ships them.
Single-platform patterns
- Campaign delivery, issue, and decision-log cockpit
- Marketing launch room
- Agent supervision inbox
- Cross-functional approval workspace
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
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
MCPRepresentative source
https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/ ↗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…
- Publisher published
- Jul 4, 2025
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Jun 15, 2024
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
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.
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.
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.
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 12, 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 12, 2026
Targeted first-party access review
Verified fact
Tied to cited first-party evidence reviewed for this profile.
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.