Atlassian MCP Server
The Atlassian Rovo MCP Server is a cloud-based bridge between your Atlassian Cloud site and compatible external tools. Once configured, it enables those tools to interact with Jira, Compass, and Confluence data in real-time. This functionality is powered by secure authentication using OAuth 2.1 or API tokens, which ensures all actions respect the user's existing access controls.
With the Atlassian Rovo MCP Server, you can:
- Summarize and search Jira, Compass, and Confluence content without switching tools.
- Create and update issues or pages based on natural language commands.
- Automate repetitive work, like generating tickets from meeting notes or specs.
It's designed developers, content creators, and project teams who use IDEs or AI platforms and want to work with Atlassian data without constantly context switching.
Supported clients
The Atlassian Rovo MCP Server supports several clients, including:
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.
Before you start
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, or API token credentials for headless authentication
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 OAuth login, or API token credentials for headless authentication
Data and security
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 and API token authentication provide secure 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:
How it works
Architecture and communication
- A supported client connects to the server endpoint:
https://mcp.atlassian.com/v1/mcp
- Depending on your setup, a secure browser-based OAuth 2.1 flow is triggered, or API token authentication is used.
- Once authorized, the client streams contextual data and receives real-time responses from Jira, Compass, or Confluence.
[!NOTE] While
/sseas a server endpoint are supported, we recommend updating any custom clients configured to use/sseso they now point to/mcp.
Permission management
Access is granted only to data that the user already has permission to view in Atlassian Cloud. All actions respect existing project or space-level roles. OAuth and API token authentication both honor configured scopes and Atlassian permissions.
API token authentication (headless)
API token authentication is available for headless or long-running client setups.