What it is
The Atlassian Rovo MCP Server is a hosted, generally available server on Atlassian Cloud. The recommended endpoint is https://mcp.atlassian.com/v2/mcp; v1 endpoints still work and now expose v2 tools, and the legacy SSE endpoint stopped being supported after 30 June 2026. Users sign in with OAuth 2.1. An org admin can also allow personal API tokens or service account keys for headless use.
It covers Jira, Confluence, Bitbucket Cloud, Jira Service Management, Compass and Loom, plus Atlassian's Teamwork Graph, Goals, Projects, Teams, Focus and Talent. Tools are grouped into permission groups by product and intent, and Jira delete and manage groups are off by default. To save context, the server shows the most-used tools first and lets clients discover the rest; ?tools=all returns a flat list for MCP gateways.
The server itself carries no fee, but MCP calls that pull enriched or cross-product context consume Rovo credits from the organisation's pooled allowance, and billing for usage beyond the allowance starts on 3 December 2026.
Install
https://mcp.atlassian.com/v2/mcpOur review
Governance is the reason to prefer Atlassian's server over a community Jira wrapper. Admins grant access by permission group per product, decide whether API tokens are allowed at all, restrict which AI tool domains may connect, and see each tool call in the audit log. Existing IP allowlists apply to MCP calls too, though Atlassian warns that some AI clients call from their own servers' addresses, so a corporate VPN alone may not satisfy the allowlist.
The cost model changed this autumn and most coverage has not caught up. Looking up a single Jira work item or Confluence page, and write operations, are free. Enriched calls, including searchAtlassian, search and getTeamworkGraphContext, cost 1 to 10 Rovo credits each, from a pool of 25 credits per user per month on Jira or Confluence Standard, 70 on Premium and 150 on Enterprise. From 3 December 2026, usage beyond the pool is billed at $0.01 a credit, and extra usage is on by default unless an admin turns it off or sets a cap.
Coverage is wide but uneven by auth method. Jira Service Management tools work only with API tokens, Compass only with OAuth, Bitbucket only for workspaces linked to an organisation, and Loom only for workspaces linked to a site. Atlassian publishes no MCP-specific rate limit, and one open issue reports 429 errors after about 20 parallel Confluence reads, so bulk automations are better built on the REST API.
The README is candid that prompt injection and tool poisoning can lead an agent to exfiltrate data or make unwanted changes. That risk is larger here than in most servers, because Jira tickets and Confluence pages are routinely written by customers, contractors and integrations, and the agent reads them with the user's full permissions.
Where it earns its place
A developer at a 150-person company on Jira and Bitbucket Cloud
Read the ticket, write the fix and move the issue to In Review from Claude Code or Cursor
Looking up one work item and updating its status are free in Rovo credits. Pinning the cloudId, project key and a 10-result search limit in AGENTS.md cuts the discovery calls Atlassian's README warns about.
A support operations lead running Jira Service Management
Have an agent summarise new requests and draft first replies
JSM tools need an admin to enable API token auth and a scoped token or service account key. Enriched cross-product searches cost credits, so 50 a day at up to 10 credits each is up to 15,000 credits a month, about $88 beyond the 6,250 credits a 25-agent Service Collection Standard pool includes.
An Atlassian org admin preparing for December's billing change
Keep MCP usage from producing a surprise Rovo bill
Track Rovo credits under Insights, Platform usage, set a spending cap on extra usage or switch it off, and watch the 80% and 100% alerts. 100 Jira Premium plus 100 Confluence Premium users pool 14,000 credits a month.
Before you commit
- Setup
- claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp, or the Cursor, VS Code, ChatGPT, Claude Desktop and Codex plugins, then OAuth in the browser. Headless setups need an admin to enable API tokens first.
- Integrations
- Read, write, search, delete and manage permission groups across Jira, Confluence, Bitbucket Cloud, JSM, Compass, Loom, Goals, Projects, Teams, Focus, Talent and Teamwork Graph; Teamwork Graph can also return linked GitHub, GitLab and Jenkins data.
- Data and privacy
- Hosted by Atlassian over TLS 1.2 or later; calls act with the user's Atlassian permissions and are recorded in the audit log. Content in tickets and pages is a prompt-injection route, which the README flags. No GitHub security advisories are published.
- Cost at scale
- Rovo allowances pool across the organisation: 25, 70 or 150 credits per user a month on Jira or Confluence Standard, Premium or Enterprise, and 250 to 1,500 on the Teamwork and Service Collections. Enriched MCP calls cost 1 to 10 credits; overage is $10 per 1,000 from 3 December 2026.
- Limits
- Atlassian Cloud only; Rovo requires an organisation on a verified business domain. MCP rate limits are not published, and clients moved from v1 may need cached client IDs or credentials cleared.
What's good
- One endpoint for Jira, Confluence, Bitbucket, JSM, Compass and Loom
- Permission groups, domain controls, IP allowlists and audit logs
- Jira delete and manage tools off by default
- Single-product lookups and writes use no Rovo credits
What's not
- Enriched search calls use 1-10 Rovo credits each, billed beyond allowance from December
- Cloud only; Data Center and Server sites are not supported
- JSM needs API tokens and Compass needs OAuth
- No published MCP rate limits; an open issue reports early 429s
Best for
Companies that run on Jira and Confluence Cloud and want agents to read and update work items under admin control.
Alternatives
Atlassian Rovo MCP Server: common questions
- Is Atlassian Rovo MCP Server worth it?
- Atlassian has built the best-governed vendor server for work tracking, and from December the price of that convenience shows up as Rovo credits on the company bill. We rate it 4.4 out of 5.
- How much does Atlassian Rovo MCP Server cost?
- Included with paid Atlassian Cloud plans. Single-product lookups and writes are free; enriched search uses 1-10 Rovo credits a call, $10 per 1,000 over allowance.
- What are the downsides of Atlassian Rovo MCP Server?
- Enriched search calls use 1-10 Rovo credits each, billed beyond allowance from December; cloud only; Data Center and Server sites are not supported; jSM needs API tokens and Compass needs OAuth; no published MCP rate limits; an open issue reports early 429s.
- Who is Atlassian Rovo MCP Server best for?
- Companies that run on Jira and Confluence Cloud and want agents to read and update work items under admin control.
- How much does Atlassian Rovo MCP Server cost for a team or in production?
- Rovo allowances pool across the organisation: 25, 70 or 150 credits per user a month on Jira or Confluence Standard, Premium or Enterprise, and 250 to 1,500 on the Teamwork and Service Collections. Enriched MCP calls cost 1 to 10 credits; overage is $10 per 1,000 from 3 December 2026.
- Is Atlassian Rovo MCP Server safe for company data?
- Hosted by Atlassian over TLS 1.2 or later; calls act with the user's Atlassian permissions and are recorded in the audit log. Content in tickets and pages is a prompt-injection route, which the README flags. No GitHub security advisories are published.
- What are the best Atlassian Rovo MCP Server alternatives?
- The closest alternatives we have reviewed are Linear MCP, Notion MCP and Asana MCP.
Answers checked Oct 23, 2026.
Make Atlassian Rovo MCP Server? Show this rating on your site
