Which Atlassian products does it support?

Jira, Confluence, Jira Service Management, Bitbucket, and Compass. Tool availability depends on your authentication method and the scopes your admin has granted.

How does authentication work?

It uses OAuth 2.1 or an API token. OAuth 2.1 is recommended for most users; API token auth supports headless or automated setups and is required for Jira Service Management and Bitbucket, while Compass is available via OAuth only.

Do I need to install anything?

For supported remote clients, no. You add the server endpoint and complete a browser sign-in. Local or IDE setups run a lightweight proxy (mcp-remote) and need Node.js v18 or later.

Atlassian Rovo MCP Server

official

Official Atlassian MCP server giving AI agents secure, real-time access to Jira, Confluence, Jira Service Management, Bitbucket, and Compass.

View on atlassian.com

What is Atlassian Rovo MCP Server?

The Atlassian Rovo MCP Server is the official, cloud-hosted Model Context Protocol server from Atlassian. It acts as a secure bridge between your Atlassian Cloud site and external AI tools, letting assistants like Claude, ChatGPT, and Cursor read, search, and update data across Jira, Confluence, Jira Service Management, Bitbucket, and Compass in real time, using plain natural language. Because it is a remote server, there is no local installation for supported clients: you connect the endpoint, authorize once, and start working.

Authentication uses OAuth 2.1 or an API token, and every action inherits the permissions the signed-in user already has in Atlassian. Nothing is exposed that the user could not already see, and admins keep control at the organization level through scoped tokens, domain allowlists, IP rules, and audit logging. It is built for developers, project teams, and content owners who live inside an IDE or AI tool and want Atlassian context without switching windows.

A note worth keeping in mind: any MCP connection lets an AI agent act with your real permissions, so Atlassian recommends least-privilege scoping, human confirmation for high-impact changes, and monitoring audit logs. Treat it as you would any tool with write access to your workspace.

Requirements: An Atlassian Cloud site with at least one of Jira, Confluence, Jira Service Management, Bitbucket, or Compass. Supported remote clients need only a browser for the OAuth sign-in; local or IDE setups need Node.js v18+ to run the mcp-remote proxy.

What can you do with Atlassian Rovo MCP Server?

Search and summarize across products — Find open bugs, surface pages, and summarize work across Jira, Confluence, and Bitbucket from one prompt.
Create and update issues and pages — Generate Jira stories and tasks or draft Confluence documentation using natural language.
Manage Compass components — Look up service dependencies or create components straight from a repository.
Bulk-create from notes or specs — Turn meeting notes or a structured file into multiple Jira issues or Compass components in one pass.
Link work across products — Connect Jira tickets to Confluence pages, or fetch the docs linked to a Compass component.

Connection URLs

Streamable HTTP (recommended)

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

Streamable HTTP (API token)

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

SSE (deprecated)

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

Frequently asked questions

What is the Atlassian Rovo MCP Server?: It is Atlassian's official cloud-hosted MCP server that connects AI tools and agents to Jira, Confluence, Jira Service Management, Bitbucket, and Compass, so they can search, summarize, create, and update Atlassian data through natural language.
Which Atlassian products does it support?: Jira, Confluence, Jira Service Management, Bitbucket, and Compass. Tool availability depends on your authentication method and the scopes your admin has granted.
How does authentication work?: It uses OAuth 2.1 or an API token. OAuth 2.1 is recommended for most users; API token auth supports headless or automated setups and is required for Jira Service Management and Bitbucket, while Compass is available via OAuth only.
Do I need to install anything?: For supported remote clients, no. You add the server endpoint and complete a browser sign-in. Local or IDE setups run a lightweight proxy (mcp-remote) and need Node.js v18 or later.

The server exposes 46+ tools organized by product and by intent (read, write, search). Hosted on Atlassian Cloud, licensed Apache 2.0, Generally Available. Official product page: https://www.atlassian.com/platform/remote-mcp-server. Last verified: 29 July 2026.