## Atlassian integration

Atlassian publishes a single **official MCP server** ("Rovo MCP") covering Jira, Confluence, Bitbucket, Loom, and the wider Atlassian platform. Agen.co connects to it directly as an **Official** connector, giving your agents access to issues, pages, repositories, and cross-product data across your connected Atlassian Cloud site, scoped to the connecting user's own permissions.

Prerequisites
- An Atlassian Cloud site with Jira, Confluence, and/or Bitbucket. Jira Service Management and Compass aren't reachable through this connector — Jira Service Management tools only work with API token authentication, which this connector doesn't use, and Compass isn't part of the access this connector requests.
- To reach Bitbucket, the Bitbucket workspace must be linked to an organization — an unlinked workspace can't be selected when authorizing.
- To reach Loom, the Loom workspace must be linked to the Atlassian site.
- Deleting or administratively managing Jira issues needs an Atlassian admin to enable the `delete_jira` and `manage_jira` permission groups first — they're disabled by default.


### Connect Atlassian in Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. In the **Select connector** drawer, search for `Atlassian` and select it. The **Add Atlassian** panel opens.
3. Fill in the field:
| Field | Required | Description |
|  --- | --- | --- |
| **Instance Slug** | Yes | Prefixes each imported tool as `slug__tool`, so several instances of the connector can coexist. Prefilled with `atlassian`. Use lowercase kebab-case. You can change it later from the connector's settings. |
4. Click **Connect**. Atlassian opens in a new tab, and the panel shows **Waiting for authorization — complete it in the opened tab…**
5. Sign in to Atlassian if prompted, then approve the requested access.
6. Back in Agen.co, the panel switches to **Select the tools to import from Atlassian.** Every tool is toggled on; turn off any you don't want to import, then click **Add**.


The connector is created and its tools imported only when you click **Add**. If you close the panel before that, nothing is saved, even though the Atlassian tab reported success.

"Your organization admin must authorize access from this redirect URL to this site"
If you get "Your organization admin must authorize access from this redirect URL to this site" while approving access, your Atlassian Cloud site is blocking Agen.co's redirect URL by default. You need to add it to the allowed list in Atlassian's admin console before the connection can complete:

1. Sign in to admin.atlassian.com with an organization admin account and open the relevant site.
2. In the left sidebar, go to **Rovo** → **Rovo MCP server** → **Domain settings**.
3. Add Agen.co's redirect URL to the allowed list — this is the same **Callback URL** shown on the **Add Atlassian** panel in Agen.co.
4. Save your changes, then retry the **Connect** flow in Agen.co.


### Authorize each user

Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls an Atlassian tool, the call returns an authorization link instead of a result. The user opens the link, signs in to Atlassian, and approves the same way. After that, the user's tool calls reach only the sites and products that user already has access to — the first user to complete authorization for a given site also determines which of that site's products the connection can reach.

Once connected, Atlassian appears under **My connectors** with tools spanning:

| Area | What it covers |
|  --- | --- |
| **Jira** | Searching, reading, creating, and updating issues; deleting or administratively managing issues once an admin enables those permission groups |
| **Confluence** | Searching, reading, and creating pages |
| **Bitbucket Cloud** | Reading and writing repository data, for workspaces linked to an organization |
| **Loom** | Reading and writing Loom video data, for workspaces linked to the Atlassian site |
| **Cross-product and platform search** | Searching and reading data across the connected Atlassian site, including third-party data Jira has linked, such as pull requests, builds, and deployments |
| **Goals, Projects, Teams, Focus, and Talent** | Reading and writing data from these Atlassian platform products, where the connected site uses them |


The Atlassian MCP server progressively discovers tools rather than sending its full catalog up front, so the **Select the tools to import** screen may show a smaller list than the areas above cover; more tools can become available after the initial connection.

Enabling the Atlassian connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose.

### Additional resources

- [Getting started with the Atlassian Remote MCP Server](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/)
- [Configuring OAuth 2.1](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-oauth-2-1/)
- [Fix OAuth consent block for Atlassian Rovo MCP server in Atlassian Cloud](https://support.atlassian.com/rovo/kb/fix-oauth-consent-block-for-atlassian-rovo-mcp-server-in-atlassian-cloud/)
- [Atlassian Remote MCP Server on GitHub](https://github.com/atlassian/atlassian-mcp-server)
- [Supported tools reference](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/)