Atlasian Rovo Connector(Claude) - pricing and API call cost clarification

[bhanub]

Hi Atlassian Support,

We're evaluating the Rovo MCP Server (Atlassian connector in Claude) for our Sales team at Zenoti. Need pricing clarity before enablement:

1. Any cost to enable the Rovo MCP Server and connect it to Claude — included in our existing Jira/Confluence Cloud subscription, or separate Rovo licence required?

2. Per-call charges from Atlassian's side for standard operations (search issues, read Confluence pages, create tickets)? If yes, what's the unit and rate?

3. Do standard Jira/Confluence read/write calls consume Rovo credits today, or only specific tools like Teamwork Graph? What's the credit allowance and overage rate?

4. Status of Teamwork Graph tool billing (getTeamworkGraphContext, getTeamworkGraphObject) — confirmed GA date? Will we get the 90-day notice before charges?

5. Rate limits or fair-use thresholds we should plan for?

6. Where can admins see usage / cost reporting for MCP calls?

Context: ~100 Sales users, mostly querying Confluence SOPs and SLOPS Jira tickets. Estimated 50–200 queries per user per month at full rollout.

Doc links welcome. Happy to jump on a call if easier.

Thanks,
Bhanu Prakash Buddana
Sales Operations, Zenoti

[Alexander Nilsson]

Hello Bhanu,

this one comes up often and the good news is that for your sales rollout, the cost picture today is mostly zero. Let me go through your points one by one.

On 1 and 2: there is no separate licence and no per-call charge from Atlassian for the MCP server itself. Rovo is bundled into all paid Jira, Confluence, JSM and Teamwork Collection cloud subscriptions, so if your sales users already have Jira or Confluence seats, the MCP server is in scope. One activation gate to know about, the org admin has to enable Rovo and your organization must be on a verified domain.

On 3: standard Jira and Confluence reads and writes through the MCP server do not consume Rovo credits today. The page that defines what actually burns credits lists only three billable features right now, 10 credits per request to Rovo Chat, 10 credits per request to Rovo Agents, and 100 credits per Deep Research request. The MCP Server is explicitly called out as free and not counting against your Rovo credit allowance. For reference, the included allowance is 25 credits per user per month on Standard, 70 on Premium, 150 on Enterprise (Jira, Confluence, JSM seats), pooled at the org level. Full table here:

https://support.atlassian.com/rovo/docs/rovo-usage-limits/

On 4: the Teamwork Graph tools getTeamworkGraphContext and getTeamworkGraphObject are currently in beta and free. The docs commit to a minimum of 1 Rovo credit per call once they move to GA, with multi-step or AI-inferencing calls potentially costing more. No GA date is published, and Atlassian commits to 90 days notice and an explicit opt-in before any overage becomes billable. The supported tools page is the source for this:

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

On 5: the public docs do not publish hard rate limits or fair-use thresholds for MCP calls. What is documented is the credit pool and the 80% / 100% allowance notifications. For your scale (100 users, 50 to 200 calls per month per user, mostly reads), you should be well within bounds since reads do not draw credits today. If you plan to layer Rovo Chat or Agents on top, that is where the credit math starts to matter.

On 6: admin usage and audit reporting lives in Atlassian Administration under Insights, Audit log. Every MCP tool invocation is logged with tool name, action and user, and you can filter for "Rovo MCP User Actions" or search "MCP". Be aware that if your team uses API token authentication instead of per-user OAuth, calls show up under the technical user, not the end user, which matters for your sales user attribution:

https://support.atlassian.com/security-and-access-policies/docs/monitor-atlassian-rovo-mcp-server-activity/

Just to summarize it: enable it, no extra cost today, watch the Teamwork Graph GA announcement (90 day clock) if you start using those two tools, and keep an eye on the audit log for adoption tracking.

Hope that helps and feel free to ask if you any further questions.

Greetings,

Alex