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

# Connect the Atlassian Rovo MCP server

> Connect Atlassian's Rovo MCP server to Spojit for Jira, Confluence, and Jira Service Management: admin domain allowlist, OAuth sign-in, or an API token.

The **Atlassian Rovo MCP Server** is Atlassian's hosted MCP server for Jira, Confluence, Jira Service Management, Bitbucket, and Compass. Connect it to Spojit and your workflows can search and create Jira issues, read and update Confluence pages, and act on service requests.

<Note>
  Spojit connects to this server through a [custom MCP server](/connectors/remote-mcp-servers/custom) connection, so you add it with **Add custom server** rather than from the connector catalog. Atlassian maintains it and decides which tools it offers; see [Atlassian's Rovo MCP Server documentation](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/) for the current list.
</Note>

## Before you start

* An Atlassian Cloud site. The tools can only reach what your Atlassian account can already see.
* For OAuth sign-in, an **organization admin** must allow Spojit's domain. Atlassian blocks OAuth clients from domains that are not on the list.

<Steps>
  <Step title="Allow Spojit's domain (organization admin)">
    In [Atlassian Administration](https://admin.atlassian.com/), select your organization, then **Rovo > Rovo MCP server**. Select **Add domain** and add the domain you use Spojit on (for example `miraxa.spojit.com`), following Atlassian's [domain pattern guidance](https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-rovo-mcp-server-settings/).
  </Step>
</Steps>

## Server URL

```
https://mcp.atlassian.com/v2/mcp
```

## Connect in Spojit

<Steps>
  <Step title="Add a custom server">
    Go to **Connections** and click **Add custom server**. Enter a **Name** such as `Atlassian` and paste the **Server URL**.
  </Step>

  <Step title="Keep Auto authentication">
    Leave **Authentication** on **Auto**, choose a visibility, and click **Save & connect**.
  </Step>

  <Step title="Approve access in Atlassian">
    Atlassian opens its consent page. Sign in, choose the site, and approve. Spojit marks the connection **Connected** and refreshes the token automatically.
  </Step>
</Steps>

### Alternative: an API token

For unattended workflows that should not depend on one person's sign-in, Atlassian supports API tokens. An organization admin must first turn on **API token** under **Rovo > Rovo MCP server > Authentication**. Domain allowlisting does not apply to token connections.

<Steps>
  <Step title="Create a token">
    Create an API token at [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens).
  </Step>

  <Step title="Encode your email and token">
    Atlassian expects Basic authentication: your account email and the token joined by a colon, then base64 encoded.

    ```bash theme={null}
    echo -n "you@example.com:YOUR_API_TOKEN" | base64
    ```
  </Step>

  <Step title="Add the server with Token authentication">
    In **Add custom server**, choose **Token**. Paste the encoded value as the **Token**, keep **Header name** as `Authorization`, set **Prefix** to `Basic`, and click **Add**.
  </Step>
</Steps>

<Tip>
  Atlassian notes that a personal API token sent as a Bearer token falls back to read-only tools. Use the Basic format above for write access. Service account API keys use `Bearer` instead.
</Tip>

## Use it in a workflow

Add a **Connector** node, pick your Atlassian server under **Custom Servers**, and choose **Agent Mode** or **Direct Mode**. See [Use a custom server in a workflow](/connectors/remote-mcp-servers/custom#use-a-custom-server-in-a-workflow).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Atlassian blocks the consent page">
    The Spojit domain is not on your organization's allowed list. Ask an organization admin to add it under **Rovo > Rovo MCP server**, then click **Reconnect** on the connection.
  </Accordion>

  <Accordion title="Only read tools are available with a token">
    Use Basic authentication with your email and token as shown above, not a Bearer token.
  </Accordion>

  <Accordion title="Token connections are rejected">
    API token authentication is off for the organization. An organization admin can turn it on under **Rovo > Rovo MCP server > Authentication**.
  </Accordion>
</AccordionGroup>

## Learn more

* [Get started with the Atlassian Rovo MCP Server](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/)
* [Control Atlassian Rovo MCP server settings](https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-rovo-mcp-server-settings/)
* [Configure authentication via API token](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-authentication-via-api-token/)

<Snippet file="start-free.mdx" />