---
title: "Atlassian Rovo MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/atlassian/
description: "Searches connected Atlassian work and lets an authorized client create or update work items and pages through the current Rovo MCP endpoint."
---

# Atlassian Rovo MCP: review, setup & limitations · Undominated.ai

> Searches connected Atlassian work and lets an authorized client create or update work items and pages through the current Rovo MCP endpoint.

[← Explore all mcp servers](/mcp-servers/)

TEAM COLLABORATION / Atlassian

# Atlassian Rovo MCP

Searches connected Atlassian work and lets an authorized client create or update work items and pages through the current Rovo MCP endpoint.

 See setup guidance ↓Original source ↗

SOURCE REVIEW

 Reviewed 2026-09-21
 Evidence 2 linked sources
 Publisher Atlassian
 Licence Not established
 Read what was—and wasn’t—checked ↓

“Atlassian Rovo MCP Server”

 Atlassian · upstream description ↗ Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Connects Jira and Confluence work with related Atlassian context in a single documented service.
- The current v2 setup distinguishes user permissions and Rovo credit consumption.

### A good fit for

 - Turning a reviewed set of project notes into Jira work items or a Confluence update.

### Weigh up before choosing

 - Actions use the authenticated user’s existing access across connected products.
- Enriched Teamwork Graph/Rovo context tools consume the account’s shared Rovo credits.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/ (setup, access and capability sections)
- Official MCP Registry publisher entry: endpoint matched against official setup documentation

### Our findings

 - The current documented endpoint is /v2/mcp, with client-specific setup and an optional flat-tool-list mode.
- OAuth is the primary setup; API-token authentication is a separate documented path.

### Not established by this review

 - Authentication, service availability and tool execution were not tested.
- The hosted implementation source and licence were not established.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

Upstream setup instructions ↗
 - Add https://mcp.atlassian.com/v2/mcp using the official guide for your client.
- Complete OAuth and confirm the intended site/product access before authorizing changes.

### Before you start

 - An Atlassian account with access to the relevant connected products and an eligible MCP client.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "atlassian": {
 "url": "https://mcp.atlassian.com/v2/mcp"
 }
 }
} Copy configuration ↗

### Compatibility

A client supporting the documented remote transport and authentication flow. · Configuration example follows the documented Claude Desktop form; use client-specific instructions elsewhere.

### Transports

Streamable HTTP

### Remote service / documented account access

 - Searches connected work; enabled tools create/update work items or pages within account rights.

### Cost model

Atlassian product entitlements and shared Rovo-credit usage apply.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - Atlassian Rovo MCP official setup guide ↗ Checked 2026-09-21 https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/ Supports: summary, whySelected, bestFor, limitations, review, compatibility, install, access, transports, configExample
- Official MCP Registry: publisher endpoint transport ↗ Checked 2026-09-21 https://registry.modelcontextprotocol.io/v0.1/servers?search=atlassian&version=latest&limit=100 Supports: transports

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### AWS Knowledge MCP ↗ Retrieves official AWS documentation, regional availability and task guidance without granting access to an AWS account.](/mcp-servers/aws-knowledge/)[### Elastic Agent Builder MCP ↗ Exposes an Elastic Agent Builder tool catalog to external MCP clients through a chosen Kibana space.](/mcp-servers/elastic-agent-builder/)[### Figma Remote MCP ↗ Brings Figma design context into an assistant and supports creating or editing native Figma and FigJam content in supported clients.](/mcp-servers/figma/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)
