Atlassian Rovo MCP Server

Official

Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.

Remote serverstreamable-httpsseJavaScriptApache-2.0★ 923

What is the Atlassian Rovo MCP Server?

Atlassian's official cloud-hosted Rovo MCP server connects Jira, Confluence, Jira Service Management, Bitbucket and Compass to AI clients via OAuth 2.1.

Configuration

An Atlassian Cloud site with at least one supported product. Local clients need Node.js 18+ to run the mcp-remote proxy, and a browser for the OAuth 2.1 flow (or an admin-enabled API token for headless setups).

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

What you can do with it

Turning meeting notes into tickets

Paste raw notes and have the assistant create the five Jira issues that fall out of them, in the right project, with sensible summaries and descriptions.

Context while you code

From your IDE, ask what the acceptance criteria on the ticket you are implementing actually say, and log work against it without leaving the editor.

Sprint and incident summaries

Run a JQL search for open bugs in a project, or read JSM alerts, and get a written status digest instead of scanning boards.

Service catalogue upkeep

Create a Compass component from the current repository and query what depends on a service before you plan a breaking change.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
atlassianUserInfoReturn details about the currently authenticated Atlassian user.
getAccessibleAtlassianResourcesList the cloudId values you can reach; required before any other call because every tool needs a cloudId.
getJiraIssueFetch a single Jira issue by key or id.
createJiraIssueCreate a Jira issue in a given project and issue type.
editJiraIssueUpdate fields on an existing Jira issue.
transitionJiraIssueMove a Jira issue through a workflow transition.
addCommentToJiraIssuePost a comment on a Jira issue.
addWorklogToJiraIssueLog time against a Jira issue.
searchJiraIssuesUsingJqlRun a JQL query and return matching issues.
getVisibleJiraProjectsList Jira projects the authenticated user can see.
getTransitionsForJiraIssueList workflow transitions available on an issue.
getConfluencePageRetrieve a Confluence page and its content.
createConfluencePageCreate a new Confluence page in a space.
updateConfluencePageUpdate the body or title of an existing Confluence page.
getConfluenceSpacesList Confluence spaces available to the user.
getPagesInConfluenceSpaceList the pages contained in a Confluence space.
searchConfluenceUsingCqlSearch Confluence content with a CQL query.
createConfluenceFooterCommentAdd a footer comment to a Confluence page.
getJsmOpsAlertsRead Jira Service Management Operations alerts (API-token auth only).
updateJsmOpsAlertUpdate a Jira Service Management Operations alert (API-token auth only).
getTeamworkGraphContextAggregate contextual information across Atlassian products and connected apps.
getTeamworkGraphObjectFetch a specific object from the Atlassian Teamwork Graph.

How to install the Atlassian Rovo MCP Server

claude mcp add atlassian https://mcp.atlassian.com/v1/mcp/authv2 -t http

Configuration

An Atlassian Cloud site with at least one supported product. Local clients need Node.js 18+ to run the mcp-remote proxy, and a browser for the OAuth 2.1 flow (or an admin-enabled API token for headless setups).

Example prompts to try

  • “Find all open bugs in project ALPHA created in the last two weeks and summarise the common themes.”
  • “Create a Confluence page called 'Team Goals Q3' in the Engineering space using the bullet points below.”
  • “Read the Confluence page linked from this Jira epic and tell me which acceptance criteria are not covered by the subtasks.”
  • “Transition ticket ALPHA-412 to In Review and add a comment explaining what changed.”

Frequently asked questions

Use https://mcp.atlassian.com/v1/mcp/authv2 for most clients. The older https://mcp.atlassian.com/v1/mcp endpoint still works and is what API-token configurations typically use. The legacy SSE endpoint at /v1/sse is supported but Atlassian recommends migrating custom clients off it.