atlassian-mcp-server
Official MCP server for integrating Atlassian products with AI tools through OAuth and API tokens
GraphCanon updated 4w · GitHub synced 4w
Decision brief
The atlassian-mcp-server is an official repository designed to bridge Atlassian products including Jira, Confluence, and Bitbucket with AI tools via the Model Context Protocol using OAuth 2.1 or API tokens.
Good fit when
- When needing secure integration of Atlassian apps with AI like ChatGPT or VS Code through modern authentication
- To leverage official support for connection protocols between Atlassian products and AI tools
Avoid when
- If only generic third-party integrations without official Atlassian support are required
- For environments that do not allow OAuth 2.1 or API token-based authentication methods
Observed Jul 17, 2026 · Source: enrich:decision_facts
Verify the decision
Adoption
Package downloads where a registry match exists. GitHub stars (910) are secondary evidence.
- npm downloads (30d)
- 185·npm downloads API·4w
Maintenance and security
Full trust report- Maintenance
- Active (18d since push)
- As of 4w
- Provenance
- Not a fork · Organization account
- As of 4w
- Security (OSV)
- No MCP manifest
- As of 1mo
Public GitHub metadata and optional OSV scans. Signals, not a guarantee. Trust methodology.
Install
npm install atlassian-mcp-serverSimilar tools
Same-category neighbours. No typed graph edges are catalogued for this tool yet.
Evidence and technical details
Sourced facts, taxonomy, compatibility claims, README excerpt, and machine-readable endpoints.
Overview
Repository for the official remote MCP server facilitating secure connections between Atlassian applications such as Jira, Confluence, and Bitbucket to AI tools like Claude, ChatGPT, VS Code, using modern authentication methods. Supports integration via Model Context Protocol.
Capability facts
- MCP server
- No MCP server detected
Source: repo_scan · Jul 27, 2026
- Languages
- javascript
Source: github.language · Jul 27, 2026
Categories
Tags
README
Installation and access
- Not a Marketplace app: The Atlassian Rovo MCP Server is not installed via the Atlassian Marketplace or the Manage apps screen. Instead, it is installed automatically the first time a user completes the OAuth 2.1 (3LO) consent flow (just-in-time, or "lazy loading," installation).
- First-time installation requirements: The first user to complete the 3LO consent flow for your site must have access to the Atlassian apps requested by the MCP scopes (for example, Jira and/or Confluence). This ensures the MCP app is registered with the correct permissions for your site.
- Subsequent user access: After the initial install, users with access to only one Atlassian app (for example, just Jira or just Confluence) can also complete the 3LO flow to access that app through MCP.
For agents
This page has a .md twin and JSON over the API.