Atlassian (Confluence & Jira)

# Atlassian (Confluence & Jira)

Read and write Jira issues and Confluence pages. Contains internal documentation, so its read tools are a disclosure risk even though they change nothing.

- **Publisher of the server:** Atlassian
- **Upstream:** https://www.atlassian.com/remote/mcp-server
- **Documentation:** https://www.atlassian.com/remote/mcp-server
- **Transport:** streamable HTTP (remote)
- **Endpoint:** `https://mcp.atlassian.com/v1/sse`

## Credentials and configuration

- Authorization: Bearer <OAuth access token>

These are **placeholders describing what to supply**; the registry stores no credentials. Enter real values in your own AO instance when you create the connection.

## Tools (8)

- `getJiraIssue` — Read one Jira issue with its comments.
- `createJiraIssue` — Create a Jira issue.
- `transitionJiraIssue` — Move an issue through a workflow transition.
- `searchJiraIssues` — Search issues with JQL.
- `getConfluencePage` — Read a Confluence page's content.
- `createConfluencePage` — Create a Confluence page.
- `updateConfluencePage` — Update an existing Confluence page.
- `searchConfluence` — Search Confluence content with CQL.

## Risk

Declared risk: **high**. Tools that can change state: `createJiraIssue`, `transitionJiraIssue`, `createConfluencePage`, `updateConfluencePage`. Write access must be enabled explicitly.

> This entry is a catalogue description. Installing it creates no connection and grants no agent access;
> your instance's own connection settings and approvals decide what an agent can reach.