Supported tools
This page lists all the tools supported by Atlassian Rovo MCP server. Each listed tool is organized into permission groups, with each grouping one or more Atlassian Rovo MCP server tools by intent (for example, read, write, or search). Organization admins grant or revoke access at the permission-group level, and each tool inherits the access of its parent group.
The tools listed on this page are only available with Atlassian Rovo MCP v2. Need help upgrading from v1? How to upgrade from Atlassian Rovo MCP v1 to Atlassian Rovo MCP v2
How the MCP server exposes tools
Rather than sending every tool definition to the AI client at connection time, Atlassian Rovo MCP exposes a small set of the most-utilized tools and lets the client find other tools demand. This keeps the client's context free for the user's actual task, and means new tools become available without the client needing to reconnect. Tools marked as Primary are visible directly to agents.
If you’re utilizing an MCP gateway or require all tools to be available, you can utilise the https://mcp.atlassian.com/v2/mcp?tools=all MCP endpoint to retrieve a paginated flat list of tools.
Common tools
ツール | 説明 |
|---|---|
| Get the current authenticated user's account information. |
| List all Atlassian sites and apps accessible to the authenticated user, including their |
| Natural-language search over the deferred tool catalogue. Returns a list of potentially related tools, their toolSchema and operations for running on |
| Execution pathway to run any deferred tools identified via |
| Returns the rich-content authoring format guidance to support improved document formatting and whiteboard creation. Reached through the |
Jira tools
read_jira
Available using: OAuth 2.1 and API token authentication
Required scope: read:jira:agent-interface
ツール | 説明 |
|---|---|
| Get a Jira work item by ID or key. |
| Get Jira spaces visible to the current user. |
| All work item types available in a Jira space. |
| Schema and field metadata for a specific work item type in a project, for creating work items with correct fields. |
| Available workflow transitions for a Jira work item. |
| Available work item link types in Jira. |
| Remote links associated with a Jira work item. |
| Paginated worklogs (logged time) for a Jira work item. |
| Look up a Jira user account ID by display name or email. |
| Find users assignable to a Jira space or work item. |
| Paginated comments for a Jira work item. |
| An work item’s field-change history, paginated oldest-first. |
| Details for the current Jira user. |
| Retrieves a Jira user's profile by account ID. |
| List of statuses a Jira work item can be in. |
| Components in a space, with IDs, names, work item counts, and ownership details. |
| A space’s releases/versions, or a single version. |
| Related work links (evidence) on a space version (release). |
| Lists boards visible to the current user. |
| A board's configuration: filter, column layout, and each column's mapped statuses. |
| The work items on a board, its backlog, or both, with optional count and JQL filtering. |
| Resolve a board plus its sprint data in one call; defaults to the active sprint. |
| Sprints from a board, optionally filtered to active, future, or closed. |
| Search saved filters visible to the current user, returning IDs and JQL. |
| Dashboards visible to the current user, for discovery and linking workflows. |
| Read a property from the key/value store on an work item, comment, worklog, dashboard item, or user. |
| Get a short-lived download URL for an attachment and a local command to save the file. |
write_jira
Available using: OAuth 2.1 and API token authentication
Required scope: write:jira:agent-interface
ツール | 説明 |
|---|---|
| Create a new Jira work item. |
| Edit an existing work item; only fields editable on that work item can be set. |
| Transition an work item to a new status, and/or assign it to a sprint or backlog. |
| Add a comment, or edit an existing one. |
| Log time on an work item, or edit an existing worklog. |
| Create a link between two Jira work items. |
| Create, update, release, or archive a space version (release or fix version). |
| Create or update related work links on a space version. |
| Create, populate, start, update, or close a sprint. |
| Create a company-managed board (scrum or kanban) from an existing filter. |
| Watch or unwatch a work item. |
| Attach a local file to an work item. |
| Set a property in the key/value store on an work item, comment, worklog, dashboard item, or user. |
search_jira
Available using: OAuth 2.1 and API token authentication
Required scope: search:jira:agent-interface
ツール | 説明 |
|---|---|
| Search Jira work items using JQL. |
delete_jira
delete_jira is disabled by default. An admin must enable it before you can be utilized.
Available using: OAuth 2.1 and API token authentication
Required scope: delete:jira:agent-interface
ツール | 説明 |
|---|---|
| Permanently delete an issue. Cannot be undone. |
| Permanently delete a comment from an issue. Cannot be undone. |
| Permanently delete an attachment from an issue. Cannot be undone. |
manage_jira
manage_jira is disabled by default. An admin must enable it before you can utilize it.
Available using: OAuth 2.1 and API token authentication
Required scope: manage:jira:agent-interface
ツール | 説明 |
|---|---|
| Create a new Jira space from a space template. |
| Update settings on an existing space. |
Confluence tools
read_confluence
Available using: OAuth 2.1 and API token authentication
Required scope: read:confluence:agent-interface
ツール | 説明 |
|---|---|
| Read any Confluence content such as page, blog, live doc, comment, whiteboard, embed, database, or folder. |
| List content of one type within a single space. |
| List spaces accessible to the caller. |
| Retrieve a space by ID or key, including enabled content types, optional labels, and configured space instructions. |
| The space instructions configured for a space. |
| The current user's personal space. |
| List comments on a page or blog post. |
| A single comment by ID. |
| Version history for a page, live doc, or blog post, newest first. |
| One historical version of a page, live doc, or blog post. |
| A unified diff between two versions of a page, live doc, or blog post. |
| Attachment metadata for a content item. |
| Attachment metadata by attachment ID. |
| An attachment download URL plus a local curl command. |
| Export content as PDF or Word and return a download link. |
| The explicit content-level permission grants on a content entity, each pairing an operation with a principal. |
| General access for a content entity: |
| The external public-link (anonymous share) status of a page. |
| Emoji reactions on Confluence content. |
| A single inline task by ID. |
| Inline tasks, optionally scoped to a page or blog post and filtered by status. |
| List templates and blueprints. |
| A template body. |
| Resolve supported macro wrappers into per-macro HTML as displayed in Confluence web. |
write_confluence
Available using: OAuth 2.1 and API token authentication
Required scope: write:confluence:agent-interface
ツール | 説明 |
|---|---|
| Create a page, blog post, live doc, whiteboard, database, embed, smart link, or folder. |
| Update docs, whiteboards, or databases, via full-body replacement or granular edits. |
| Create a space. The response includes its ID, key, and homepage ID. |
| Set the space instructions for a space. |
| Copy a page, whiteboard, database, folder, or embed to a new parent. |
| Move a page, whiteboard, database, folder, or embed to a new parent or sibling position. |
| Archive a single content entity. |
| Unarchive (restore) a single content entity. |
| Restore an earlier version as a new latest version. |
| Convert a page or live doc between classic page mode and live-doc mode. |
| Set the content state (status) of a page or blog post. |
| Create or reply to a footer or inline comment on a page or blog post. |
| Update an existing footer or inline comment. |
| Resolve or reopen a footer or inline comment. |
| Prepare an attachment upload and return a local curl command. |
| Add labels to any content. |
| Add an emoji reaction to Confluence content. |
| Add content-level permission grants, preserving existing grants for other principals. |
| Remove content-level permission grants, optionally narrowed by operation, principal type, or principal. |
| Replace all content-level permission grants with the supplied set. Grants absent from the request are removed. |
| Set the high-level restriction state for a content entity. |
| Enable the external public link (anonymous share) for a page. |
| Disable the external public link for a page. |
| Marks an action item on a page as done. |
| Marks a completed action item as not done. |
| Stars a page for the user. |
| Removes a star from a page. |
| Stars a space for the user. |
| Removes a star from a space. |
| Subscribes the user to updates on a page. |
| Unsubscribes the user from updates on a page. |
| Subscribes the user to updates in a space. |
| Unsubscribes the user from updates in a space. |
| Subscribes the user to updates on content carrying a label. |
| Unsubscribes the user from updates on a label. |
search_confluence
Available using: OAuth 2.1 and API token authentication
Required scope: search:confluence:agent-interface
ツール | 説明 |
|---|---|
| Search Confluence content with CQL. |
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
ツール | 説明 | Required scopes |
|---|---|---|
| Get an operations alert by ID or alias, or search query. |
|
| List on-call schedules or get current/next responders. |
|
| List operation teams and team details. |
|
write_jsm
Available using: API token authentication
ツール | 説明 | Required scopes |
| Perform alert actions, like acknowledge, unacknowledge, close, or escalate an alert. |
|
Bitbucket Cloud tools
These tools are only available if your Bitbucket workspace is linked to an organization. Bitbucket workspaces not linked to an organization won’t be selectable when authenticating.
read_bitbucket
Available using: OAuth 2.1 and API token authentication
Required scope: read:bitbucket:agent-interface
ツール | 説明 |
|---|---|
| Workspaces the user is a member of. |
| Get a workspace. |
| Repositories in a workspace. |
| Get a repository. |
| The effective default reviewers for a repository. |
| Get file or directory content. |
| Get a branch. |
| Get a commit. |
| List code-insights reports on a commit. |
| Get a code-insights report on a commit. |
| The annotations of a commit report. |
| List pull requests in a repository. |
| Get a pull request. |
| The diff of a pull request. |
| Comments on a pull request. |
| The tasks on a pull request. |
| Pipelines for a repository. |
| Get a pipeline. |
| The steps of a pipeline. |
| Get a pipeline step. |
| The log of a pipeline step. |
| Deployments for a repository. |
| Get a deployment. |
| Deployment environments for a repository. |
| Get a deployment environment. |
write_bitbucket
Available using: OAuth 2.1 and API token authentication
Required scope: write:bitbucket:agent-interface
ツール | 説明 |
|---|---|
| Create a pull request. |
| Update a pull request. |
| Merge a pull request. |
| Approve a pull request. |
| Request changes on a pull request. |
| Add a comment to a pull request. |
| Resolve a comment thread on a pull request. |
| Reopen a resolved comment thread. |
| Create a task on a pull request. |
| Resolve or reopen a pull request task. |
| Create a branch. |
| Create a commit. |
| Run a pipeline. |
アトラシアンのプラットフォーム
read_teamwork_graph
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).
Available using: OAuth 2.1 and API token authentication
Required scope: read:all:twg
ツール | 説明 |
|---|---|
| Retrieves connected context from Teamwork Graph for any Atlassian entity. Returns all relationships and linked objects in one traversal, including cross-product and third-party connections. Use when the answer requires connections between entities, not just a single entity's fields. Supported entry points:
Note: Utilizing this tool may consume up to 10 Rovo credits. |
| 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 |
write_teamwork_graph
Available using: OAuth 2.1 and API token authentication
Required scope: write:all:twg
ツール | 説明 |
|---|---|
| Adds a relationship between two objects in the Teamwork Graph. |
search_atlassian
Available using: OAuth 2.1 and API token authentication
Required scope: search:rovo:agent-interface
ツール | 説明 |
|---|---|
| Semantic search across Jira, Confluence, and connected apps using natural language, through Rovo. Note: Utilizing this tool may consume up to 10 Rovo credits. |
search_code
Available using: OAuth 2.1
Required scope: search:code:agent-interface
ツール | 説明 |
|---|---|
| Searches source code across connected source-control providers, returning the files that match and the specific lines within them. |
| Reads the full contents of one file in a connected repository at a specific commit. |
| Lists the files and subfolders under a path in a connected repository, page by page. |
| Lists a repository's file paths at a specific commit, without reading any file contents. |
| Finds where a function, class, or variable is defined and everywhere it is used, including in other repositories. |
| Given two commits, reports which parts of the code the change touches and everywhere else those parts are referenced. |
Loom tools
Only Loom workspaces linked to an Atlassian site are available.
read_loom
Available using: OAuth 2.1 and API token authentication
Required scope: read:loom:agent-interface
ツール | 説明 |
|---|---|
| A video's core metadata, and optionally its transcript, comments, AI agent briefs, AI-extracted meeting action items, or attached links. |
| The videos you own, most recent first. |
| Videos others have shared with you, most recent first. |
| Comments on a video, each with author and the in-video timestamp it is anchored to. |
| The AI-generated meeting action items Loom extracted from a recording. |
| A time-limited signed URL to download the MP4 file itself. |
| Folders in the current workspace a video can be moved into. |
write_loom
Available using: OAuth 2.1 and API token authentication
Required scope: write:loom:agent-interface
ツール | 説明 |
|---|---|
| Step 1 of 2 for uploading a new video. |
| Step 2 of 2, finalises the video publishing |
| Rename a video. The change is immediate and visible to all viewers. |
| Set visibility to |
| Share a video with specific Atlassian users by notification. Notifies people; does not change visibility. |
| Post a comment on a video, anchored to a point in seconds. |
| Add an emoji reaction to a video, anchored to a point in the video. |
| Create a folder in the current workspace, optionally nested or placed in a space. |
| Move a video into a folder in the current workspace. |
| Re-process a video that failed to process or is stuck. |
Goals tools
read_goals
Available using: OAuth 2.1 and API token authentication
Required scope: read:goals:agent-interface
ツール | 説明 |
|---|---|
| Find goals by text and structured filters. |
| One goal by its exact ARI or key, with optional related details. |
| One goal update by its exact ARI, with optional related details. |
| The goal types available in a site for creating goals and success measures. |
write_goals
Available using: OAuth 2.1 and API token authentication
Required scope: write:goals:agent-interface
ツール | 説明 |
|---|---|
| Create a goal or success measure using an enabled goal type. |
| Create a progress update for an existing goal. |
| Add one type of connection to one or more goals. |
Projects tools
read_projects
Available using: OAuth 2.1 and API token authentication
Required scope: read:projects:agent-interface
ツール | 説明 |
|---|---|
| Find projects by text and structured filters. |
| One project by its exact ARI or key, with optional related details. |
| One project update by its exact ARI, with optional related details. |
write_projects
Available using: OAuth 2.1 and API token authentication
Required scope: write:projects:agent-interface
ツール | 説明 |
|---|---|
| Create an Atlassian project. |
| Create a progress update for an existing project. |
| Add one type of connection to one or more projects. |
Teams tools
read_teams
Available using: OAuth 2.1
Required scope: read:teams:agent-interface
ツール | 説明 |
|---|---|
| Search teams by name with cursor pagination; |
| Core metadata for one team, with optional expansions for members, projects, goals, and hierarchy. |
write_teams
Available using: OAuth 2.1
Required scope: write:teams:agent-interface
ツール | 説明 |
|---|---|
| Create a team with |
| Update a team. |
Focus tools
read_focus
Available using: OAuth 2.1 and API token authentication
Required scope: read:focus:agent-interface
ツール | 説明 |
|---|---|
| Search focus areas by text and structured filters. |
| A focus area by UUID, ARI, or page URL, with optional expansions. |
| The configured focus-area type hierarchy for a workspace. |
write_focus
Available using: OAuth 2.1 and API token authentication
Required scope: write:focus:agent-interface
ツール | 説明 |
|---|---|
| Create a focus area in a workspace. |
| Update name, owner, start date, or description on an existing focus area. |
| Post a status update recording a change to status and/or target date, with an optional progress summary. |
| Link sub-focus areas to a focus area, one connection type per call. |
Talent tools
read_talent
Available using: OAuth 2.1 and API token authentication
Required scope: read:talent:agent-interface
ツール | 説明 |
|---|---|
| Resolve the calling user's own place in the workspace: their position entity ID, their manager's, and their role. |
| Discover the workspace's queryable fields, or resolve valid filter values for one field. |
| Search positions by their own attributes using an RQL filter, paginated. |
| Read a single position by ARI, with its selected field values and optionally the worker filling it. |
| Positions attached to an entity - for example the direct reports of a manager position. |
| Aggregate positions into counts grouped by up to four field IDs - headcount by country, status, level, job family, or manager. |
write_talent
Available using: OAuth 2.1 and API token authentication
Required scope: write:talent:agent-interface
ツール | 説明 |
|---|---|
| Create a skill in the skills hierarchy, optionally nested under a parent skill. |
| Assign skills to a worker, or decline skills previously assigned to them. |
| Allocates a position to a focus area, or clears its allocation. A position is allocated to one focus area at a time, so setting a new one replaces the current allocation. |
免責事項
MCP clients can perform actions across Atlassian apps 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.
この内容はお役に立ちましたか?