---
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 ↓](#setup)[Original source ↗](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher Atlassian
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Atlassian Rovo MCP Server”

 [Atlassian · upstream description ↗](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/) 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.
- Atlassian’s setup page points clients at the v2 remote URL and says OAuth 2.1 keeps actions inside the user’s existing product permissions.
- The same page says MCP calls that retrieve data or generate insights consume Rovo credits from the shared organization pool.

### A good fit for

 - Turning a reviewed set of project notes into Jira work items or a Confluence update.
- Searching or updating Jira, Confluence, or Bitbucket from an AI client, using the permissions the user already has
- An organization that can account for Rovo credit use from MCP tool calls

### 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.
- The page tells operators to use least privilege and review high-impact changes; it does not describe a privilege above the user’s existing access.
- API-token authentication is described as optional, not as a replacement for the permission check.
- Other Atlassian-named registry rows were not treated as this remote server.
- No licence was stated on the support page, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- Tool availability does not remove Rovo credit consumption or product-specific permissions; review the connected product list.

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
- https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/
- https://registry.modelcontextprotocol.io/v0.1/servers?search=atlassian&version=latest&limit=100
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### 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.
- The documented server URL is https://mcp.atlassian.com/v2/mcp, and the registry entry com.atlassian/atlassian-mcp-server describes search and management across Jira, Confluence, Loom, and more.
- OAuth 2.1 is the documented authorization method, and clients act on connected products only with the user’s existing permissions.
- The page says those MCP calls consume Rovo credits, and it tells readers to review high-impact changes and monitor audit logs. It does not grant access beyond the user’s existing controls.
- The setup guide provides tools=all as a client compatibility option and distinguishes MCP calls that consume Rovo credits.

### Not established by this review

 - Authentication, service availability and tool execution were not tested.
- The hosted implementation source and licence were not established.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

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 ↗](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/)

DOCUMENTED COMMAND

 claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - 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.
- The command above is the guide’s Claude Code setup; run /mcp in a Claude Code session to authenticate. It was not run.

### 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 ↗](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/) Checked 2026-10-14 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 ↗](https://registry.modelcontextprotocol.io/v0.1/servers?search=atlassian&version=latest&limit=100) Checked 2026-10-14 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/)[### Dropbox DocSend MCP ↗ Retrieves DocSend documents, Space contents and engagement activity, and can update Space-group access settings.](/mcp-servers/dropbox-docsend/)[### 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/)

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

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
