> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.basement.chat/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.basement.chat/_mcp/server.

# Jira and Confluence

Jira is the issue and project tool of [Atlassian](https://www.atlassian.com/software/jira). Confluence is the page base of the same company. The Gateway uses the MCP server of Atlassian itself. No configuration by the admin is necessary: each person connects their own Atlassian account.

## What the assistant does

| With read only                                                                                                                                   | With read and write                                                                                      |
| ------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- |
| Searches issues by text or by filter (JQL). Reads an issue: title, description, status, assignee, comments. Searches and reads Confluence pages. | All of the read part. Creates issues. Changes fields and status. Adds comments. Creates and edits pages. |

The assistant sees only the projects and pages that your Atlassian account sees.

## Connect your account

In **Connections**, on the **Jira** card, click **Connect my account**. There are two ways:

#### Sign in with Atlassian (recommended)

1. Click **Sign in with Atlassian**.
2. Sign in to Atlassian. Select the site (for example `yourcompany.atlassian.net`) and approve Basement.
3. Go back to the Gateway. The card shows **Connected**.

If Atlassian blocks the sign-in, the admin of your Atlassian site must permit Basement one time: in [admin.atlassian.com](https://admin.atlassian.com), **Rovo › Rovo MCP server › Domains › Add domain**, and add the domain that the Gateway shows on the screen.

#### API token

1. Open the [Atlassian API tokens](https://id.atlassian.com/manage-profile/security/api-tokens) page. Click **Create API token with scopes**. A simple token (without scopes) does not work.
2. Give the token a name. Select the app **Atlassian MCP V2** and select all its scopes. Create and copy the token.
3. In the Gateway, paste the token and enter the e-mail of your Atlassian account. Click **Connect**.

The admin of your Atlassian site must permit API tokens one time: **admin.atlassian.com › Rovo › Rovo MCP server › Authentication › API token**.

## Example questions

* "Which issues of project OPS are in progress in my name?"
* "Summarize issue OPS-12 and the comments."
* "Create an issue in project OPS: 'Review the X integration', high priority." (needs read and write)
* "What does the page 'Deploy procedure' in Confluence say?"

## If it does not work

| Message                              | What to do                                                                                  |
| ------------------------------------ | ------------------------------------------------------------------------------------------- |
| Atlassian refused the sign-in        | Ask the admin of the Atlassian site to permit Basement (above).                             |
| The token does not work              | Make sure that the token was created **with scopes** and with the app **Atlassian MCP V2**. |
| The assistant does not see a project | Your Atlassian account has no access to that project.                                       |
| A write answers "not permitted"      | Your access level has read only in Jira. Ask the admin for a level with write.              |