Jira & Confluence
Estimated reading time: 5 minutes
Connect Atlassian Cloud (Jira + Confluence) for sprint, issue, and documentation analytics. There are now two paths: the legacy native OAuth connectors (Jira and Confluence separately) and the unified Atlassian MCP connection in the MCP catalog.
Two Paths — Which to Pick
Recommendation: use the Atlassian MCP connection (Trial / Starter+).
Unified Jira + Confluence in a single MCP connection. Auto-discovers your sites, no project pre-selection needed, read scopes only. The native OAuth connectors below are still supported and remain the right choice if you're on Free or Lite (which don't include MCP), or if you need to scope explicitly to a subset of projects.
Path A: Atlassian MCP (Trial / Starter / Professional / Enterprise)
- Go to Settings → Data Sources → Connect MCP and pick Atlassian.
- Authorize on the Atlassian screen — read scopes for Jira and Confluence.
- clariBI discovers your accessible sites + projects + spaces automatically.
- Ask questions against either Jira or Confluence in plain English.
See the Atlassian MCP KB article for the full tool list and example queries.
Path B: Native Jira OAuth (every tier including Free)
If MCP isn't on your tier, or you want fine-grained project scoping, use the legacy native connector:
Connecting Jira (native)
Go to Data Sources and select Jira as the source type
Click Connect Jira Account. An authorization popup appears for your Jira Cloud instance.
After authorization, select which Jira projects to sync from the list of available projects
Enter a name for the data source and optionally choose a date range for the data to sync
Click Create Data Source to start the sync
Available Jira Data
- Issues (bugs, stories, tasks, epics) with status, priority, assignee
- Sprint data (velocity, burndown, completion rates)
- Time tracking (logged hours, estimates)
- Custom fields defined in your Jira projects
Confluence Data
Confluence data is accessed through clariBI's native Confluence OAuth integration. This connector supports syncing page content, creation dates, authors, and labels from your Confluence spaces.
Example Questions
The AI engine routes these against whichever Atlassian connection is live (MCP or native):
"How many bugs were opened vs. closed each week this quarter?"
"What is the average sprint velocity for the Frontend team?"
"Which team members have the most overdue issues?"
"Show me story point completion rate by sprint"
"List Confluence pages updated in the last 7 days under the Engineering space"
"Which Linear and Jira issues share the same labels?" (cross-source if both are connected)When to Use Which Path
| If you... | Pick |
|---|---|
| Want one connection covering Jira + Confluence + tier supports MCP | Atlassian MCP |
| Are on Free or Lite (no MCP catalog access) | Native Jira + native Confluence OAuth |
| Need to scope to a specific project subset only | Native Jira (project-level select at connect time) |
| Connect Confluence-only (no Jira) | Native Confluence OAuth |
| Connect Jira Server / Data Center (self-hosted) | REST API connector — neither native nor MCP support self-hosted Atlassian today |
Related
Ready to try clariBI?
Start your free 14-day trial. No credit card required.
Looking for step-by-step setup guides?
See our dedicated integration pages: Jira · Confluence