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

# Atlassian Integration

> Connect Jira and Confluence through Atlassian's MCP server, and what an Atlassian admin must allow first.

Connect Atlassian so the agent can work with Jira issues and Confluence pages in your tasks. Aether connects to Atlassian's own MCP server (`https://mcp.atlassian.com/v2/mcp`) with your Atlassian account, so the agent acts in Atlassian as you.

> [!NOTE]
>
> An admin of your Atlassian organization must allow Aether before anyone in it can connect. Atlassian blocks Aether until they do. See [Allow Aether in Atlassian](#allow-aether-in-atlassian).

## Allow Aether in Atlassian

Atlassian lets an organization admin decide which apps may connect to its MCP server. By default it allows only the apps on [Atlassian's own list](https://support.atlassian.com/security-and-access-policies/docs/available-atlassian-mcp-server-domains/), and Aether is not on it. Until an admin allows Aether, connecting stops on an Atlassian page that reads:

> Access to this domain is restricted. Your admin has blocked this domain "[https://app.runaether.dev/settings/integrations/mcp/callback](https://app.runaether.dev/settings/integrations/mcp/callback)" in your organization's settings.

An Atlassian organization admin allows Aether once, for the whole organization:

1. Open [Atlassian Administration](https://admin.atlassian.com) and select the organization that owns your Jira or Confluence site.
2. Go to **Connectors → Atlassian MCP server**. Some organizations have it under **Rovo → Rovo MCP server → Domain settings**.
3. Select **Add domain** and enter `https://app.runaether.dev/**`.
4. Save, then connect again from Aether.

### If Atlassian still blocks the connection

* **Add the entry again.** Delete `https://app.runaether.dev/**`, add the same entry, and save. Atlassian [describes](https://support.atlassian.com/rovo/kb/fix-oauth-consent-block-for-atlassian-rovo-mcp-server-in-atlassian-cloud/) entries that show in the list before they apply.
* **Check the organization.** An admin of several Atlassian organizations has one list per organization. The entry belongs in the organization that owns the site you are connecting.
* **Turn off "Allow Atlassian supported domains", then add the entry again.** This cleared the block for an admin whose entry was otherwise ignored, and an [open Atlassian issue](https://github.com/atlassian/atlassian-mcp-server/issues/254) describes the same block with the option on. With the option off, the apps on Atlassian's own list can no longer connect to your organization, so decide that with your team.

## Connecting Atlassian

Open **Integrations** from the sidebar, choose **Atlassian**, and click **Connect as me**. Atlassian asks you to sign in and to approve the access Aether requests, then returns you to Aether, where Atlassian shows as **Connected**.

The connection is yours. By default, each member of an Aether organization connects their own Atlassian account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.