nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Announcing GA of the Atlassian Rovo MCP server 🎉

Jemma Swaak

We’re excited to share that the Atlassian Rovo MCP server is now generally available.

If your teams already work in AI assistants like Claude or ChatGPT, the Atlassian Rovo MCP server gives you a secure, admin-controlled way to let those AI clients take action in Atlassian products including Jira, Confluence and Compass (with Jira Service Management and Bitbucket Cloud on the roadmap).

Instead of copy/pasting between an AI chat and Atlassian, you can turn conversations directly into specs, plans and updates - while Atlassian remains the system of record.

What is the Atlassian Rovo MCP server?

The Atlassian Rovo MCP server is our Remote Model Context Protocol (MCP) server that exposes Jira, Confluence and Compass as structured tools to third-party AI clients.

From within an external AI client’s connector gallery, users can:

Connect Atlassian Rovo MCP server to their AI client
Consent to scopes and sign in with their Atlassian account
Use tools backed by the Atlassian Rovo MCP server, including:
- Rovo search and fetch to power deep research
- Create and update Confluence pages
- Create and link Jira epics and issues
- Work with Compass entities

All actions respect users' existing permissions, so AI clients can only see and change what the user could.

👉 Product overview & docs:
https://support.atlassian.com/atlassian-rovo-mcp-server/docs/use-atlassian-rovo-mcp-server/

What can you do with it?

Here are a few common “chat-to-work” flows we see:

Turn a chat into a Confluence spec
- Brainstorm and refine a product spec in Claude or ChatGPT
- Ask it to create a Confluence page in the right space
- The MCP server will:
  - Find the right space using Rovo search
  - Create a structured page (title, sections, etc.)
  - Share the page link back in the chat
Create Jira epics and issues from that spec
- From the same conversation, ask:
  “Create an epic and related stories for this spec and link them to the page.”
- The MCP server will:
  - Find the right Jira project
  - Create an epic and child issues
  - Link them back to the Confluence page
Understand a service using Compass

In your AI client, paste a link to a service or describe it (e.g. “our checkout service”)
Ask: “What is this service, who owns it, and how healthy is it?”
The MCP server will:
- Look up the Compass component and its owners
- Pull key health, dependency, and runtime details
- Summarize it back in the chat with links to Compass for deeper investigation

What’s new with GA?

Our GA focuses on making the Atlassian Rovo MCP server enterprise-ready:

✅ Audit logs for tool invocations
✅ Domain allowlist so admins can choose:
- Allow any supported AI domain
- Use Atlassian’s trusted list (with the ability to extend it)
- Block all domains unless explicitly allowlisted
✅ Respects existing IP allowlists
✅ CSS support and runbooks in place
✅ Security whitepaper in the Atlassian Trust Portal
✅ Apps that deliver tailored UI experiences on top of MCP tools
✅ Atlassian Skills in Claude's directory

We’d love your feedback

If you’re already experimenting with AI clients and our MCP tools:

What workflows are you trying to automate first?
Which AI clients and Atlassian products are most important to you?
What additional tools or controls would make the Atlassian Rovo MCP server more useful?

Please share your questions, feedback, or examples in the comments below so we can continue to evolve the Atlassian Rovo MCP server with you.

Comments

Yanqing Lin

excited to see it is in GA!

Josh

Thank you for the helpful post, @Jemma Swaak .

You mentioned GA will include "Audit logs for tool invocations" - can you please clarify if this includes the following?

Displaying unsuccessful attempts in addition to successful attempts
Including the source domain for each attempt (successful or unsuccessful)
1. It was basically impossible for us to troubleshoot trusted domain configurations without this information.

Will the GA release include the feature enabled or disabled by default?

The beta was launched with MCP enabled by default, which was a major pain point for us. We understand the desire to drive user adoption of new features, but that needs to be balanced against security considerations.

Our team had some conversations (MCP-871) with Jeffin and Erick about these topics back in November.

aerbe@micron.com

Thank you.

You say Bitbucket is on the roadmap. What's the timeline for this.
[BCLOUD-23748] MCP server for Bitbucket cloud - Create and track feature requests for Atlassian products.

Jason Pickens_tfrbhz

How do we use it in GitHub Coding Agent?

j_krauwer

Great that the MCP is GA. I've been using it with OpenCode, it worked great. But somehow since the weekend, I've been unable to connect, only getting errors. Both for https://mcp.atlassian.com/v1/mcp and https://mcp.atlassian.com/v1/sse.

┌ MCP OAuth Debug
│
● Server: atlassian
│
● URL: https://mcp.atlassian.com/v1/mcp
│
● Auth status: ✓ authenticated
│
● Access token: XXX
│
● Expires: 2026-02-16 XXXX
│
● Refresh token: present
│
● Client ID: XXXXX
│
◒ Testing connection◇ HTTP response: 401 Unauthorized
│
● WWW-Authenticate: Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token"
│
▲ Server returned 401 Unauthorized
│
● Testing OAuth flow (without completing authorization)...
│
◆ Connection successful (already authenticated)
│
└ Debug complete

I don't know if this is happening because of OpenCode (which seems to get a new update every few hours), or on the MCP side. Is there a status dashboard for the mcp somewhere, perhaps?

Jason Miller_wyy3pn

@j_krauwer There has been an open incident the past few days thats has been impacting OAuth apps with JIRA. It's clear if its related to the MCP OAuth, but I'm guessing so.

https://jira-software.status.atlassian.com

I had troubles with it all day yesterday, but as of this morning my is connecting again.

j_krauwer

I'm glad to report that mine is working again as well.

Dima_fxhtns

Claude Desktop and web cannot work with this MCP - timeouts all the time. It wasn't the case a few days ago.

Timur Davidenko_ves54o

Indeed doesn’t work right now from Claude neither Desktop neither Web version

sometimes works if i delete and recreate atlassian connector but after short time stops working again

very annoying

Jack Liu_0kh6kl

A simple search in this forum, or using this MCP for a few times would reveal that this MCP is poorly wirtten and suffers intermittent connectivity issues. EXTREMELY bad for a business SaaS software. Whoever QA'ed this clunky mess and whoever approved this for GA must be questioned!!!

Timur Davidenko_ves54o

Its unbelievable to me

mcps are out there since early last year, having ai agents accessing the main company resources in confluence and jira is Essential! In building a modern company workflow!!

Sunil Kunisetty

Hi Everyone,

Thanks so much for being a customer of Atlassian and the Rovo MCP Server — we genuinely appreciate you sharing this feedback, and I want to assure you we’re taking it very seriously.

Since GA, we’ve seen a significant increase in traffic over the past few weeks, which has unfortunately surfaced some intermittent issues. Addressing these reliability problems is a top priority for our team right now.

Thanks.

Dilip Venkatesh

Hi,

Apologies for the inconvenience.

Would you be available for a 10-minute debugging session?

Please book a slot using one of the links below:

• AU/IN timezone: https://atlassian.zoom.us/zbook/ibraheem-osama/debug-mcp
• US/EU timezone: https://atlassian.zoom.us/zbook/dilip-venkatesh/debug-mcp

If you're unable to schedule a session, please provide the following information:

• MCP Logs
• MCP Configurations
• mcp-remote version
• Node.js version (node -v)

─────────────────────────────────────────

KNOWN ISSUES & SOLUTIONS

1. Update mcp-remote
• Update to mcp-remote@latest or mcp-remote@0.1.38

2. Update your IDE/CLI
• Please ensure you're using the latest version of your IDE or CLI

3. Use the correct endpoint
• Important: Use https://mcp.atlassian.com/v1/mcp
• Do not use: https://mcp.atlassian.com/v1/sse endpoint

4. API Token Configuration
• We've released API Tokens for headless authentication
• Requirement: Organization admin must enable API Tokens
• Configuration guide: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-authentication-via-api-token/
• Org admin enablement: https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-rovo-mcp-server-settings/#Configure-authentication

5. Consistent Authentication
• Use API Tokens for consistent authentication when using multiple windows/sessions

─────────────────────────────────────────

Thanks

Nicolas Leblanc_astac1

Any update on the roadmap for this ? When can we expect a bitbucket connector for the claude.ai chatbot ?

Sunil Kunisetty

Hi @Nicolas Leblanc , we added support for BitBucket tools recently. See:

https://support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/

Note that it's not a separate connector, but part of Atlassian Rovo MCP Server itself.

Nicolas Leblanc_astac1

Is it available, say, when I use claude.ai (or even claude desktop) ?

I don't see it on either of them... (see screenshot)

screenshot 366.png screenshot 367.png

Sunil Kunisetty

Nicolas, I should have clarified that BBC Tools are only available via API Tokens for now:
https://www.atlassian.com/blog/bitbucket/the-atlassian-rovo-mcp-server-now-supports-bitbucket-cloud

Welcome!

It looks like you're new here. Sign in or register to get started.