> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/atlassian.md).

# Atlassian

Connect your company's Atlassian organization to Cakewalk's MCP Gateway. Every agent tool call against Jira, Confluence and other Atlassian products passes through the gateway and is evaluated against your Policies.

Atlassian exposes its products through the Rovo MCP server. That server only accepts connections from domains your company trusts. Before employees can connect, an Atlassian admin adds Cakewalk's gateway domain to the trusted list. There are no credentials to create or paste: once the domain is trusted, each employee signs in and approves access, and Atlassian registers Cakewalk automatically.

## Requirements

* An Atlassian organization admin who can open Atlassian Administration.
* The Rovo MCP server available in your Atlassian org.

## Step 1: Open the Rovo MCP Server Settings

1. Go to [Atlassian Administration](https://admin.atlassian.com) and select your organization if you have more than one.
2. In the left sidebar, expand **Rovo**.
3. Select **Rovo MCP server**.
4. Open the **Domains** tab.

Leave **Allow Atlassian supported domains** on. It governs Atlassian's own partner tools and does not cover Cakewalk, so you still add the gateway domain in the next step.

## Step 2: Add Cakewalk's Gateway Domain

1. Under **Your domains**, select **Add domain**.
2. In the **Domain** field, enter this pattern:

```
https://mcp-gateway.getcakewalk.io/**
```

3. Select **Add**.

The domain now appears under **Your domains**. Cakewalk's gateway is allowed to connect to your Rovo MCP server.

## Step 3: Connect From Cakewalk

No credentials change hands. Once the domain is trusted, employees connect themselves:

1. The Admin enables the Atlassian Connection in Cakewalk.
2. From an agent platform connected to Cakewalk, an employee signs in to Atlassian and approves access.
3. Atlassian registers Cakewalk on first connect and issues the access token.

## Verifying It Works

The Atlassian Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to find a recent Jira issue or a Confluence page. If Atlassian returns results, the Connection is live.

## Troubleshooting

* Connection is refused or the sign in is blocked: open the **Domains** tab on the Rovo MCP server and confirm `https://mcp-gateway.getcakewalk.io/**` is listed under **Your domains**.
* Domain saved but still blocked: the pattern must end with `/**`. A bare `https://mcp-gateway.getcakewalk.io` does not match the gateway paths.
* Domain rules apply only to tools connecting through OAuth 2.1. If your Atlassian org is set to API token authentication for the Rovo MCP server, switch the connecting method to OAuth 2.1.

## Learn More

* [Control Atlassian Rovo MCP server settings](https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-rovo-mcp-server-settings/)
* [Available Atlassian Rovo MCP server domains](https://support.atlassian.com/security-and-access-policies/docs/available-atlassian-rovo-mcp-server-domains/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/atlassian.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.