Back to the MCP Gateway catalog

MCP Gateway · Catalog

Atlassian Rovo icon

Atlassian Rovo MCP server

Official

Atlassian Rovo MCP is the official Model Context Protocol server for Atlassian Rovo, with OAuth and tools that let agents search across Atlassian Cloud, read and create Confluence pages and comments, and create, edit, and transition Jira issues. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Project management31 toolsAuth: oauth

Behind the MCP Gateway

Run Atlassian Rovo MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Atlassian Rovo call inspected and logged.

Deploy on MCP Gateway

Tools · 31

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

atlassianUserInfo

Get current user info

getAccessibleAtlassianResources

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.

getConfluencePage

Get a Confluence page or blog post by ID, including body content.

searchConfluenceUsingCql

Search content with CQL

getConfluenceSpaces

Get spaces

getPagesInConfluenceSpace

Get pages or blog posts in a space

getConfluencePageFooterComments

Get footer comments for a page or blog post

getConfluencePageInlineComments

Get inline comments for a page or blog post

getConfluenceCommentChildren

Get reply(child) comments for a comment

getConfluencePageDescendants

Get child pages of specified page

createConfluencePage

Create a Confluence page or blog post

updateConfluencePage

Update a Confluence page or blog post

createConfluenceFooterComment

Create a footer comment on a page or blog post

createConfluenceInlineComment

Create an inline comment on specific text in a page or blog post

getJiraIssue

Get issue details

editJiraIssue

Update issue

createJiraIssue

Create issue

getTransitionsForJiraIssue

Get transitions

getJiraIssueRemoteIssueLinks

Get remote links

getVisibleJiraProjects

Get projects

getJiraProjectIssueTypesMetadata

Get issue types

getJiraIssueTypeMetaWithFields

Get field metadata

addCommentToJiraIssue

Add comment

transitionJiraIssue

Transition issue status

searchJiraIssuesUsingJql

Search issues with JQL

lookupJiraAccountId

Lookup user IDs

addWorklogToJiraIssue

Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog;

getIssueLinkTypes

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).

createIssueLink

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.

searchAtlassian

Search Jira and Confluence 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

fetchAtlassian

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

Questions

What is an Atlassian Rovo MCP server?
An Atlassian Rovo MCP server exposes Atlassian Rovo to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as atlassianUserInfo or getAccessibleAtlassianResources to work with Atlassian Rovo. The server in this catalog is the official Atlassian Rovo MCP server, which authenticates with OAuth.
What can you do with Atlassian Rovo MCP?
Agents can search across Atlassian Cloud, read and create Confluence pages and comments, and create, edit, and transition Jira issues. The catalog lists 31 tools for this server, including atlassianUserInfo, getAccessibleAtlassianResources, and getConfluencePage. The full list with descriptions is on this page.
Why put Atlassian Rovo MCP behind an MCP gateway?
Connecting the Atlassian Rovo MCP server directly to each client means a separate credential per developer, no inventory of who can reach Atlassian Rovo through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Atlassian Rovo server, so sign-in runs through your identity provider, role-based access decides which teams can call which Atlassian Rovo tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Atlassian Rovo and to every other server in your catalog.
How do you connect Atlassian Rovo MCP through a gateway?
Add the Atlassian Rovo server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Atlassian Rovo tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Atlassian Rovo MCP?
Community-built Atlassian Rovo MCP servers wrap the same Atlassian Rovo surface but are not vendor-maintained, and most authenticate with a static credential that gives an agent everything the credential owner can touch. This catalog lists the official Atlassian Rovo MCP server, which uses OAuth. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access, and an audit trail of every call.

AI everywhere.

Control here.

Talk to usLearn more