Skip to main content
The Atlassian integration connects Aperium to Jira and Confluence Cloud. Agents can search and read issues, projects, users, spaces, and pages, and — with approval — create and update Jira issues and Confluence pages. Each user links their own Atlassian account through OAuth.

​
How it connects

Atlassian is an OAuth (per-user) integration. An admin registers the OAuth client once; then each user links their own account from the Integrations page and consents to the requested scopes. Aperium’s driver uses the Atlassian 3LO authorization-code flow with PKCE. After the token exchange it calls Atlassian’s accessible-resources endpoint, so every Atlassian site the user can reach is captured under a single OAuth grant. Tools accept an optional site selector (cloud_id) to pick one site per call; the generated searches serve the connection’s default site.
1

Register the OAuth client (admin, once)

In the admin onboarding flow or the Admin Console’s MCP Servers tab, configure the Atlassian OAuth client (client ID, client secret, redirect URI).
2

Each user links their account

From the Integrations page, each user clicks Link Account, is redirected to Atlassian’s consent screen, and approves the requested Jira and Confluence scopes.

​
What agents can read

Seventeen read tools span both products:
  • Jira — JQL issue search, a typed issue search with filters, get issue, list transitions, and vocabulary lookups (statuses, priorities, issue types). A dynamic query surface exposes arbitrary fields discovered from your instance, including customfield_*.
  • Confluence — CQL search, get page, and current user.
  • Generated searches — projects, users, spaces, and pages, each a queryable dataset for filtering and counting.

​
What agents can write

Ten write tools are available, all approval-gated — the agent must surface the change for a human to approve before it executes:
Confluence purge permanently deletes a page rather than moving it to trash. Like every write here it requires explicit approval before it runs.
This connector serves Atlassian Cloud. Jira and Confluence Data Center are separate, experimental connectors with their own personal-token authentication.