triage-issue

The Atlassian Rovo MCP Server supports several clients, including:

• [OpenAI ChatGPT](https://platform.openai.com/docs/guides/tools-connectors-mcp)
• [Claude](https://code.claude.com/docs/en/mcp)
• [Google Gemini](https://github.com/google-gemini/gemini-cli/blob/main/docs/tools/mcp-server.md)
• [Amazon Quick Suite](https://docs.aws.amazon.com/quicksuite/latest/userguide/mcp-integration.html)

The Atlassian Rovo MCP Server also supports any local MCP-compatible client that can run on localhost and connect to the server via the mcp-remote proxy. This enables custom or third-party integrations that follow the MCP specification.

For detailed setup instructions, refer to your client's own MCP documentation or built-in assistant.

---

Ensure your environment meets the necessary requirements to successfully set up the Atlassian Rovo MCP Server. This section outlines the technical prerequisites and key access considerations.

Prerequisites

Before connecting to the Atlassian Rovo MCP Server, review the setup requirements for your environment:

#### For supported clients

• An Atlassian Cloud site with Jira, Compass, and/or Confluence
• Access to the client of choice
• A modern browser to complete the OAuth 2.1 authorization flow

#### For IDEs or local clients (Desktop setup)

• An Atlassian Cloud site with Jira, Compass, and/or Confluence
• A supported IDE (for example, Claude desktop, VS Code, or Cursor) or a custom MCP-compatible client
• Node.js v18+ installed to run the local MCP proxy (mcp-remote)
• A modern browser for completing the OAuth login

---

Security is a core focus of the Atlassian Rovo MCP Server:

• All traffic is encrypted via HTTPS using TLS 1.2 or later.
• OAuth 2.1 ensures secure authentication and access control.
• Data access respects Jira, Compass, and Confluence user permissions.
• If your organization uses IP allowlisting for Atlassian Cloud products, tool calls made through the Atlassian Rovo MCP Server also honor those IP rules.

For a deeper overview of the security model and admin controls, see:

• [Understand Atlassian Rovo MCP Server](https://support.atlassian.com/security-and-access-policies/docs/understand-atlassian-rovo-mcp-server/)
• [Control Atlassian Rovo MCP Server settings](https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-rovo-mcp-server-settings/)

---

Architecture and communication

1. A supported client connects to the server endpoint:

```

https://mcp.atlassian.com/v1/mcp

```

1. A secure browser-based OAuth 2.1 flow is triggered.
2. Once authorized, the client streams contextual data and receives real-time responses from Jira, Compass, or Confluence.

> [!NOTE]

> While /sse as a server endpoint are supported, we recommend updating any custom clients configured to use /sse so they now point to /mcp.

Permission management

Access is granted only to data that the user already has permission to view in Atlassian