Rovo MCP Server Pricing: Credits per Call
Background
On 16 June 2026 an answer was accepted on the Atlassian Community thread Atlasian Rovo Connector(Claude) - pricing and API call cost clarification. It said "there is no separate licence and no per-call charge from Atlassian for the MCP server itself".
The thread has 3,721 views today. People are still asking, now that Atlassian has started pricing some of these calls. (MCP is Model Context Protocol, the standard an AI tool uses to call another product's functions. Each function it can call is a "tool".)
Here's where it stands on 20 November 2026. Connecting an AI tool like Claude, ChatGPT or Cursor to Jira and Confluence still costs nothing, and so does looking something up or changing it in one app. A search across all your apps is different.
Rovo credits are the units Atlassian meters Rovo and Teamwork Graph usage in. On our test site on 19 November an all-app search used 6 of them each time. A search inside one app used 1, and a graph context call for one work item used 5.
From 3 December 2026 every credit above your monthly allowance costs $0.01. Before then, open Usage, then Meters, then Rovo credits in Atlassian Administration. On the Features tab, look for a row named Teamwork Graph. Then check the pay-as-you-go limit on the Usage tab.
The accepted answer in that thread was right when it was written, and it saw this coming. It said the Teamwork Graph tools were "currently in beta and free". It also said the docs promised at least 1 Rovo credit per call once they left beta.
A second thread, Does atlassian-rovo-mcp cost anything for using the mcp server, was asked and answered on that same 16 June: the server "uses Rovo Credits", and "over usage has no cost yet".
Atlassian's How Rovo credits work page has changed since. Its latest edit is from 18 November. It now says "On December 3, 2026, pay-as-you-go billing takes effect for Rovo credits."
If you're the admin who has to say yes or no to this before 3 December, the rest of this page is our measurements and five things to check on your own site.
You'll see two names for the product. Atlassian's support pages and the admin screen now say Atlassian MCP server, while the developer docs, the credits page and most people searching still say Rovo MCP server. It's the same server. I'll call it the Atlassian MCP server from here.
This piece covers cost only; what the server can read and change is in our Atlassian MCP server permissions guide.
Note Prerequisites - check these before step 1
Role: organization admin, so you can open Atlassian Administration at admin.atlassian.com. We ran every step as one.
Product: Jira and Confluence Cloud. We tested Cloud only. Data Center isn't covered here.
Plan: any paid Jira, Confluence, Service Collection or Teamwork Collection Cloud plan includes a Rovo credits allowance. Our test organization has Service Collection Premium with 4 users and Rovo turned on, and its meter shows an allowance of 7,105 credits. Atlassian's table gives Service Collection Premium 700 credits per user, which would be 2,800 for 4 users. We haven't traced why ours is higher, so read your own allowance on the Usage tab.
An AI tool that can use MCP, for step 3 only. We give the Claude Code command because Atlassian documents it.
About 20 minutes, most of it waiting for the meter.
When you're done you'll know what the MCP server has cost you so far and who used the credits. You'll also know where the charged tools can be blocked, and what your pay-as-you-go limit is.
What we found on 19 November 2026
Eleven calls that read or changed one thing in one app cost 0 credits. Six were lookups, a JQL search among them, and five were writes.
An all-app search, the search tool with targetApp set to ALL, cost 6 credits both times we asked the same question. The same tool limited to Confluence or Jira cost 1, even when it found nothing.
A graph context call on one Jira work item cost 5 credits when it ran alone. A batch of four graph calls with it in cost 5 as well.
Of our 26 calls, 7 were charged, for 25 credits in total. The other 19 cost nothing. All 25 credits showed up in the admin meter under a feature called Teamwork Graph and under the user who made the calls. No row on the meter's four tabs says MCP.
Is the Rovo MCP server free? What Atlassian's docs say today
Connecting, lookups in one app and writes are free. What Atlassian labels Enriched is charged, apart from Enriched tools still in beta, which mostly aren't billed until they leave beta. Both lists sit in one row of the credits page, called Teamwork Graph Context.
Teamwork Graph (TWG in Atlassian's docs) is its map of how your work and the people doing it connect across apps. We explained it in What is Atlassian Teamwork Graph?.
Under Free that row lists "Installing Teamwork Graph CLI and Atlassian Rovo MCP" (the CLI is a command-line tool), "Write operations such as updating a Jira work item", and "Requesting single product context, such as looking up a Jira work item or Confluence page's content." That row is on Atlassian's credits page. On your admin meter the charges show up in a row named just Teamwork Graph.
Under Enriched it lists calls that "involve complex queries, cross-product traversals, and enriched context lookups", and it adds that they "encompass unified search through the Teamwork Graph CLI and Rovo MCP". Unified search is Atlassian's name for what I call an all-app search here. The price cell reads "Vast majority of enriched TWG API and tool calls are 1-10 Rovo credits per call". The Rovo licensing page goes further in its FAQ: "Typical prompts require multiple TWG API calls, consuming 10-25 Rovo credits total."
There's one more line on the supported tools page that surprised me: "Enriched tools consume Rovo credits even if Rovo or AI is turned off for your site", because, the page goes on, billing doesn't depend on AI being used. So turning Rovo off doesn't make these calls free.
Sean Bourke of the Atlassian Team answered this on 7 November 2026. In the thread COST MCP he wrote: "As a general principle, access to MCP and access to key and core product features do not consume any Rovo Credits." He also wrote that "There are additional features which may utilise Rovo Credits which are enriched but do not use generative AI." That matches our run. The 11 lookups and writes cost 0 credits. The 7 charged calls were searches and graph context calls.
Search is in beta, and it's charged. On the supported tools page, search is marked Beta and Enriched. Other beta tools there carry the note "Usage is not billed during beta", and search doesn't. The page also says "Some beta tools may consume credits while still in beta; see the toolβs description for details." The tool's own description, which the server sends to your AI tool, reads: "The utilisation of this tool may consume up to 10 Rovo Credits. If the user or organization does not have any Rovo Credits available, the tool call will fail." Our meter agreed. It moved by 1 or 6 credits on every search that ran.
Rovo MCP server cost per call: lookups, writes and all-app search
Every call below went to https://mcp.atlassian.com/v2/mcp, the endpoint Atlassian's setup page gives. We signed in as an organization admin through OAuth 2.1, the sign-in where you approve access in the browser.
The lookups went as one batch and the writes as another. The four graph tools ran twice: once together, when the meter moved by 5, and once one at a time, when getGraphContext cost 5 and the other three 0. Every other call went alone. "Credits" is how far the organization's Rovo credits meter moved.
- Group Tool What we asked for Credits Lookups
getAccessibleAtlassianResourcesthe sites we can reach 0 for the batch of 6 - Lookups
getJiraIssueone work item 0 (in the batch) - Lookups
searchJiraIssuesUsingJql10 newest work items of one space 0 (in the batch) - Lookups
listJiraIssueCommentscomments of one work item 0 (in the batch) - Lookups
getConfluenceContentone page, full content 0 (in the batch) - Lookups
searchConfluencea CQL search, 25 results 0 (in the batch) - Writes
createJiraIssuea new task 0 for the batch of 5 - Writes
editJiraIssuesummary and labels 0 (in the batch) - Writes
transitionJiraIssueone transition 0 (in the batch) - Writes
addOrEditJiraIssueCommentone comment 0 (in the batch) - Writes
createConfluenceContenta new page 0 (in the batch) - Search and graph search,
targetAppALL"payroll upgrade cutover risks", 10 results 6, twice - Search and graph search,
targetAppCONFLUENCE"how do we handle third party risk reviews", 10 results 1, twice - Search and graph search,
targetAppJIRA"payroll upgrade cutover risks", 0 results 1 - Search and graph search with limit 1 rejected: limit must be 10 to 30 0
- Search and graph
getConfluenceContent, AI summary a summary of one page 0 - Search and graph
getGraphContextone work item, summary detail 5 alone; the batch of four cost 5 - Search and graph
getGraphObjectthe same work item by its URL 0 alone; also in the batch of four - Search and graph
getWorkActivity(beta) the signed-in user's last 7 days 0 alone; also in the batch of four - Search and graph discover "list Jira projects" 0 alone; also in the batch of four
JQL is Jira Query Language and CQL is Confluence Query Language, the search syntax each app has.
Of the tools in the Search and graph rows, Atlassian's supported tools page marks search, the graph context tool and getWorkActivity as Enriched; getGraphObject, discover and getConfluenceContent aren't marked. Don't plan on 0 for getWorkActivity: its entry says "Usage is not billed during beta" and that pricing will be announced when it becomes generally available.
We watched the meter for six minutes after the lookups and six more after the writes. It stayed at 616. I didn't expect a search that found nothing to cost a credit, but it did. The same question cost six times more across all apps than inside Jira alone. We don't know why. The 6 comes from one question asked twice, so please don't read it as a fixed price. And the AI summary of a page came back for 0 credits. I suspect Confluence had stored it already.
If you look these tools up, Atlassian's pages call the charged context tool getTeamworkGraphContext, and the server we called lists it as getGraphContext, with getGraphObject beside it. On the older endpoint, /v1/mcp, our API token listed four tools, and the graph ones there had the long names.
Every charged call ran with an OAuth sign-in, so we can't say a call made with an API token is charged the same. We called getGraphContext on one work item at summary detail, so 5 is one data point, and about ten tools were never called. The calls came from our own script, one tool call at a time, so we didn't count how many calls Claude makes for one prompt.
The five checks, in order [[steps]]
- Read the Rovo credits meter and look for a Teamwork Graph row.
- Open the Users tab to see who has used the most credits.
- Connect an AI tool, only if you want to watch a charge arrive yourself.
- Find the two toolsets that hold the charged tools.
- Check your pay-as-you-go limit before 3 December 2026.
Step 1. Check the Rovo credits meter for a Teamwork Graph row
The Rovo credits meter in Atlassian Administration records MCP charges, and you can read it before anyone connects anything. In Atlassian Administration, select your organization if you have more than one, then select Usage, then Meters. The list of meters opens, with a line like "Rovo credits 616 of 7,105 credits". Select Rovo credits. It opens on a page with tabs. Select the Features tab. You see one row per feature with its credits for the billing period. Look for a row named Teamwork Graph. On our organization every charged MCP call was counted in this row. Its number is what all-app searches and graph context calls have cost since the period started. We didn't run the Teamwork Graph command-line tool, so we can't say whether its calls land here too.
Check that it worked. You're on the Features tab and can read a credits number next to each feature. Before our run ours had two rows, Rovo Agents with 590 credits and Rovo Chat with 66. After it there was a third.
The path has moved since our older Rovo pieces. In October this screen was under Insights, then Platform usage. How to check Rovo credits usage for each user still describes the tabs correctly.
Step 2. See who used the credits on the Users tab
On the same Rovo credits page, select the Users tab. You see one row per person with their credits for the period. Read the list, which on ours was ordered by credits used, highest first. The number per person covers all their Rovo use, so it tells you who to ask, not what they ran. A charged MCP call is added to the person who was signed in when it ran.
Optional: select the Apps tab. It didn't change in our run. Don't expect MCP usage there. For more detail, select Export data. Atlassian's credits page says the file includes "feature, user, agent, timestamp, and number of credits consumed". Atlassian emails you a download link, and the dialog says exports "include up to 3 months of usage data or the first 1 million usage events".
Check that it worked. On our site the calling user went from 437 to 462 credits, the same 25 the Features tab gained. The export we took in October has columns for Date, App, Actor ID, Feature and Agent, and it already had a Teamwork Graph row at 0 credits. We haven't opened an export that holds MCP calls, so we can't tell you what else marks them in the file.
Step 3. Optional: connect Claude Code and watch a search reach the meter
You don't need this step to read your costs. Do it if you want to check a charge on your own site. In a terminal, run the command from Atlassian's setup page. Claude Code should print a line starting "Added HTTP MCP server".
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
In Claude Code, run /mcp to sign in, as Atlassian's page says. We signed in with a script, not through this prompt. In the term
Comments
No comments yet. Start the discussion.