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

# Connect Jira

> Connect the Sidekick Agent to Jira through the Atlassian Rovo MCP server, using a service account instead of a personal account.

The Sidekick Agent's Jira tool connects through Atlassian's Rovo Model Context Protocol (MCP) server, authenticated with a service account instead of a personal login. Atlassian defines a service account as an account that is not associated with a person, so the connection keeps working if the person who set it up leaves your team.

## Before you start

You need:

* **Org admin** access to Atlassian Administration (`admin.atlassian.com`), to create the service account
* Workspace **Admin** or **Owner** access in Plain, to connect the server in the Sidekick Agent's settings

## Set up a service account in Atlassian

Do this in Atlassian Administration, before touching the Sidekick Agent's settings.

**1. Enable API token authentication**

Go to **Atlassian Administration → Rovo → Rovo MCP server**. In the **Authentication** section, turn **API token** on.

This is separate from creating the credential itself. Both steps are required.

**2. Create or reuse a service account with Jira access**

Go to **Directory → Service accounts**.

* **New service account**: click **Add service account**, name it something identifiable such as `Sidekick MCP`, and select **Jira** as one of its apps.
* **Existing service account**: open it, select **Grant access**, and select **Jira**.

**3. Create an API key**

On the service account's page, select **Create credentials → API token**.

Select these scopes:

| Scope | Why the Sidekick Agent needs it |
| - | - |
| `read:me` | Resolves the connected identity. Required before any other call succeeds |
| `read:account` | Resolves the connected identity. Required before any other call succeeds |
| `read:jira-work` | Reads and searches issues |
| `write:jira-work` | Creates and edits issues and comments |

Set an expiration and copy the API key. Atlassian shows it once.

## Connect the server in Sidekick Agent

With the service account and API key ready, add the server as a custom MCP server in the Sidekick Agent.

**1. Open the Add MCP server form**

Go to **Agents → Sidekick Agent → Plugins**, then in **Custom** click **Add MCP**.

**2. Fill in the server details**

* **Name**: `Atlassian`
* **Server URL**: `https://mcp.atlassian.com/v2/mcp`
* **Authentication**: API key

**3. Add the Authorization header**

Under **Auth parameters**, set:

* **Placement**: Header
* **Name**: `Authorization`
* **Value**: `Bearer` followed by a space and the API key you copied, for example `Bearer your_atlassian_service_account_api_key`

**4. Click Connect for workspace**

The Sidekick Agent opens the connection and lists the tools Atlassian's server makes available.

The server appears under **Confluence** on the plugins page, not under **Custom**, because the Confluence plugin uses the same Atlassian server address. It keeps the Jira access you granted the service account.

## Verify the connection

A successful connection only confirms the Sidekick Agent can list Atlassian's tools, not that it can read your Jira data. Confirm both in a Sidekick Agent chat: ask it to search Jira for issues in one of your real projects. Watch the tool call render in the chat. If it returns real issues, the connection works end to end.


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