What Is Atlassian Rovo MCP? Connecting Jira and Confluence to Your AI Assistant: Setup, Credits and Admin Settings
You ask your assistant (such as Claude, ChatGPT, Codex or Cursor) about a Jira work item, a Confluence page or a Bitbucket repository; Atlassian Rovo MCP Server works with the Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom and Teamwork Graph data on your Atlassian Cloud site, and can also create or update records. It's the official remote MCP server hosted by Atlassian; the recommended address is `https://mcp.atlassian.com/v2/mcp`, sign-in is through OAuth 2.1, and if an admin enables it you can also connect with an API token. Access is limited to your Atlassian permissions; the delete (delete_jira) and management groups are off by default and an admin has to turn them on. Simple read and write calls don't use Rovo credits; enriched calls mostly use 1-10 credits. The official pages don't clearly state whether MCP can be used on the free Atlassian plan.
- What it does
- Lets your assistant work with Jira, Confluence and other Atlassian data
- Type
- Connector (remote MCP server hosted by Atlassian)
- Where
- Claude, ChatGPT, Codex, Cursor, VS Code, Windsurf and more
- Sign-in
- OAuth 2.1; API token if an admin enables it
- Deleting
- delete_jira is off by default; an admin turns it on
- Turkish
- Not stated in the official documentation
- Cost
- No separate fee for the server; Rovo credits are included in paid subscriptions
What Is Atlassian Rovo MCP Used For?
MCP is the standard that lets AI programs connect to outside tools. This server connects your assistant to Atlassian products: searching Jira work items with JQL, summarizing boards and sprints, creating work items and posting comments, reading and editing Confluence pages, reviewing Bitbucket pull requests, Compass services and Loom video transcripts, and seeing third-party data linked to Jira (such as GitHub PRs and builds) through Teamwork Graph.
Limited to your Atlassian permissions; the delete and management groups are off by default, and an admin turns them on.
The number of tools varies by source: Claude's connector directory shows 21 "core" tool names, while Atlassian's support page lists about 245 tool names in v2, and most tools are reached through the discover, read, write and destructive groups. That's why no single number is given.
Who it's for: teams and managers who use Jira and Confluence. The assistant's write tools make real changes on your site; see the "What does it access?" section below.
How Do You Connect Atlassian Rovo MCP?
What you need: an Atlassian Cloud site with Jira, Confluence, Jira Service Management, Bitbucket or Compass, and a browser for OAuth approval. The recommended server address is v2: https://mcp.atlassian.com/v2/mcp. The old v1 addresses are still supported; the old SSE address (/v1/sse) is no longer supported after June 30, 2026. The commands are taken verbatim from Atlassian's README and support pages.
- Claude Desktop (README): Settings then Extensions then Browse extensions › Plugins, then search for Atlassian and install it.
- claude.ai: the "Add to Claude" link in the README goes to the Atlassian page in Claude's connector directory, which has a Connect button.
- On the Atlassian OAuth 2.1 consent screen that opens, pick your site and products and approve the permissions.
The "Customize then Connectors" menu path mentioned in some sources doesn't appear in Atlassian's documentation.
› claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcpThen sign in with the /mcp command in a Claude Code session. The repo also offers a Claude Code plugin with six ready-made skills (turning meeting notes into tasks, status reports, sprint boards and others); the README doesn't give its command line.
› codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcpIn Codex Desktop, Plugins or Connectors › Atlassian Rovo › Install. In Cursor, the Atlassian plugin from Cursor Marketplace › Add to Cursor. In VS Code, search for "@mcp Atlassian" in the Extensions view and click Install.
› {"mcpServers": {"atlassian": {"serverUrl": "https://mcp.atlassian.com/v2/mcp/"}}}For ChatGPT, the README gives an "Add to ChatGPT" link; the menu path isn't in Atlassian's documentation. GitHub Copilot CLI, Gemini CLI, Docker, Kiro and Amazon Quick Suite are listed in the README's client table, each with a link to its own documentation.
Connect with OAuth first; an API token is an option if your admin allows it. Your admin may have turned off some tools, domains or IP addresses.
How Do You Use Atlassian Rovo MCP?
Once connected, you write your request as usual. For tasks that require writing, ask the assistant to show you a draft first; the delete tools are off by default anyway.
It has been reported that asking for a small edit on a large Confluence page can break the table layout (open issues #269, #270); on important pages, try it on a copy first.
Which Clients Does Atlassian Rovo MCP Work With?
| Claude (web and desktop)Yes | Connector directory and Desktop extension; Atlassian's setup instructions are in the README. |
|---|---|
| Claude Code, Codex, Cursor, VS Code, WindsurfYes | The README and support page have setup steps. |
| ChatGPTPartly | The README gives an "Add to ChatGPT" link; the menu path isn't in Atlassian's documentation. |
| GitHub Copilot CLI, Gemini CLI, Docker, Kiro, Amazon Quick SuitePartly | Listed in the client table; there are no step-by-step setup instructions on Atlassian's pages. |
For people coming from old v1 connections, the old setup in Claude turns into a "Custom Web" connector: remove the old one and reinstall v2 from the connector list.
What Does Atlassian Rovo MCP Access, and What Can Admins Do?
Jira work items, boards, sprints, comments; Confluence pages, comments, version history, attachments; Bitbucket repositories, PRs, commits, pipeline logs; Loom videos and transcripts; Goals, Projects, Teams, Talent and Capacity planning; Teamwork Graph.
Jira: creating and editing work items, transitions, comments, worklogs, sprints and attachment uploads; Confluence: changing pages, comments, labels, permissions and public links; Bitbucket: creating, merging and approving PRs, creating branches and commits, running pipelines; Loom: changing visibility.
The delete_jira group deletes work items, comments and attachments, and this can't be undone. According to Atlassian's tools page, delete_jira is off by default and an admin has to turn it on (per the official page). Confluence has tools for archiving (reversible) and removing permissions.
Access is limited to the user's existing Atlassian permissions; OAuth and API tokens follow the configured scopes. Atlassian writes that scopes can tighten permission restrictions but can't exceed them.
| Admin control | What it does (per Atlassian's documentation) |
|---|---|
| Atlassian Administration › Connectors › Atlassian MCP server › Permissions | Turns Read, Write and Search permissions on or off per product; changes take effect immediately. |
| Domains | Turns the domains Atlassian supports on or off, and adds your own domain (OAuth only). |
| Authentication | Turns API token sign-in on or off. |
| IP allowlist | Hosted AI clients send requests from the provider's IP; a VPN may not be enough. |
| Audit log | Tool usage appears under Insights › Audit log. |
!Atlassian explicitly flags the risks of prompt injection and tool poisoning: connect only to clients you trust, grant the least privilege, require human approval for destructive actions and monitor the audit logs. Jira work item and Confluence page text may be content written by others. There are no entries in GitHub Security Advisories; that doesn't mean "safe." Read Atlassian's privacy policy yourself for the data processing terms.
Is Atlassian Rovo MCP Free? Rovo Credits
No separate fee is listed for the server; calls are tied to your Atlassian Cloud site. According to Atlassian's Rovo usage page, setting up the server, reading single-product context and write operations don't use Rovo credits; enriched calls (search, context, people activity) mostly use 1-10 credits per call, and Confluence infographic and visualization calls typically use 15-30 credits. So not every call uses credits. These pages don't clearly state that MCP can be used on the free Atlassian plan or that it comes with credits: credits are defined for "paid subscriptions."
| Subscription | Included Rovo credits (per user/month) |
|---|---|
| Jira and Confluence Standard / Premium / Enterprise | 25 / 70 / 150 |
| Service Collection and Teamwork Collection (Standard / Premium / Enterprise) | 250 / 700 / 1,500 |
Credits are in a shared pool across the organization, reset monthly and don't roll over. Billing for extra usage starts December 3, 2026; it's on by default, and an admin can set a spending cap or turn it off. Prices are listed separately by Atlassian; there's no Turkish lira price. To turn on Rovo, the organization admin needs to be on a verified business domain (a generic domain like gmail.com won't work).
Source: Atlassian support pages (Rovo usage limits). Check the current page for credit and pricing details. This is not legal or financial advice.
Common Problems and Fixes
| What's happening | What to do |
|---|---|
| "You don't have permission to connect from this IP address" | The IP allowlist is on; an admin needs to add the AI provider's egress IP range to the allowlist. |
| "Access denied: Your organization admin has not authorized the write permission" | An admin needs to set the relevant permission to Allowed in the Permissions tab; changes take effect immediately. |
| Sign-in succeeds but tool calls return 403 | It may be an IP restriction, insufficient scope or app permission; confirm the reason for the denial. |
| The connector doesn't work, empty boxes on screen | Interactive windows use iFrames; if strict egress filtering is in place, *.atlassian.net needs to be added to the allowlist. |
| OAuth loop or redirect error | Make sure your browser isn't blocking pop-ups and redirects; if you're using a local proxy, allow http://localhost:3334. |
| Reported by users JQL search cuts off at 5 results; the v2 refresh token becomes invalid when idle | Open issues (#221, #225, #260); no official fix. |
How Do You Disconnect Atlassian Rovo MCP?
- In the client: In Claude Code,
claude mcp remove atlassian(a general command; Atlassian's documentation doesn't mention it); in Claude Desktop, remove the extension under Settings then Extensions. - On the Atlassian side (user): You can revoke your own app authorizations from your profile settings (README).
- On the Atlassian side (admin): Revoke the MCP app's access from the Marketplace and third-party apps management page, or turn off permissions in the Permissions tab.
Frequently asked questions
What is the connection address, v1 or v2?
The recommended one is v2: https://mcp.atlassian.com/v2/mcp. v1 addresses are still supported and have started serving v2 tools. The old SSE address is no longer supported after June 30, 2026.
What happens on March 1, 2027?
Atlassian's support page says that on March 1, 2027, existing v1 usage will automatically start serving v2 tools; it doesn't say "v1 is shutting down." The README says this has already started. Incompatible clients may need to clear their cached credentials.
Can Claude do more than my Jira permissions allow?
No. Access is limited to the user's existing Atlassian permissions; OAuth and API tokens follow the configured scopes and permissions.
What can my admin turn off?
From the Permissions tab, an admin can turn off Read, Write and Search permissions per product; they manage the domain allowlist, turn off API token sign-in and apply an IP allowlist; every tool use is recorded in the audit log.
Are the delete tools turned on?
No. The delete_jira and manage_jira groups are off by default; they can't be used unless an admin turns them on.
Does it work on the free Atlassian plan?
The official pages don't give a clear statement for the Free plan. What's required is an Atlassian Cloud site; Rovo credits are included in paid subscriptions. Ask your admin or check Atlassian Administration.
Related guides
Sources
- Atlassian: getting started with the remote MCP server
- Atlassian: supported tools
- Atlassian: Rovo usage limits
- atlassian-mcp-server README
Not clear in the official sources: MCP use and credit allowance on the Atlassian Free plan · rate limits (not on the pages reviewed) · the exact path of the screen for turning on delete_jira and manage_jira · the connector menu path on the Claude side · the ChatGPT menu path · Atlassian's model training and privacy policy · the current wording of the credit rules and the March 1, 2027 change · Turkish language support. Each one is covered in its section.