ChatGPT Plugin

Atlassian Rovo (Legacy)

Read/write Jira & Confluence

Brand: Atlassian

Category: Productivity
Primary Subcategory: Project & Task Management Platforms

Integration details

Description

The Atlassian Rovo MCP Server connects ChatGPT to your Atlassian workspace, so you can work with Jira, Confluence, and Compass directly from your conversation. Find and summarize Jira issues, create and update tickets, transition statuses, and add comments without switching tabs. Search, read, draft, and edit Confluence pages with full context. Explore Compass components and their related issues and documentation. The Atlassian Rovo MCP Server supports both read and write actions, enabling you to retrieve information and take action in real time. It also includes dedicated UI components for Jira and Confluence, making issue details, page content, and updates easier to review and act on directly within ChatGPT. More Atlassian products are coming soon.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Productivity
Primary Subcategory: Project & Task Management Platforms
Secondary Subcategories: None listed
Brand: Atlassian
Access: Account required
First tracked: 2026-09-03
Tool count: 32
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

No longer visible · last seen 14 Oct

Your Plugin is no longer discoverable

We previously found Atlassian Rovo (Legacy) discoverable in ChatGPT, but ChatGPT is no longer surfacing it.Add your email below and we’ll let you know when your Plugin becomes discoverable again, and send you alerts about it.

No spam. Unsubscribe any time.

See who ChatGPT suggests

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Project & Task Management Platforms

View Category

Listed in alphabetical order

Primary Subcategory

Adobe Workfront0/100

AgentCron0/100

Agiflow0/100

AIOProductOS0/100

Aphex0/100

Atlassian Rovo (Legacy)43/100

Tools

32 tools agents can invoke

Add or update a comment on a Jira issue
addCommentToJiraIssue
Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog;
addWorklogToJiraIssue
Create a footer comment on a page or blog post
createConfluenceFooterComment
Create an inline comment on specific text in a page or blog post. For top-level comments, provide pageId and inlineCommentProperties (text selection + match counts). For replies, provide parentCommentId only (no pageId or inlineCommentProperties). You must first fetch the page content (e.g. using getConfluencePage) to find the exact text and count how many times it appears. Incorrect or missing inlineCommentProperties can result in a 400 error from the Confluence API.
createConfluenceInlineComment
Create a Confluence page or blog post. When contentFormat is "html" or omitted because HTML is the default, first call the getContentFormatGuide tool with { toolName: "createConfluencePage" } and follow the returned HTML-format guidance. Do not call it when contentFormat is "markdown".
createConfluencePage
Create a Jira issue. Use additional_fields to set any Jira field that does not have its own parameter (e.g. custom fields, priority, components).
createJiraIssue
Create a link between two Jira issues. For directional link types (e.g. Blocks): inwardIssue = issue that blocks, outwardIssue = issue that is blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A). Use getIssueLinkTypes if link type is unknown.
createIssueLink
Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content
fetch
Get reply(child) comments for a comment
getConfluenceCommentChildren
Get the canonical Confluence HTML-format guidance for `createConfluencePage` or `updateConfluencePage`. Use this tool before authoring HTML/default page bodies or fine-grained HTML edits. First call with only `toolName`; if the returned guidance references a follow-up document, call this tool again with the same `toolName` and `reference` set to that single referenced path. Fetch one document per call. Valid `toolName` values: createConfluencePage, updateConfluencePage.
getContentFormatGuide
Get current user info
atlassianUserInfo
Get field metadata
getJiraIssueTypeMetaWithFields
Get issue details
getJiraIssue
Get available Jira issue link types (e.g. Blocks, Duplicate, Clones, Relates). For createIssueLink: inwardIssue = blocker, outwardIssue = blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A).
getIssueLinkTypes
Get issue types
getJiraProjectIssueTypesMetadata
Get footer comments for a page or blog post
getConfluencePageFooterComments
Get pages or blog posts in a space
getPagesInConfluenceSpace
Get projects
getVisibleJiraProjects
Get remote links
getJiraIssueRemoteIssueLinks
Get spaces
getConfluenceSpaces
Get transitions
getTransitionsForJiraIssue
Get cloudId to make tool calls. When a link is provided (e.g. https://site.atlassian.net/*), try passing the site hostname (e.g. site.atlassian.net) as cloudId to other tools first; if that fails, use this tool to list accessible resources.
getAccessibleAtlassianResources
Get child pages of specified page
getConfluencePageDescendants
Get inline comments for a page or blog post
getConfluencePageInlineComments
Lookup user IDs
lookupJiraAccountId
Get a Confluence page or blog post by ID, including body content.
getConfluencePage
Search Jira, Confluence and linked 3P data using Rovo Search, ALWAYS use this tool to search for Jira and Confluence content unless the word CQL or JQL is used in the context. The utilisation of this tool may consume up to 10 Rovo Credits. If the user or organization does not have any Rovo Credits available, the tool call will fail.
search
Search Confluence content (pages, blog posts, comments, attachments) using CQL (Confluence Query Language). CQL is specific to Confluence and is not interchangeable with JQL.
searchConfluenceUsingCql
Search issues with JQL, total counts only when explicitly requested.
searchJiraIssuesUsingJql
Transition issue status
transitionJiraIssue
Update a Confluence page or blog post by replacing its body or applying fine-grained edits. Before an HTML/default full-body update or any fine-grained edits, first call the getContentFormatGuide tool with { toolName: "updateConfluencePage" } and follow the returned HTML-format guidance. For fine-grained edits, then call getConfluencePage with contentFormat="html" and includeSnapshotToken=true, and pass the returned snapshotToken and copied data-local-id values. Do not call getContentFormatGuide for a Markdown full-body update.
updateConfluencePage
Update issue. After updating, returns the issue using the same default read fields as getJiraIssue (summary, description, status, issuetype, priority, labels, components, assignee, reporter, created, updated, resolution, project). Use getJiraIssue with fields ["*all"] or a custom list if you need more.
editJiraIssue

FAQs

Atlassian Rovo (Legacy) ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Atlassian Rovo (Legacy)'s ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Atlassian Rovo (Legacy) alternatives on ChatGPT?

As of 2026-10-28, Atlassian Rovo (Legacy) competes with Asana, Linear, monday.com, ClickUp, Trello, Smartsheet AU, Smartsheet EU, Smartsheet US and 78 more in ChatGPT Project & Task Management Platforms, ranked by public Discoverability Score.

Where does Atlassian Rovo (Legacy) rank in Project & Task Management Platforms on ChatGPT?

As of 2026-10-28, Atlassian Rovo (Legacy) ranks #3 of 87 in ChatGPT Project & Task Management Platforms with a Discoverability Score of 43/100 (Emerging).

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.