Atlassian Rovo MCP Server

Overview

Atlassian Rovo MCP Server is Atlassian's official cloud-hosted Model Context Protocol server for Atlassian Cloud products. It connects MCP-compatible AI clients to Jira, Confluence, Jira Service Management, Bitbucket Cloud, Compass, and Atlassian platform/Teamwork Graph capabilities while preserving the authenticated user's existing product permissions.

Installation

This is a remote hosted MCP server, not a local package to install. Atlassian's README says it is not installed through the Atlassian Marketplace or the Manage apps screen; the app is installed automatically for a site the first time a user completes the OAuth 2.1 consent flow.

For most interactive clients, configure the remote MCP URL:

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

Documented setup commands include:

claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2
codex mcp add atlassian --url https://mcp.atlassian.com/v1/mcp/authv2

Claude Desktop, VS Code, Cursor, Codex Desktop, and other MCP-compatible clients can also be configured with the same remote URL when they support remote streamable HTTP MCP servers. Legacy or custom desktop clients may use the documented local proxy command:

npx -y mcp-remote@latest https://mcp.atlassian.com/v1/mcp/authv2

Remote Endpoints

Recommended interactive OAuth endpoint:

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

Supported API-token endpoint for headless or non-interactive configurations:

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

The older SSE endpoint https://mcp.atlassian.com/v1/sse is legacy. Atlassian recommends custom clients move to /mcp or /mcp/authv2.

Authentication and Configuration

OAuth 2.1 is the primary and recommended authentication mechanism for interactive user-driven setups. MCP clients start an OAuth 2.1 flow, the user grants access, and the client sends a bearer access token.

API-token authentication is available only when enabled by an organization admin. Personal API tokens use Basic auth with a base64-encoded email and API token. Service account API keys use Bearer auth. Tool availability can be smaller with API-token auth than with OAuth.

The hosted remote endpoint has no documented runtime environment variables. The API-token endpoint uses an Authorization header supplied by the client.

Capabilities

Supported tool families include Jira read/write/search, Confluence read/write/search, Jira Service Management read/write, Bitbucket Cloud read/write, Compass read/write, Atlassian platform Teamwork Graph read/search, and shared user/resource discovery tools. Rovo search and fetch provide natural-language search and retrieval for Jira and Confluence content.

Requirements and Limitations

Users need an Atlassian Cloud site with one or more supported products, an MCP-compatible client, and either a browser for OAuth 2.1 or API-token credentials for non-interactive auth. Desktop proxy setups require Node.js 18 or later. Capabilities vary by product access, scopes, organization admin settings, client support, and authentication method. MCP clients can perform actions using the user's existing permissions, so Atlassian recommends least privilege, review of high-impact actions, and audit log monitoring. Jira Service Management and Bitbucket Cloud tools are available only through API-token authentication, while Compass tools are available only through OAuth 2.1.