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

# Atlassian

> Give the Sazabi agent tools to search and manage Jira, Confluence, Jira Service Management, Compass, and Bitbucket from your workflow.

[All Jira integration capabilities](https://docs.sazabi.com/catalogs/integrations/jira.md)

## About

Atlassian is an MCP connector that gives the Sazabi agent tools to search and manage Jira, Confluence, Jira Service Management, Compass, and Bitbucket. Atlassian hosts a remote MCP server (Atlassian Rovo) at `https://mcp.atlassian.com/v1/mcp` over Streamable HTTP. Sazabi authenticates via OAuth 2.1 using Atlassian's dynamic client registration — you approve access once in the browser and Sazabi refreshes the token thereafter. Write tools are gated by the per-connection read-only toggle and your organization's tool policy.

**What the agent can do:**

* Search and read Jira issues, projects, and boards
* Search and read Confluence pages and spaces
* Work with Jira Service Management requests and Compass components
* Access Bitbucket repositories and pull requests

## Prerequisites

* An Atlassian Cloud site with Rovo/MCP access enabled
* Permission to authorize third-party OAuth applications for your Atlassian organization

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Atlassian in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Authorize

Start the connection; Sazabi redirects you to Atlassian to authorize. During authorization, pick the Atlassian site you want to connect, then Sazabi redirects you back.

## Set up with the CLI

You can also connect Atlassian with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)).

Atlassian authenticates over OAuth, so the CLI opens a browser to complete authorization:

```bash theme={"system"}
sazabi mcp-connectors connect atlassian
```

Add `--read-only` to restrict the connector to read-only tools, or `--project-id <project>` to target a specific project. In `--json` mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with `sazabi mcp-connectors list`.

## Verify

Open the connector's connection page under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized and that your Atlassian Cloud site has Rovo/MCP access enabled.

## Troubleshooting

**No tools discovered** — Disconnect and reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) to restart the OAuth flow; confirm your Atlassian site has Rovo/MCP enabled.

**Connection shows needs attention** — The authorization may have expired or been revoked; reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


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