What we're building

We are extending the Atlassian Remote MCP Server so that MCP-compatible clients (e.g. Claude, Cursor, and other MCP-aware tools) can invoke Atlassian's Rovo AI agent as a single delegated tool.

Today, MCP clients connected to Atlassian can perform individual product actions (read/write Jira issues, fetch Confluence pages, search Bitbucket, etc.). With this change, the same clients will also be able to ask Rovo to handle multi-step, cross-product tasks on the user's behalf, using the existing OAuth session.

What this means for customers

• From any MCP-compatible client, you'll be able to delegate higher-level requests like "Summarise the last sprint and draft a Confluence retro page" or "Look at this PR and link any related Jira issues" to Rovo without leaving your tool of choice.
• The action runs under the same OAuth identity and permissions the user has already consented to for Atlassian MCP.
• This will be made available through the standard MCP tool list, so no custom integration work is needed on the client side beyond connecting to Atlassian's Remote MCP Server.

Availability

• Initially rolling out behind a feature gate to internal and early-access customers.
• General availability date will be announced via the Atlassian Remote MCP Server changelog and the Atlassian Developer Blog once we complete validation with the first set of MCP clients.

Related

•  Atlassian Remote MCP Server: https://www.atlassian.com/platform/remote-mcp-server 
•  Rovo: https://www.atlassian.com/software/rovo