# Atlassian will meter Rovo MCP and Teamwork Graph context calls from December 3 Atlassian's upcoming usage-based billing reaches beyond its own AI features: enriched context queries made through Rovo MCP and Teamwork Graph CLI will consume credits, while ordinary single-product lookups and writes remain free. From December 3, agent workflows that ask Atlassian's Teamwork Graph for cross-product context will need a cost budget. Most enriched tool calls use 1–10 Rovo credits, with paid overages at $0.01 per credit. - Status: Active - Published: 2026-10-08T17:56:26+13:00 - Updated: 2026-10-08T17:56:26+13:00 - Categories: Artificial Intelligence, Web Development, SaaS, Pricing & Billing, AI Agents, AI SaaS, Developer Tools - Tags: AI agents, Atlassian, Model Context Protocol, Rovo, usage pricing - Canonical HTML: https://beyondthe.news/dossiers/atlassian-rovo-mcp-teamwork-graph-usage-billing-december-2026 ## What changed Atlassian announced on September 1 that expanded usage-based billing for Rovo credits, automation steps and AI agent resolutions begins December 3, 2026. Its current Rovo documentation explicitly includes enriched Teamwork Graph context accessed through the Rovo MCP server and Teamwork Graph CLI, including unified search and cross-product queries. Most enriched context tool calls consume 1–10 Rovo credits, while basic Rovo interactions consume 10 and premium AI features vary. Included monthly credits are pooled across an organisation; extra usage currently lists at $0.01 per credit. Installing MCP, simple single-product lookups and write operations remain free. ## Why it matters Builders using Claude, ChatGPT or custom agents to interrogate Jira and Confluence can no longer treat every enriched context retrieval as an unmetered integration call. Query design, cache policy, agent loop frequency and spending caps become part of operating cost. A simple work-item lookup is not the same billable event as a Teamwork Graph traversal. This creates an actionable distinction for small teams before December 3, without implying that every Jira API call or MCP tool invocation will be charged. ## The boundary is enriched context, not every API request Atlassian documents free single-product lookups and writes, including looking up a Jira issue or updating it. Enriched Teamwork Graph searches and cross-product relationship queries are metered, including searchAtlassian and context tools invoked through Rovo MCP or TWG CLI. The vast majority of these enriched calls consume 1–10 credits, depending on the operation. ## The cost model sits above existing subscriptions Standalone Jira and Confluence plans include 25 Rovo credits per user per month on Standard, 70 on Premium and 150 on Enterprise. Teamwork and Service Collections include higher per-user allowances. Credits pool across the organisation and reset monthly. Beyond the included pool, the published list price is $0.01 per credit, with prepaid options and discounts. ## Controls matter for agent loops Atlassian says extra usage is enabled by default on its general Rovo billing documentation, with alerts at 80% and 100% of allowance and optional spending ceilings or disabling overage. When metered capacity is exhausted with extra usage off, affected enriched calls pause. Its Teamwork Graph CLI FAQ separately describes an explicit opt-in, so admins should confirm the setting on their own organisation rather than rely on an assumption. ## Founder evidence illustrates the risk but not a universal price SaaStr founder Jason Lemkin says its 21-plus agents make 35,000–40,000 vendor API calls per day and describes an unverified estimate of up to $240,000 annually for future agent access across multiple vendors. That is an operator's scenario, not an Atlassian rate card or proof that all those calls are billable. The relevant lesson is to meter real workflows before a usage policy goes live. ## Key details - Atlassian announced expanded usage pricing September 1, 2026; billing starts December 3 for most meters. - Enriched Teamwork Graph API, TWG CLI and Rovo MCP context calls are in scope; free lookups and writes are not. - Most enriched TWG calls consume 1–10 Rovo credits; basic Rovo Chat and agents consume 10 credits per invocation. - Standalone Jira and Confluence allowances are 25/70/150 credits per user monthly for Standard/Premium/Enterprise; collections offer larger allowances. - Credits pool at organisation level, reset monthly and do not roll over. - Published list overage price is $0.01 per Rovo credit; usage caps and extra-usage controls are available. - Atlassian documentation is inconsistent on default overage opt-in across product-specific pages; check actual admin settings. ## Builder takeaways - Instrument agent calls by free single-product lookup versus enriched Teamwork Graph retrieval, and record credit consumption per workflow. - Cache or batch repeat context requests where correctness permits; do not let an autonomous loop repeatedly run expensive enriched searches without a budget. - Review Atlassian Administration > Insights > Platform usage, and set limits or disable extra usage before December 3. - Estimate monthly cost from the organisation's pooled allowance and actual enriched-call mix, not raw API request counts. - Do not conflate SaaStr's cross-vendor $240,000 anecdote with Atlassian's published per-credit price. ## What to watch - Whether Atlassian changes the December 3 start date or rate card. - Clarification of contradictory extra-usage opt-in wording across Atlassian support pages. - New per-agent allocation and usage export controls, and whether they are available before billing begins. - Real-world billing distributions for high-volume MCP/Teamwork Graph workloads. ## Uncertainties - Actual bills depend on plan allowances, workload mix, and which calls receive the enriched-context classification. - Most enriched calls use 1–10 credits, but complex operations and future features can vary. - One Atlassian FAQ says extra usage requires explicit opt-in, while its current Rovo documentation says it is enabled by default. - SaaStr's $240,000 annual estimate is a founder report spanning multiple vendors, not a verified price or Atlassian quote. ## Sources - [Atlassian’s usage-based pricing: AI value with predictability and control](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing) — Atlassian · primary · 2026-09-01T00:00:00+12:00. Official announcement of new meters and December 3 start. - [How Rovo credits work](https://support.atlassian.com/rovo/docs/rovo-usage-limits/) — Atlassian Support · primary documentation · 2026-10-08T00:00:00+13:00. Live detailed classification of MCP/TWG calls, free exceptions, included credits, overage price and controls; page undated, checked October 8. - [Usage-Based Pricing](https://www.atlassian.com/resources/usage) — Atlassian · primary documentation · 2026-10-08T00:00:00+13:00. Live official terms, date and admin control details; page undated, checked October 8. - [We Got a $240,000 Estimate for Agent API Access](https://www.saastr.com/we-got-a-240000-estimate-for-agent-api-access-our-agent-suggested-a-5-postgres-instance/) — SaaStr · secondary · 2026-10-03T00:00:00+13:00. Founder account of agent access costs; quote and estimates are self-reported and not Atlassian-specific.