Skip to main content

Connect Jira with OAuth: Admin Setup for Atlassian Rovo MCP

Written by Ines

An Atlassian organization admin may need to complete a one-time setup before anyone in the organization can connect Jira to Thunders with OAuth.

Connect Jira with OAuth

Use this guide when the Jira connection displays an Atlassian message that an organization admin must authorize access from the Thunders redirect URL.

Who needs to complete this?

An Atlassian organization admin with access to the organization’s Rovo MCP server settings must allow Thunders. This setup is completed once per Atlassian organization.

After the domain is allowed, users can connect Jira to Thunders using their usual Jira permissions.

Before you begin

You need:

Allow Thunders in Atlassian

  1. Go to Atlassian administration.

  2. Select the relevant workspace.

  3. In the sidebar, open Rovo → Rovo MCP server.

  4. Open the Domains tab.

  5. Under Your domains, select Add domain.

  6. Add the following allowed domain: https://api.thunders.ai/**

  7. Save the change.

Return to Thunders

  1. Return to Settings → Connectors in Thunders.

  2. Select Atlassian Cloud (including Jira, Confluence).

  3. Select Connect → Connect with OAuth.

  4. Complete the Atlassian authorization flow.

Troubleshooting

The same authorization error appears again

  • Confirm that the domain was added to the correct Atlassian organization.

  • Confirm that the domain value is exactly https://api.thunders.ai/**.

  • Wait briefly after saving the domain, then retry the connection from Thunders.

I am not an Atlassian organization admin

Send this to your Atlassian admin:

To enable Jira OAuth in Thunders, please go to Atlassian administration → select our workspace → Rovo → Rovo MCP server → Domains, then add https://api.thunders.ai/**. Once this is complete, I can retry connecting Jira from Thunders.

This requirement applies to the organization configuration. It does not mean every Jira user needs administrator privileges to connect after the setup is complete.

Proposed Thunders connection flow

Click through the mockup to review the OAuth entry point, admin documentation handoff, known-error recovery, and successful Jira site selection.

Did this answer your question?