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.

Contents

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

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.

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.

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

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 notes: managing access

If you're an admin preparing your organization to use the Atlassian Rovo MCP Server, review the points below. For more detailed admin guidance, see:

• Understand Atlassian Rovo MCP Server
• Control Atlassian Rovo MCP Server settings
• Manage Atlassian Rovo MCP Server
• Monitor Atlassian Rovo MCP Server activity

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 (just-in-time, or "lazy loading," installation).
• First-time installation requirements:
  The first user to complete the 3LO consent flow for your site must have access to the Atlassian apps requested by the MCP scopes (for example, Jira and/or Confluence). 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 Atlassian app (for example, just Jira or just Confluence) can also complete the 3LO flow to access that app through MCP.

Manage, monitor, and revoke access

• Admin controls:
  Site and organization admins can manage, review, or revoke the MCP app's access from Manage your organization's Marketplace and third-party apps. The app appears in your site's Connected apps list after the first successful 3LO consent.
• Domain controls:
  Use the Rovo MCP server settings page in Atlassian Administration to control which external AI tools and domains are allowed to connect. By default, Atlassian-supported domains are allowed; you can add trusted domains or block supported ones. Domain controls apply to OAuth 2.1 connections. For details, see Available Atlassian Rovo MCP server domains.
• IP controls:
  If your organization uses IP allowlisting for Atlassian Cloud apps, requests made through the Atlassian Rovo MCP Server must originate from an IP address allowed by your organization's IP allowlist for the relevant app. For configuration details, see Specify IP addresses for product access.
• End-user controls:
  Individual users can revoke their own app authorizations from their profile settings.
• Audit logging:
  Every time a tool is used through the Atlassian Rovo MCP Server, an event is recorded in your organization's audit log. Admins can review these in Atlassian Administration under Insights → Audit log (filter for Rovo MCP User Actions or search MCP). For more information, see Monitor Atlassian Rovo MCP server activity.

Troubleshooting common issues

• "Your site admin must authorize this app" error:
  A site admin must complete the 3LO consent flow before anyone else can use the MCP app. See "Your site admin must authorize this app" error in Atlassian Cloud apps for more details.
• "You don't have permission to connect from this IP address. Please ask your admin for access."
  This usually indicates that IP allowlisting is enabled and the user's current IP address isn't allowed to access Jira, Confluence, Jira Service Management, Bitbucket, or Compass via the Atlassian Rovo MCP Server. Ask your site or organization admin to review the IP allowlist configuration and add the relevant network or VPN IP ranges if appropriate.
• App not appearing in Connected apps:
  Ensure the user is using the correct Atlassian account and site, and confirm the app is requesting the correct Atlassian app scopes (for example, Jira scopes). If issues persist, check Manage your organization's Marketplace and third-party apps or contact Atlassian Support. Also verify the user's product permissions in Atlassian Administration.

Security

Model Context Protocol (MCP) lets AI agents connect to tools and Atlassian data using your account's permissions, which creates powerful workflows but also structural risks. Any MCP client or server you enable (for example, IDE plugins, desktop apps, hosted MCP servers, or "one-click" integrations) can cause an AI agent to perform actions on your behalf.

Large language models (LLMs) are vulnerable to prompt injection and related attacks (such as indirect prompt injection and tool poisoning). These attacks can instruct the agent to exfiltrate data or make unintended changes without explicit requests.

To reduce risk, only use trusted MCP clients and servers, carefully review which tools and data each agent can access, and apply least privilege (scoped tokens, minimal project/workspace access). For any high-impact or destructive action, require human confirmation and monitor audit logs for unusual activity. We strongly recommend reviewing Atlassian's guidance on MCP risks at MCP Clients: Understanding the potential security risks.

Support and feedback

We use your feedback to improve the Atlassian Rovo MCP Server. If you hit a bug or limitation, or have a suggestion:

• Visit the Atlassian Support Portal to report issues and feature requests.
• Share your experiences and questions on the Atlassian Community, and developer-related asks on the Atlassian Developer Community.
• Go to our Ecosystem Developer Portal if you are building an app and found a bug or issue, or have suggestions.

Disclaimer

MCP clients can perform actions in Jira, Confluence, Jira Service Management, Bitbucket, and Compass with your existing permissions. Use least privilege, review high-impact changes before confirming, and monitor audit logs for unusual activity.

Learn more: MCP Clients: Understanding the potential security risks.