Atlassian MCP Server

The Atlassian Rovo MCP Server is Atlassian's officially hosted remote Model Context Protocol server that connects AI assistants and IDEs to Jira, Confluence, Compass, Jira Service Management, and Bitbucket Cloud. It is a cloud-hosted endpoint (no install required) that uses OAuth 2.1 with dynamic client registration as the primary auth method, with API tokens available for headless setups when an admin enables them. All actions respect existing user permissions, IP allowlists, and audit logging in the connected Atlassian Cloud site.

The server exposes tools organized into permission groups (read_jira, write_jira, search_jira, read_confluence, write_confluence, search_confluence, read_jsm, write_jsm, read_bitbucket, write_bitbucket, read_compass, write_compass) plus cross-platform helpers like searchAtlassian and getTeamworkGraphContext. Capabilities include searching issues with JQL, creating and transitioning Jira issues, reading and writing Confluence pages and comments, managing Compass components, querying and acting on JSM alerts, and inspecting Bitbucket repos, pull requests, pipelines, and deployments.

The server is supported by major MCP clients including Claude, ChatGPT, GitHub Copilot CLI, Gemini CLI, Amazon Quick Suite, VS Code, and Cursor, and works with any MCP-compatible client via the mcp-remote proxy. The legacy SSE endpoint (/v1/sse) is being deprecated after June 30, 2026, in favor of the streamable HTTP endpoint at /v1/mcp/authv2.

Tools

Prerequisites

• Atlassian Cloud site with Jira, Confluence, Compass, JSM, or Bitbucket Cloud access
• A user account with permissions on the resources you want to access
• Node.js v18+ (only needed for clients that connect via the mcp-remote proxy)
• Modern browser for the OAuth 2.1 sign-in flow

The first time you connect, you (or an organization admin) may need to approve the Atlassian Rovo MCP app for your site. API tokens are an optional alternative for headless setups and must be enabled by an admin.

Server URL

https://mcp.atlassian.com/v1/mcp/authv2

The older SSE endpoint https://mcp.atlassian.com/v1/sse is deprecated and will stop working after June 30, 2026.

VS Code (.vscode/mcp.json)

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

Cursor

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

Claude Desktop and other clients via mcp-remote

For clients that do not yet support remote HTTP MCP servers natively, proxy through mcp-remote:

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

On first run, mcp-remote opens a browser window to complete OAuth 2.1 sign-in with your Atlassian account.

• Triage and update Jira tickets from an IDE: search with JQL, transition status, add worklogs, and post comments without leaving Claude or VS Code.
• Auto-generate Jira issues from meeting notes, design docs, or PR descriptions, then link them to the relevant Confluence pages.
• Summarize Confluence spaces and draft or update pages (release notes, runbooks, RFCs) directly from an AI assistant.
• Respond to incidents by querying JSM Ops alerts, acknowledging or escalating them, and checking on-call schedules from chat.
• Inspect Bitbucket Cloud pull requests, pipelines, and deployments, and cross-link them to the Jira issues they implement.

• "Search Jira for all open bugs assigned to me in the PLAT project and summarize them by priority."
• "Create a Confluence page in the Engineering space titled Q3 Release Notes from the latest 10 closed issues with label release-q3."
• "Transition PROJ-1423 to In Review, add a comment linking the Bitbucket PR, and log 2h of work."
• "Find any JSM alert containing database connection in the last hour and acknowledge it."
• "Show me the Compass component for checkout-service and list its dependencies and recent activity."

• Officially built and hosted by Atlassian, with no self-hosting or token management required for OAuth users.
• Broad product coverage: Jira, Confluence, Compass, Jira Service Management, and Bitbucket Cloud in one endpoint.
• Granular permission groups (read_*, write_*, search_*) that admins can enable or revoke per tool group.
• Respects existing user permissions, IP allowlists, and audit logging in the Atlassian Cloud site.

• Cloud-only: does not support Jira/Confluence Data Center or Server deployments.
• Some tools (JSM, Bitbucket) require API token auth rather than OAuth, which an admin must enable.
• The legacy SSE endpoint is being deprecated, so existing integrations must migrate to /v1/mcp/authv2 before June 30, 2026.

• sooperset/mcp-atlassian: popular community MCP server that supports both Atlassian Cloud and Data Center/Server.
• Linear MCP server: alternative if you use Linear instead of Jira for issue tracking.
• Notion MCP server: alternative for teams using Notion instead of Confluence for documentation.