Atlassian Adds Capacity-Planning Tools to Rovo MCP
Five new read/write tools let approved AI clients inspect individual allocations and manage work across projects during a progressive tenant rollout.
Edited by Tyronne Panaino
Atlassian added individual capacity-planning tools to its Rovo Model Context Protocol service on September 24, 2026. The company says five tools are entering a progressive tenant rollout under separate `read_capacity_planning` and `write_capacity_planning` toolsets.
The change is aimed at organizations that want an AI-powered interface to inspect team-member allocations or manage work allocations across projects and work items. It also puts operational planning data behind tools that administrators may need to enable, so availability will depend on both Atlassian's rollout and each organization's access settings.
Read and write scopes are separated
The official changelog divides the new capabilities into read and write groups. The read side can show individual team-member allocations. The write side can manage work allocations that span projects and work items. Atlassian says the two groups contain five tools in total, although the fetched changelog entry does not enumerate every operation or its parameters.
That separation matters because looking at a capacity plan and changing it carry different operational consequences. A planning assistant may use read access to summarize where people are allocated, while write access can alter the plan that teams use to distribute work. Organizations evaluating the release should therefore treat the two toolsets as distinct permissions instead of assuming that access to one implies access to the other.
Rollout and administrator controls remain part of the release
Atlassian labels the release as a progressive rollout by tenant and says it is still in progress. The company also warns that organizations using automatic enablement for toolset groups may not see the capacity-planning tools become available to every user immediately.
Administrators can manage access and enable the toolsets from the Atlassian MCP section of the Admin portal. That gives organizations a defined control point during rollout, but the changelog does not say which tenants receive the tools first or provide a date when the rollout will be complete. Teams should verify their own tenant rather than infer availability from the announcement date.
The practical delta for planning workflows
The release moves capacity planning into the set of actions an MCP-connected AI interface can perform. For managers and project leads, the immediate value is a shorter path between asking about allocations and working with the underlying plan. For platform and security teams, the important boundary is whether a client can only inspect allocations or is also authorized to change them.
The fetched announcement confirms the product surface and access path, not the behavior of every connected client. It does not document in this entry how individual write actions are approved, which audit details are recorded, or how capacity permissions interact with every project role. Those questions need tenant-level testing and the supported-tools documentation before an organization treats the integration as ready for consequential planning changes.
What to verify during the rollout
A cautious evaluation can start by confirming whether the two toolsets appear in the Admin portal, enabling read access for a limited test group, and checking which allocations the connected client can actually retrieve. Write access should be tested separately against a controlled planning workspace, with the resulting project and work-item changes reviewed through the organization's normal governance process.
The next useful evidence will be a completed rollout, fuller operation-level documentation and real tenant experience with permissions and auditability. Until then, the supported conclusion is narrow: Atlassian has introduced five capacity-planning tools for Rovo MCP, divided them into read and write toolsets, and placed access under a progressive rollout with administrator controls.
Status
Confirmed. Internal confidence is medium because Atlassian's official developer changelog establishes the tools, scope and rollout state, while no independent tenant test was performed for this article.
Sources
Update note: Last reviewed 2026-09-25. We will revise this post when Atlassian completes the rollout or publishes material permission, audit or operation-level details.
Sources
- Atlassian developer changelog — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.