Atlassian says its MCP v2 server now offers more than 220 tools, but the immediate question for platform teams is how much access and metered context to put behind an agent. The company’s October 6, 2026 general-availability announcement pairs a larger tool catalog with an internal token-efficiency claim. Its support documents add two deadlines: extra Rovo-credit billing on December 3, 2026, and a v1-to-v2 transition beginning March 1, 2027.
Those changes call for separate decisions about authorization, workflow cost, and compatibility. A broader catalog does not establish that an organization should expose every action, and fewer model tokens do not establish a cheaper completed task.
Key takeaways
- Atlassian says MCP v2 offers 220+ tools, with discovery on demand and separate read, write, and destructive execution.
- The up-to-25% token reduction comes from an internal Claude benchmark on Jira and Confluence work; it does not establish total-cost savings.
- Free operations and metered enriched context coexist. Extra-credit billing is scheduled for December 3, 2026; the v1 transition begins March 1, 2027.
More tools, discovered as needed
The launch post describes coverage for Jira, Confluence, Bitbucket Cloud, Code Search, Goals, Focus Areas, and Loom. It marks the new Jira Service Management service-workflow coverage as coming soon. That distinction matters when deciding which workflows can move into a pilot today.
Atlassian also reports more than 15 million calls a day. The announcement supplies no user count, time series, or measurement methodology for that figure. It is a vendor-reported activity measure, not independent evidence of adoption or successful task completion.
The operational change is how the catalog reaches the client. According to the supported-tools documentation, v2 discovers tools on demand rather than sending every definition when a client connects. Primary tools include discover, executeRead, executeWrite, and executeDestructive. Administrators grant or revoke access through permission groups.
For a platform team, the useful assessment is whether the tools available to a particular identity match its intended work. Dynamic discovery changes the payload presented to an agent; it does not, by itself, justify broader action rights.
The 25% result has a narrow scope
Atlassian says internal benchmarking on Claude models found up to 25% fewer tokens than the previous version for the same Jira and Confluence work. The claim concerns model-token consumption within that comparison. It is not a published finding of 25% lower bills, faster completion, or better answers across the expanded product catalog.
The announcement does not disclose model versions, the task set, prompts or setup, baseline token totals, or variance. The reviewed research contains no independent benchmark or end-to-end cost comparison. Teams therefore cannot assume the upper-bound result applies to their clients or cross-product workflows.
Our assessment is to compare representative tasks using separate records for model-provider tokens and Atlassian credits. Include retries and write actions, and judge the cost against an accepted result. A smaller tool-definition payload may help token efficiency, but the vendor’s result alone cannot settle that wider calculation.
Permissions remain a deployment check
Atlassian documents OAuth 2.1 with PKCE as the default authentication approach and says requests respect the authenticated user’s existing access. API-token authentication is an optional alternative that an organization administrator must enable. The company also describes scopes, domain and IP allowlists, and organization audit logging. These are documented controls, not controls this article has tested. See authentication and authorization.
The setup guide lists ChatGPT, Claude, Docker, GitHub Copilot CLI, Google Gemini, and Amazon Quick Suite among supported clients. That list does not establish identical capabilities or configuration across clients. Nor do the reviewed sources establish equivalent plan availability for every security control.
A practical pilot should, in our assessment, start with the smallest necessary permission groups. Read, write, and destructive actions deserve separate decisions. Teams should check user-level access and the audit trail in their own configuration before expanding the workflow.
Tool access and enriched context have different meters
Atlassian’s Rovo-credit documentation separates free MCP operations from enriched-context usage. Simple single-product context lookups, installation, and write operations such as updating a Jira work item are listed as free. Enriched cross-product context and unified search consume variable credits; Atlassian says the vast majority of enriched calls cost 1–10 credits each.
| Operation | Documented Rovo-credit treatment |
|---|---|
| Simple single-product context; write operations | Listed as free |
| Enriched cross-product context; unified search | Variable credits; most enriched calls use 1–10 |
Extra-usage billing is scheduled to begin December 3, 2026. The documentation checked for this report on October 8 lists $0.01 per extra credit, or $10 per 1,000. It says extra usage is enabled by default, with alerts at 80% and 100% of the included allowance. Administrators can set spending caps or disable extra usage.
Allowances and actual consumption vary by plan and operation. There is no single credit price for every MCP workflow. Our assessment is that teams should inspect enriched-context consumption and extra-use settings before the billing date, while keeping this meter separate from the model provider’s charges.
A rollout checklist before the two deadlines
Atlassian’s upgrade guide says existing v1 use will begin exposing and using v2 tools on March 1, 2027. It warns that incompatible clients may need cached clientIds or .well-known credentials cleared. Because v2 is a separate OAuth resource, some setups require replacement and reauthentication.
Based on those documented conditions, we assess four checks as useful before a wider rollout:
- Inventory v1 endpoints, clients, gateways, and stored OAuth configurations.
- Check v2 discovery, reauthentication, and permission boundaries with each intended client.
- Compare token and credit consumption on representative work, including cross-product lookups and retries.
- Review extra-usage settings and choose a spending cap before December 3.
These are proposed checks, not completed tests. The release offers more actions to evaluate; the evidence still leaves each organization responsible for establishing which actions, costs, and client transitions fit its deployment.
Related reading: Microsoft Copilot Usage Billing: What Can Admins Budget for Agent Work?
Image disclosure: This article uses original AI-generated conceptual illustrations, not Atlassian product interfaces.