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.
The Atlassian Rovo MCP Server supports tools across the following Atlassian apps:
Jira tools
Confluence tools
Jira Service Management tools
Bitbucket Cloud tools
Rovo code / Shared platform tools
Teamwork Graph tools
Compass tools
Jira tools
ツール | 説明 | Required scopes |
|---|---|---|
| Add a comment to a Jira issue. |
|
| Adds a time tracking worklog to a Jira issue |
|
| Create a new Jira issue in a project and issue type. |
|
| Update fields on an existing Jira issue. |
|
| Get a Jira issue by ID or key. |
|
| List remote issue links (for example, Confluence links) on a Jira issue. |
|
| Get create‑field metadata for a project and issue type. |
|
| List issue types available in a Jira project. |
|
| List available workflow transitions for a Jira issue. |
|
| List Jira projects the user can view, browse, edit, or create issues in. |
|
| Find Jira user account IDs by name or email. |
|
| Search Jira issues using a JQL query. |
|
| Perform a workflow transition on a Jira issue. |
|
Confluence tools
ツール | 説明 | Required scopes |
|---|---|---|
| Create a footer comment (or reply) on a page. |
|
| Create an inline comment or reply tied to selected text. |
|
| Create a new Confluence page or live doc with a Markdown body. |
|
| Get a Confluence page or live doc by ID, with body as Markdown. |
|
| List descendant pages under a given parent page. |
|
| List footer comments on a page, as Markdown. |
|
| List inline comments on a page. |
|
| List Confluence spaces (by key, id, type, status, labels, etc.). |
|
| List pages in a space, optionally filtered by title, status, or type. |
|
| Search Confluence content using a CQL query. |
|
| Update an existing Confluence page or live doc (title, body, location). |
|
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.
ツール | 説明 | Required scopes |
|---|---|---|
| Get an operations alert by ID or alias, or search alerts by query and time window. |
|
| List on-call schedules or get current/next on-call responders for a schedule. |
|
| List operation teams and fetch team details, like escalation policies and roles. |
|
| Perform alert actions, like acknowledge, unacknowledge, close, or escalate an alert. |
|
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.
ツール | 操作 | 説明 | Required scopes |
|---|---|---|---|
| list | List all workspaces |
|
| get | Get a specific workspace |
|
| list | List repositories in a workspace |
|
| get | Get a specific repository |
|
| branch.get | Get a branch |
|
| branch.create | Create a new branch |
|
| commit.create | Create a commit |
|
| commit.get | Get a specific commit |
|
| files.get | Get file/directory contents at a ref |
|
| 作成 | Create a new pull request |
|
| get | Get a specific pull request |
|
| list | List pull requests |
|
| comment | Add a comment to a pull request |
|
| コメント | List comments on a pull request |
|
| diff | Get the diff of a pull request |
|
| approve | プル リクエストの承認 |
|
| merge | プル リクエストのマージ |
|
| list | List pipelines |
|
| get | Get a specific pipeline |
|
| [実行] をクリックします。 | Trigger a pipeline |
|
| steps | List steps for a pipeline |
|
| step.get | Get a specific pipeline step |
|
| step.log | Get the log for a pipeline step |
|
| list | List environments |
|
| get | Get a specific environment |
|
| 作成 |
|
|
| update |
|
|
| 削除 |
|
|
| list | List deployments |
|
| get | Get a specific deployment |
|
Rovo code / Shared platform tools
ツール | 説明 | Required scopes |
|---|---|---|
| Get current Atlassian user details, such as account ID. |
|
| List Atlassian cloud sites ( |
|
| Fetch Jira or Confluence content by Atlassian Resource Identifier (ARI). |
|
| Use Rovo Search across Jira and Confluence for natural‑language queries, not CQL and JQL. |
|
Teamwork Graph tools
Teamwork Graph tools only support authentication via API token. These tools are only available if authentication via API token is enabled by your organization admin.
These tools introduce two new scopes: read:3P-data:mcp and read:home:mcp. You will need to create a new token with these scopes to make full use of these tools.
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).
ツール | 説明 | Required Scopes |
|---|---|---|
| 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 |
| 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 |
Compass tools
You can only use OAuth authentication with Compass tools.
ツール | 説明 | Required scopes |
|---|---|---|
| Create a Compass component (service, library, etc.). |
|
| Create a relationship between two Compass components. |
|
| Create a Compass custom field definition. |
|
| Delete an existing Compass component, including its definitions and links. |
|
| Remove a relationship between two Compass components. |
|
| Delete an existing Compass custom field definition from your catalog. |
|
| Get details for a Compass component by ID. |
|
| List recent activity events for a Compass component, for example, deployments or alerts. |
|
| Get the labels applied to a Compass component. |
|
| List available Compass component types, for example, service, library, or application. |
|
| Search or list Compass components. |
|
| List Compass components owned by your teams. |
|
| List Compass custom field definitions. |
|
免責事項
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.
この内容はお役に立ちましたか?