[Preview] Atlassian Rovo MCP v2

[Jemma Swaak]

Hi @Alex Gay 

Yes that makes sense. We are actively investigating creating something like that. I'll keep you updated!

[Abhinav Singh]

Hi team! I am Abhinav, PM Loom.. Great news. We now have Loom tools available on RovoMCP v2 Preview... check out the announcement post and some inspiration flows - 

https://community.atlassian.com/forums/Loom-articles/Loom-tools-are-live-on-Rovo-MCP-v2-Preview-your-recordings-now/ba-p/3274301

[Derek Chen-Becker]

Hi, we have a use case that involves creating new pages and then applying a page template to fill in the content. The new endpoint appears to have some tools related to this, but they don't work for me:

- getConfluenceTemplate
  - Retrieves a Confluence template by templateId.
  - Tested with an existing template; returned 404 Not Found.

- listConfluenceTemplates
  - Lists available Confluence templates.
  - Supports space, scope (global, space, available), type (page, blueprint, all), query, cursor, and limit.
  - Tested against a space with existing templates; returned 404 Not Found.

- createConfluenceContent
  - Creates Confluence pages or live documents.
  - Does not currently expose a template ID parameter in its schema, so template content must first be retrieved and then supplied in the page body.

I wanted to check first to make sure my understanding is correct and that these are intended to work as described.

Thanks!

[Tyler Brown]

Hey @Derek Chen-Becker ,

Thanks for the report. I was able to reproduce it and and a fix has been deployed. Can you give it another go and see if you are still experiencing the issues with the template tools?

"- Does not currently expose a template ID parameter in its schema, so template content must first be retrieved and then supplied in the page body." - This is intentional as you assumed, as we want to make the agent read the templates first, modify it if needed, then create from it as if its any other content. 

[Derek Chen-Becker]

Hi @Tyler Brown , I was able to test and it looks like the getConfluenceTemplate and listConfluenceTemplates work now. createConfluenceTemplate still does not appear to accept a template ID but Codex was able to work around it by manually copying the content of my test template and copying that in the body parameter of createConfluenceContent.

Cheers,

Derek

[Sean Bourke]

A huge thank you to everyone who tested and provided feedback throughout the v2 preview, your support helped us to improve the Atlassian MCP in readiness for v2.

I'm happy to share that Atlassian Rovo MCP v2 is now available via `https://mcp.atlassian.com/v2/mcp`. This introduces broader support for Loom, Goals, Projects, Goals, Teams, Focus, Talent and Code Search; as well as Bitbucket via OAuth.

If you need a flat list of tools for an MCP gateway, you can access this via `https://mcp.atlassian.com/v2/mcp?tools=all`.

A list of available tools is available here.

For anyone using the existing Preview endpoint, this has now been updated to reflect the existing v2 endpoint tools.

[Mike Knight]

Hi @Sean Bourke! One gap from the JSM side that carried over from preview.

Comments posted through addOrEditJiraIssueComment always land as public, so the customer sees them on the portal. commentVisibility restricts by role or group but doesn't set jsdPublic to false, so the reporter still gets it. In practice that means anything my agent writes on a ticket has to be customer safe, so diagnostic notes and account details either get watered down or I drop back into the UI to finish the work.

There's an open suggestion for it here: https://jira.atlassian.com/browse/ECO-1186

The Service Desk API already supports it with public: false, so this looks more like a gap in the wrapper than a new capability.

Is it on the roadmap now that v2 is out? A visibility flag on the comment tool, or a JSM specific comment operation behind discover/execute, would cover it either way.

[Joško Aničić]

Hi ,

The links to the reference documentation and a list of preview tools are not working, so I am posting this question. 
Does the MCP preview in some way support access to the Asset objects? Specifically, is there a way to retrieve a list of the available objects that can be selected for an Assets-backed field on a ticket/issue?

For example I got this from the codex cli:
----

Field                           Jira field ID

Product                      customfield_10200

Affected Clients        customfield_10214

Affected Modules     customfield_10273

These are Jira Assets object-reference fields. The current MCP exposes their stored references, but I could not find an operation to browse/search the available Assets objects behind those pickers.

----

Is this currently supported by the MCP preview?

If not, is there another way or workaround to query the available Assets objects so that I can determine which values can be set on these fields?

Thank you.