Supported tools

Currently, Atlassian Rovo MCP server tools marked as Beta are free to use, unless otherwise stated. In the future, these tools may become paid offerings; if that happens, we’ll provide advance notice before introducing any charges.

This page lists all the tools supported by Atlassian Rovo MCP server. Each listed tool is organised into permission groups, with each grouping one or more Atlassian Rovo MCP server tools by intent (for example, read, write, or search). Organisation admins grant or revoke access at the permission-group level, and each tool inherits the access of its parent group.

Jira tools

read_jira

Available using: OAuth 2.1 and API token authentication

Tool	Description	Required scopes
`getJiraIssue`	Get a Jira issue by ID or key.	`read:jira-work`
`getJiraIssueRemoteIssueLinks`	List remote issue links (for example, Confluence links) on a Jira issue.	`read:jira-work`
`getJiraIssueTypeMetaWithFields`	Get create‑field metadata for a project and issue type.	`read:jira-work`
`getJiraProjectIssueTypesMetadata`	List issue types available in a Jira project.	`read:jira-work`
`getIssueLinkTypes`	List available issue link types	`read:jira-work`
`getTransitionsForJiraIssue`	List available workflow transitions for an issue.	`read:jira-work`
`getVisibleJiraProjects`	List Jira projects the user can access.	`read:jira-work`
`lookupJiraAccountId`	Find Jira user account IDs by name or email.	`read:jira-work`

write_jira

Available using: OAuth 2.1 and API token authentication

Tool	Description	Required scopes
`addCommentToJiraIssue`	Add a comment to a Jira issue.	`write:jira-work`
`addWorklogToJiraIssue`	Adds a time-tracking worklog to a Jira issue.	`write:jira-work`
`createJiraIssue`	Create a link between two Jira issues.	`write:jira-work`
`editJiraIssue`	Update fields on an existing Jira issue.	`write:jira-work`
`transitionJiraIssue`	Perform a workflow transition on a Jira issue.	`write:jira-work`

search_jira

Available using: OAuth 2.1 and API token authentication

Tool	Description	Required scopes
`searchJiraIssuesUsingJql`	Search Jira issues using a JQL query	`search:jira-work`

Confluence tools

read_confluence

Available using: OAuth 2.1 and API token authentication

Tool	Description	Required scopes
`getConfluencePage`	Get a Confluence page or live doc by ID.	`read:page:confluence`
`getConfluencePageDescendants`	List descendant pages under a parent page.	`read:hierarchical-content:confluence`
`getConfluencePageFooterComments`	List footer comments on a page.	`read:comment:confluence`
`getConfluencePageInlineComments`	List inline comments on a page.	`read:comment:confluence`
`getConfluenceCommentChildren`	List child comments (replies) of a comment.	`read:comment:confluence`
`getConfluenceSpaces`	List Confluence spaces.	`read:space:confluence`
`getPagesInConfluenceSpace`	List pages in a space.	`read:page:confluence`

write_confluence

Available using: OAuth 2.1 and API token authentication

Tool	Description	Required scopes
`createConfluencePage`	Create a new Confluence page or live doc.	`write:page:confluence`
`updateConfluencePage`	Update an existing Confluence page or live doc.	`write:page:confluence`
`createConfluenceFooterComment`	Create a footer comment or reply on a page.	`write:page:confluence`
`createConfluenceInlineComment`	Create an inline comment tied to selected text.	`write:page:confluence`

search_confluence

Available using: OAuth 2.1 and API token authentication

Tool	Description	Required scopes
`searchConfluenceUsingCql`	Search Confluence content using CQL.	`search:confluence`

Jira Service Management tools

Jira Service Management tools only support authentication via API token. These tools are only available if authentication via API token is enabled by your organization admin.

read_jsm

Available using: API token authentication

Tool	Description	Required scopes
`getJsmOpsAlerts`	Get an operations alert by ID or alias, or search query.	`read:ops-alert:jira-service-management`, `read:ops-config:jira-service-management`, `read:jira-user`
`getJsmOpsScheduleInfo`	List on-call schedules or get current/next responders.	`read:ops-config:jira-service-management`, `read:jira-user`
`getJsmOpsTeamInfo`	List operation teams and team details.	`read:ops-config:jira-service-management`, `read:jira-user`

write_jsm

Available using: API token authentication

Tool	Description	Required scopes
`updateJsmOpsAlert`	Perform alert actions, like acknowledge, unacknowledge, close, or escalate an alert.	`read:ops-alert:jira-service-management`, `write:ops-alert:jira-service-management`

Bitbucket Cloud tools

Bitbucket Cloud tools only support authentication via API token. These tools are only available if authentication via API token is enabled by your organization admin and your Bitbucket workspace is linked to an organization.

read_bitbucket

Available using: API token authentication

Tool	Actions	Description	Required scopes
`bitbucketWorkspace`	`list`, `get`	Get workspace details.	`read:workspace:bitbucket`
`bitbucketRepository`	`list`, `get`, `defaultReviewers`	Get repository details and content.	`read:repository:bitbucket`
`bitbucketUser`	`pullRequests`	Get pull requests for the authenticated user.	`read:pullrequest:bitbucket`
`bitbucketDeployment`	`list`, `get`	Get deployment information.	`read:pipeline:bitbucket`
`bitbucketPullRequest`	`list`, `get`, `comments`, `diff`	Get pull requests.	`read:pullrequest:bitbucket`
`bitbucketRepoContent`	`branch.get`, `commit.get`, `files.get`	Get repository content.	`read:repository:bitbucket`
`bitbucketPipeline`	`list`, `get`, `steps`, `step.get`, `step.log`	Get pipeline details.	`read:pipeline:bitbucket`
`bitbucketEnvironment`	`list`, `get`	Get an environment.	`read:pipeline:bitbucket`

write_bitbucket

Available using: API token authentication

Tool	Actions	Description	Required scopes
`bitbucketPullRequest`	`create`, `merge`, `approve`, `comment`	Create and update pull requests.	`write:pullrequest:bitbucket`
`bitbucketRepoContent`	`branch.create`, `commit.create`	Create or update repository content.	`write:repository:bitbucket`
`bitbucketPipeline`	`run`	Run or manage pipelines.	`write:pipeline:bitbucket`
`bitbucketEnvironment`	`create`, `delete`, `update`	Manage deployment environments.	`admin:pipeline:bitbucket`

Atlassian Platform

read_teamwork_graph

Available using: OAuth 2.1 and API token authentication

Third-party data access: Teamwork Graph MCP tools can retrieve data from third-party services connected to Jira, such as linked pull requests, builds, and deployments.

GitHub for Atlassian: the data retrievable via MCP depends on the permission level you've granted to the connector.

Full access – MCP tools can retrieve GitHub data based on the user’s GitHub permissions
Limited access – MCP tools can retrieve GitHub data based on the user’s Jira permissions, which may differ from the user’s GitHub permissions. If a user can see a GitHub link in a Jira work item, they can retrieve only what they see on the Jira work item

You can check or change your access level in the GitHub for Atlassian configuration screen in Jira.

Other connectors: Azure DevOps, GitLab, Jenkins, and Spinnaker connectors follow the limited access model referenced above, meaning MCP tools can retrieve data based on Jira permissions and not the permissions set in the underlying third party service (e.g. Azure DevOps).

Tool	Description	Required scopes
`getTeamworkGraphContext` (beta)	Fetches entire context from Teamwork Graph for Jira Issues, Confluence entities and Atlassian Users. For Jira: linked deployments, PRs, builds, branches, commits, designs, issues, confluence whiteboards, feature flags, vulnerabilities, sprints, remote links. For Confluence pages/blogposts/whiteboards/spaces: child pages, comments, shared users, owners, linked entities, and more. For Atlassian Users: activity context including work items created, pages edited, PRs authored/reviewed, designs updated, and more.	`read:jira-work read:page:confluence read:comment:confluence read:space:confluence read:account read:3p-data:mcp read:home:mcp read:whiteboard:confluence read:confluence:mcp read:focus:mcp read:loom:mcp read:talent:mcp`
`getTeamworkGraphObject` (beta)	Fetches all available data for one or more objects (Atlassian or third-party) using their ARIs or URLs. Use for the objects fetched from the getTeamworkGraphContext tool.	`read:jira-work read:page:confluence read:comment:confluence read:space:confluence read:account read:3p-data:mcp read:home:mcp read:whiteboard:confluence read:confluence:mcp read:focus:mcp read:loom:mcp read:talent:mcp`

Tool

Description

Required scopes

getTeamworkGraphContext (beta)

Fetches entire context from Teamwork Graph for Jira Issues, Confluence entities and Atlassian Users.

For Jira: linked deployments, PRs, builds, branches, commits, designs, issues, confluence whiteboards, feature flags, vulnerabilities, sprints, remote links.

For Confluence pages/blogposts/whiteboards/spaces: child pages, comments, shared users, owners, linked entities, and more.

For Atlassian Users: activity context including work items created, pages edited, PRs authored/reviewed, designs updated, and more.

read:jira-work
read:page:confluence
read:comment:confluence
read:space:confluence
read:account
read:3p-data:mcp
read:home:mcp
read:whiteboard:confluence
read:confluence:mcp
read:focus:mcp
read:loom:mcp
read:talent:mcp

getTeamworkGraphObject (beta)

Fetches all available data for one or more objects (Atlassian or third-party) using their ARIs or URLs. Use for the objects fetched from the getTeamworkGraphContext tool.

read:jira-work
read:page:confluence
read:comment:confluence
read:space:confluence
read:account
read:3p-data:mcp
read:home:mcp
read:whiteboard:confluence
read:confluence:mcp
read:focus:mcp
read:loom:mcp
read:talent:mcp

search_atlassian

Available using: OAuth 2.1 and API token authentication

Tool	Description	Required scopes
`searchAtlassian` (beta)	Search across Jira and Confluence using natural language via Rovo.	`search:rovo:mcp`
`fetchAtlassian` (beta)	Fetch Jira or Confluence content by Atlassian Resource Identifier (ARI).	`search:rovo:mcp`

Compass tools

You can only use OAuth authentication with Compass tools.

read_compass

Available using: OAuth 2.1

Tool	Description	Required scopes
`getCompassComponent`	Get details for a Compass component by ID.	`read:component:compass`
`getCompassComponents`	Search or list Compass components.	`read:component:compass`
`getCompassComponentActivityEvents`	List recent activity events for a component.	`read:component:compass`
`getCompassComponentLabels`	Get the labels applied to a component.	`read:component:compass`
`getCompassComponentTypes`	List available Compass component types.	`read:component:compass`
`getCompassCustomFieldDefinitions`	List custom field definitions.	`read:component:compass`
`getCompassComponentsOwnedByMyTeams`	List components owned by your teams.	`read:component:compass`

write_compass

Available using: OAuth 2.1

Tool	Description	Required scopes
`createCompassComponent`	Create a Compass component.	`write:component:compass`
`createCompassComponentRelationship`	Create a relationship between two components.	`write:component:compass`
`createCompassCustomFieldDefinition`	Create a Compass custom field definition.	`write:component:compass`

Shared platform tools

These tools do not belong to a permission group and are required for overall MCP server operation.

Tool	Description	Required scopes
`atlassianUserInfo`	Get current Atlassian user details, such as account ID.	`read:me`
`getAccessibleAtlassianResources`	List Atlassian cloud sites (`cloudId`) that the user can access.	`read:account` , `read:me`

Disclaimer

MCP clients can perform actions in Jira, Confluence, and Compass with your existing permissions. Use least privilege, review high‑impact changes before confirming, and monitor audit logs for unusual activity.

Learn more: MCP Clients - Understanding the potential security risks

Need help? Contact Atlassian Support or visit the getting started guide.

Was this helpful?

It wasn't accurateIt wasn't clearIt wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community