Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can Rovo's AI writing capability be called programmatically via API?

Tiffany Garbanzos
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 3, 2026

Hi — I'm trying to understand whether Rovo's AI content generation is accessible via API from an external tool.

We've built an automated workflow using Claude where it pulls Jira tickets and creates Confluence pages automatically. Rovo produces better release note drafts than Claude on its own because it cross-references the REQ ticket with all related linked tickets for fuller context.

What I'd love to do is have Claude handle the workflow side (finding tickets, organizing batches, creating Confluence pages) and have Rovo handle the actual content generation — essentially calling Rovo's AI via API to generate the draft, then passing that output back to Claude to create the page.

Is that something Rovo exposes via API, or is Rovo's AI writing capability only accessible from within the Atlassian UI? And if it is accessible, what credentials or setup would be needed?

Thanks!

1 answer

1 accepted

2 votes
Answer accepted
Ajay _view26_
Community Champion
June 3, 2026

Hi @Tiffany Garbanzos 

Atlassian announced two new interfaces at Team '26. The Rovo MCP Server now exposes Teamwork Graph tools (getTeamworkGraphContext, getTeamworkGraphObject) that let any MCP-compatible AI agent — including Claude — query the full cross-ticket relationship graph across Jira, Confluence, Bitbucket, and 75+ connected tools. The Teamwork Graph CLI does the same for terminal/CI environments. Have you explored these tools for your use-case?

Tiffany Garbanzos
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 8, 2026

Hi Ajay — thank you so much, this is exactly what I was looking for!

Two follow-up questions:

  1. Do these tools (getTeamworkGraphContext and getTeamworkGraphObject) require a specific Rovo plan or admin setting to be enabled? I checked my current Atlassian MCP connector in Claude and the tools aren't showing up yet.
  2. Is there anything I need to do on my end to update the connector to get access to these tools, or would this need to be enabled by our Atlassian admin?

Appreciate your help!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events