## Atlassian integration

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

Prerequisites
- An Atlassian Cloud site with the relevant products (Jira, Confluence, Jira Service Management, Bitbucket, and/or Compass)
- The connecting user needs access to the Atlassian products the requested scopes cover — the first user to complete authorization for your site determines which products the connection can reach


### Connect Atlassian in Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. In the search bar, type `Atlassian` and select it from the results.
3. Optionally fill in **Instance Slug** — distinguishes multiple instances of this MCP connector by prefixing each imported tool as `slug__tool`. Use lowercase kebab-case; leave empty for a single instance. This value is immutable after creation.
4. Click **Connect**.


You're redirected to Atlassian to sign in and approve access. No Client ID or Client Secret needs to be entered manually.

"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.


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

| Area | What it covers |
|  --- | --- |
| **Jira** | Searching and summarizing issues, creating and updating issues, and bulk-creating issues from notes or specifications |
| **Confluence** | Searching and summarizing pages, creating new pages, browsing accessible spaces, and retrieving linked documentation |
| **Compass** | Creating service components, bulk-importing components from CSV/JSON, querying service dependencies, and linking components to Jira issues |
| **Cross-product** | Linking work across Jira, Confluence, and Compass to automate multi-step tasks |


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)