> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clarityq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Atlassian (Jira)

> Connect Jira and other Atlassian products to ClarityQ through the Atlassian Rovo MCP Server, including the Atlassian admin step required before anyone can authorize.

Connecting Atlassian lets ClarityQ's agent search, read, and work with Jira issues (and other Atlassian products your account can access, such as Confluence) while answering your questions. The connection runs through the **Atlassian Rovo MCP Server** (Atlassian also calls it the Atlassian MCP server), added to ClarityQ as an OAuth [MCP connector](/integrations/mcp/connecting-mcp-servers). Each teammate signs in with their own Atlassian account, so ClarityQ only sees what that person can see in Jira.

Three parts, in this order:

1. An **Atlassian organization admin** allows the ClarityQ domain in Atlassian. Required. Without it, authorization fails for everyone.
2. A **ClarityQ admin** adds the Atlassian MCP connector once for the organization.
3. **Each teammate** connects their own Atlassian account.

## Before connecting Atlassian: allow ClarityQ in Atlassian

<Warning>
  Atlassian only lets an AI tool complete OAuth if the tool's domain is on the organization's allowed list. An **Atlassian organization admin** must add this exact entry before anyone tries to connect:

  ```
  https://app.clarityq.ai/**
  ```

  If you aren't an Atlassian organization admin, send this section to the person who manages your company's Atlassian account.
</Warning>

The `/**` at the end is Atlassian's path wildcard. It allows any path under `app.clarityq.ai`, which covers the ClarityQ callback URLs Atlassian redirects to after you approve access. Enter the value exactly as shown, including `https://` and the trailing `/**`.

### Steps for the Atlassian organization admin

<Steps>
  <Step title="Open Atlassian Administration">
    Go to [admin.atlassian.com](https://admin.atlassian.com/) and sign in. If you manage more than one organization, select the one that owns the Jira site you want to connect.
  </Step>

  <Step title="Go to Rovo → Rovo MCP server">
    In the left menu, select **Rovo**, then **Rovo MCP server**. The domain list is under **Domain settings**.
  </Step>

  <Step title="Click Add domain">
    Below the **Allow Atlassian supported domains** setting, in your organization's own domain list, click **Add domain**.
  </Step>

  <Step title="Enter the ClarityQ domain and save">
    Add exactly:

    ```
    https://app.clarityq.ai/**
    ```

    Save. The entry appears in the list alongside any other domains your organization has allowed.
  </Step>

  <Step title="Return to ClarityQ">
    Start the Atlassian connection again from the beginning (see below).
  </Step>
</Steps>

That's the only Atlassian change needed. ClarityQ uses Atlassian's default OAuth 2.1, so leave **API token** authentication and enterprise-managed authentication as they are.

## Add the Atlassian MCP connector in ClarityQ

A ClarityQ admin does this once. Open **Organization Settings → MCP** and click **Add Connector**.

<Steps>
  <Step title="Name the connector">
    For example, `Jira` or `Atlassian`.
  </Step>

  <Step title="Paste the Atlassian Rovo MCP server URL">
    In **Remote MCP server URL**, enter:

    ```
    https://mcp.atlassian.com/v2/mcp
    ```
  </Step>

  <Step title="Leave Headers empty">
    No headers makes the connector **OAuth**, so each teammate signs in with their own Atlassian account rather than sharing one token.
  </Step>

  <Step title="Click Add">
    ClarityQ validates the connection and the connector appears in the list. Teammates now see it as an **App**.
  </Step>
</Steps>

## Connect your Atlassian account

Each teammate connects individually.

<Steps>
  <Step title="Open Settings → Apps">
    Find the Jira / Atlassian app in the list. See [Using Apps](/integrations/mcp/using-mcp-servers) for the full Apps page.
  </Step>

  <Step title="Click Connect">
    A new window opens on Atlassian's authorization screen. Sign in if prompted, review the access ClarityQ requests, and approve it. Atlassian redirects back to ClarityQ and the app shows **Connected**.
  </Step>

  <Step title="Turn the app on in a chat">
    In a chat, click **+ → Apps** and switch on Jira. ClarityQ can now use Jira tools in that conversation.
  </Step>
</Steps>

## Troubleshooting

### "Access to this domain is restricted"

If the Atlassian authorization screen shows **"Access to this domain is restricted"** or **"Your organization admin must authorize access from this redirect URL"** and mentions a ClarityQ URL, the ClarityQ domain has not been allowed in the organization's Rovo MCP server settings.

Ask your Atlassian organization admin to confirm this exact entry exists under **Rovo → Rovo MCP server → Domain settings**:

```
https://app.clarityq.ai/**
```

Common mistakes: missing `https://`, missing `/**`, a typo in the domain, or the domain added to a different Atlassian organization than the one that owns the Jira site.

### The domain was just added and authorization still fails

Atlassian can take a moment to apply a new domain, and your browser may be holding on to the earlier failed attempt.

1. Close the existing Atlassian authorization window.
2. In ClarityQ, start again from **Settings → Apps → Connect**.
3. Still failing? Retry in a private / incognito browser window.
4. Still failing? Have the Atlassian admin delete the domain entry, add the identical entry again, save, and retry. Atlassian recommends this when the entry looks correct in the admin UI but is still being blocked.

### The Jira app doesn't appear on the Apps page

A ClarityQ admin hasn't added the Atlassian MCP connector yet, or it's disabled. See [Add the Atlassian MCP connector](#add-the-atlassian-mcp-connector-in-clarityq) and check the connector's enable/disable toggle under **Organization Settings → MCP**.

### Connected, but Jira tools fail in chat

ClarityQ acts with your own Jira permissions. If you can't see a project or issue in Jira, ClarityQ can't either.

If Atlassian shows *"You don't have permission to connect from this IP address"*, your organization's Atlassian IP allowlist is blocking the connection. The Atlassian admin needs to adjust the IP allowlist, not the domain list.