Atlassian Rovo MCP Server

Atlassian Rovo MCP Server

The official Model Context Protocol (MCP) server for Atlassian: a cloud-hosted bridge that gives your AI tools secure, real-time access to Jira, Confluence, Jira Service Management, Bitbucket, and Compass.

Getting started · Supported tools · Security & admin · Community

The official 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, Confluence, Jira Service Management, Bitbucket, and Compass data in real time. Authentication uses OAuth 2.1 or API tokens, so every action respects the user's existing access controls.

With the Atlassian Rovo MCP Server, you can:

• Summarize and search Jira, Confluence, Jira Service Management, and Bitbucket 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 built for developers, content creators, and project teams who work in IDEs or AI tools and want to use Atlassian data without constantly switching context.

One-click setup

Pick your AI client below to install the official Atlassian Rovo MCP Server. Each button uses your client's native install link, so you don't need to edit any JSON config by hand.

    Add to Cursor
  
  Reference issues and log work in your codebase.


  
    
    Add to VS Code
  
  Search and create Jira issues via GitHub Copilot.


  
    
    Add to ChatGPT
  
  Search, summarize, and create right from ChatGPT.


  
    
    Add to Claude
  
  Bring Jira and Confluence into Claude workflows.

Contents

• One-click setup
• Supported clients
• Plugin packaging and compatibility
• Supported products and tools
• Before you start
• Data and security
• How it works
• Example workflows
• Tips and tricks
• Admin notes: managing access
• Security
• Support and feedback
• Disclaimer

Supported clients

The Atlassian Rovo MCP Server works with a growing list of MCP-compatible clients:

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.

[!TIP] For the current, canonical list of supported clients and step-by-step setup, see Getting started with the Atlassian Rovo MCP Server. You can also refer to your client's own MCP documentation or built-in assistant.

Plugin packaging and compatibility

This repository publishes the same MCP server and skills in several package formats so clients can use their native discovery and installation flows:

Both mcp.json and .mcp.json are intentional. Agent Plugins requires the root mcp.json filename and its portable transport vocabulary; existing clients continue to use .mcp.json and their native configuration vocabulary. Keep their endpoint settings aligned when changing either file.

The root package can be imported by clients that implement Agent Plugins, including Kiro Powers. Client-specific manifests remain available and are not replaced by the portable package.

Supported products and tools

Tools are organized by product and intent (read, write, or search). Organization admins grant or revoke access at the permission-group level, and each tool inherits the access of its parent group.

[!NOTE] Jira Service Management and Bitbucket Cloud tools are available only via API token authentication, while Compass tools are available only via OAuth 2.1. For the complete, current tool reference, see Supported tools.

Before you start

Check that your environment meets these requirements before you set up the server.

Prerequisites

The requirements depend on how you connect:

For supported clients

• An Atlassian Cloud site with one or more of Jira, Confluence, Jira Service Management, Bitbucket, or Compass
• 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 one or more supported products
• 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

The server enforces several security controls:

• All traffic is encrypted in transit over HTTPS (TLS 1.2 or later), per Atlassian's security practices.
• OAuth 2.1 and API token authentication provide secure access control.
• Data access respects Jira, Confluence, Jira Service Management, Bitbucket, and Compass 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
• Control Atlassian Rovo MCP Server settings

How it works

Architecture and communication

1. A supported client connects to the server endpoint. The recommended endpoint for most clients is:

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

   The https://mcp.atlassian.com/v1/mcp endpoint is also supported (for example, for API token configurations).

2. Depending on your setup, a secure browser-based OAuth 2.1 flow is triggered, or API token authentication is used.

3. Once authorized, the client streams contextual data and receives real-time responses from your connected Atlassian products.

[!NOTE] The legacy Server-Sent Events endpoint (https://mcp.atlassian.com/v1/sse) is still supported, but we recommend updating any custom clients configured to use /sse so they now point to /mcp (or /mcp/authv2).

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, service-style, or non-interactive client setups (for example, backend systems or automations). It is also required for Jira Service Management and Bitbucket Cloud tools.

• Admin enablement required: An organization admin must enable API token authentication for the Rovo MCP Server (Atlassian Administration → Rovo → Rovo MCP server → Authentication).
• Scoped token required: Create a personal API token with the scopes required for the tools and data you need to access.
• Configuration guide: Configure authentication via API token
• Admin setting reference: Control Atlassian Rovo MCP Server settings: Configure authentication

Example workflows

Once connected, you can run tasks like these from your client.

Jira workflows

• Search: "Find all open bugs in Project Alpha."
• Create/update: "Create a story titled 'Redesign onboarding'."
• Bulk create: "Make five Jira issues from these notes."

Confluence workflows

• Summarize: "Summarize the Q2 planning page."
• Create: "Create a page titled 'Team Goals Q3'."
• Navigate: "What spaces do I have access to?"

Compass workflows

• Create: "Create a service component based on the current repository."
• Bulk create: "Import components and custom fields from this CSV/JSON."
• Query: "What depends on the api-gateway service?"

Combined tasks

• Link content: "Link these three Jira tickets to the 'Release Plan' page."
• Find documentation: "Fetch the Confluence documentation page linked to this Compass component."

[!NOTE] Actual capabilities vary depending on your permission level and client platform.

Tips and tricks

Set default CloudId, Jira project, and Confluence space

Update your AGENTS.md with the Markdown below to reduce discovery tool calls, save time and tokens, and set maximum search results.

## Atlassian Rovo MCP

When connected to atlassian-rovo-mcp:
- **MUST** use Jira project key = YOURPROJ
- **MUST** use Confluence spaceId = "123456"
- **MUST** use cloudId = "https://yoursite.atlassian.net" (do NOT call getAccessibleAtlassianResources)
- **MUST** use `maxResults: 10` or `limit: 10` for ALL Jira JQL and Confluence CQL search operations.

Use skills

If you're using a desktop client like Claude, you can create or reuse skills for repeated tasks. See the default Rovo MCP skills.

For Cursor, skills are part of the marketplace plugin.

Admin