Skip to main content
Jira Cloud (OAuth) connects your organization’s issues, projects, boards, and sprints to Airia agents, backed directly by Atlassian’s own REST API. Each person connects with their own Atlassian account, and access follows Jira’s own permissions on top of whatever scopes the connection is granted.

​
What It Can Do

See Tools and Required Scopes below for the full list of tools behind these capabilities.

​
Connecting

1

Register an OAuth app

Go to the Atlassian Developer Console and select Create → OAuth 2.0 integration. Give the app a name, for example “Airia Jira,” and save.
2

Add the callback URL

Select Authorization in the left sidebar, then click Add next to OAuth 2.0 (3LO). Add the following callback URL and save:
3

Add API permissions

Select Permissions in the left sidebar, click Add next to the Jira API, and enable every scope listed under Tools and Required Scopes below. The Granting All Scopes section has both scope lists ready to paste in.
4

Copy your credentials

Select Settings and copy the Client ID and Secret.
5

Find your Cloud ID

Your Cloud ID is a UUID Airia uses to reach your specific Jira site. Visit the following URL, replacing {your-site} with your Atlassian domain, and copy the cloudId value from the response:
6

Add it to Airia

Add Jira Cloud (OAuth) as a server on a Gateway or Deployment, then enter your Client ID, Client Secret, and Cloud ID.
The OAuth Scopes field in Airia is optional. Leave it blank to request the standard scopes above, or fill it in to request a different set. If you customize it, make sure to include offline_access so your connection can refresh automatically.

​
Tools and Required Scopes

Every tool below needs a specific Jira scope before it will work. Tool names are what an agent actually calls, the same names you’d see in an agent’s tool call log.
Atlassian scopes come in two flavors. Classic scopes are broad and recommended, granting one alone is enough for every tool that lists one. Granular scopes are narrower and only needed if you’re building an OAuth app without classic scopes, in which case a tool needs every listed granular scope granted together. A few tools, mostly Jira Software board and sprint tools, have no classic equivalent at all and always need their granular scope(s) regardless of which approach you use.

​
Issues

​
Comments

​
Attachments

​
Worklogs

​
Watchers

​
Votes

​
Projects

​
Components

​
Versions

​
Boards

Jira Software’s agile endpoints (Boards and Sprints) have no classic scope equivalent. Their granular scopes are always required, even if you otherwise use classic scopes for everything else.

​
Sprints

​
Users

​
Reference Data

​
Filters

​
Dashboards

​
Granting All Scopes

If you’d rather not cross-reference the table above tool by tool, enable every scope below in the Atlassian console and every tool becomes available at once. Classic scopes
Granular scopes
Together, these two short lists cover every tool in the reference above. The five Classic scopes cover every tool that lists a Classic option, and the Granular list adds the handful of scopes Jira Software’s Boards and Sprints tools need, since those have no Classic equivalent. You don’t need to hunt down the long Granular lists shown per tool above unless you’re deliberately building an OAuth app that avoids Classic scopes entirely.

​
Troubleshooting

Check the Tools and Required Scopes table above for the exact scope that tool needs, add it to your app registration, and reconnect.
This happens when offline_access wasn’t included in the granted scopes, so Airia has no way to refresh the session. If you customized the OAuth Scopes field in Airia, add offline_access back in and reconnect.

​
Learn More

​
Jira Cloud (API Token)

Airia also offers Jira Cloud (API Token), a separate, Restricted server that most organizations will never see or need. It’s not enabled by default. If you want to use it, talk to your Airia contact about adding it to your tenant, after which a Platform Admin, Admin, or Security Admin can turn it on from Server Management using Add Restricted Server.
It exposes the exact same tools as Jira Cloud (OAuth) above, using a different way of authenticating: every request runs as whichever Atlassian account owns the token, so there’s no OAuth app, no Cloud ID, and no scopes to grant. The token has full access to whatever that account can already do in Jira.
1

Create an API token

Go to your Atlassian API token settings and create a new token. Copy it, along with the email address of the Atlassian account it belongs to.
2

Base64 encode your credential

Combine your email and token as {your email}:{your API token}, then Base64 encode the whole string. On macOS or Linux, you can run:
3

Add it to Airia

Add Jira Cloud (API Token) as a server on a Gateway or Deployment, then enter the encoded string as the credential, along with your Atlassian domain, the part before .atlassian.net in your site’s URL.
The credential Airia needs is the Base64 encoding of email:apitoken, not the API token by itself. This method authenticates every request with a single token rather than individual user sign-in, so it’s best suited to simpler or single-account setups.

Confluence Cloud

Connect Confluence pages, spaces, and content the same way

Tenant vs. Personal Level App Credentials

Decide whether your OAuth app registration is shared or personal

Supported Credential Types

See how each authentication method works across servers

Server Management

Approve which MCP servers your organization can use