Atlassian Rovo MCP Server

The Atlassian Rovo MCP Server is Atlassian's official, cloud-hosted Model Context Protocol gateway for connecting AI assistants, IDEs, and agent platforms to an Atlassian Cloud site. Unlike community Jira or Confluence MCP servers that wrap individual REST endpoints, the Rovo server is operated by Atlassian, uses the same Teamwork Graph and Rovo search infrastructure that powers Rovo agents, and respects existing user permissions, IP allowlists, and admin-controlled tool groups.

The server exposes read, write, and search tools across Jira, Confluence, Compass, Bitbucket Cloud, and Jira Service Management Operations, plus cross-product tools (searchAtlassian, fetchAtlassian, getTeamworkGraphContext) that span products. Tools are bundled into permission groups (for example read_jira, write_confluence, search_atlassian) so admins can enable or disable capabilities at a granular level. Authentication is via OAuth 2.1 by default, with API token authentication available for headless setups. Bitbucket Cloud tools require API tokens with scopes.

It is separate from any self-hosted Jira/Confluence MCP server because there is no code to run: clients connect directly to https://mcp.atlassian.com/v1/mcp/authv2. Local clients without native HTTP MCP support can bridge to it using mcp-remote. The companion GitHub repo atlassian/atlassian-mcp-server is not the server itself; it ships reference .mcp.json and AGENTS.md files that teams can drop into a project to preconfigure default cloudId, project keys, and space IDs for their agents.

Tools

Prerequisites

• An Atlassian Cloud site with Jira, Confluence, Compass, Bitbucket, or JSM
• Node.js v18+ (only for clients that need the mcp-remote proxy)
• For Bitbucket Cloud tools: an API token with the appropriate scopes

VS Code

Add to your MCP settings:

{
  "servers": {
    "atlassian-mcp-server": {
      "url": "https://mcp.atlassian.com/v1/mcp/authv2",
      "type": "http"
    }
  }
}

Cursor (recent versions, native HTTP)

{
  "Atlassian-MCP-Server": {
    "url": "https://mcp.atlassian.com/v1/mcp/authv2"
  }
}

Claude Desktop and other stdio-only clients

Use the mcp-remote proxy to bridge to the remote server:

{
  "mcpServers": {
    "Atlassian-Rovo-MCP": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.atlassian.com/v1/mcp/authv2"]
    }
  }
}

On first connection a browser window opens to complete the OAuth 2.1 flow against your Atlassian Cloud site. For headless setups, configure API token authentication instead (admin must enable this in org settings).

Notes

• The older /v1/sse endpoint is deprecated and will stop working after 30 June 2026. Use /v1/mcp/authv2.
• Admins control which tool permission groups (for example write_jira, write_confluence) are exposed via the org's security and access policies.

• Triage incoming work: have an agent run searchJiraIssuesUsingJql for stale tickets, summarize them, and post status updates via addCommentToJiraIssue.
• Generate Jira tickets in bulk from a meeting transcript or PRD, with createJiraIssue + transitionJiraIssue plus matching Confluence pages via createConfluencePage.
• Build a Confluence page from scratch (or update an existing one) using searchAtlassian + fetchAtlassian to gather source material, then updateConfluencePage.
• Use Compass tools to bootstrap a service catalog: createCompassComponent from CSV/JSON and createCompassComponentRelationship to model dependencies.
• Wire JSM Operations into an agent that acknowledges or escalates alerts (getJsmOpsAlerts, updateJsmOpsAlert) and links them to incident pages in Confluence.

• "Find all open Jira bugs in project PLAT assigned to me, summarize them, and add a comment on each asking the reporter for a repro."
• "Create a Confluence page in the Engineering space titled 'Q3 Platform Roadmap' using the bullet list I just pasted, and link it from PLAT-1423."
• "Search Atlassian for everything related to the 'checkout latency' incident and give me a single timeline."
• "Register a new Compass component called 'payments-gateway' owned by team-payments and link it as a dependency of 'checkout-api'."
• "Acknowledge JSM alert ALERT-559, set its priority to P2, and open a Jira incident ticket linked to it."

• Official and fully managed by Atlassian, with no server process to host or update.
• Broad coverage across Jira, Confluence, Compass, Bitbucket Cloud, and JSM Operations, plus cross-product Rovo search and Teamwork Graph tools.
• Permission groups let admins enable or disable read, write, and search capabilities per product, and all access respects existing user permissions and IP allowlists.
• OAuth 2.1 authentication works out of the box with modern MCP clients; API token auth is available for headless agents.

• Cloud only: there is no support for Jira Data Center or Server deployments.
• Bitbucket Cloud tools require API token authentication with explicit scopes, so they do not work via the standard OAuth flow.
• Rate limits are tiered by Atlassian Cloud subscription, and the legacy /v1/sse endpoint is being retired (after 30 June 2026), so older client configs need updating.

• sooperset/mcp-atlassian: popular community MCP server for Jira and Confluence that also supports Server/Data Center deployments.
• GitHub Copilot Coding Agent with built-in Atlassian connectors for users who only need a few Jira/Confluence actions inside an IDE.
• Atlassian Forge custom agents or Zapier MCP for workflow automation that does not need direct LLM tool calling.