| FMRS | 54 / 100 · D | 66 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 8 / 20 | 15 / 20 |
|---|
| Maintenance | 14 / 20 | 15 / 20 |
|---|
| Documentation | 13 / 20 | 15 / 20 |
|---|
| Setup experience | 11 / 20 | 13 / 20 |
|---|
| Best for | - Developers who use Jira and Confluence daily with Cline
- Individuals wanting to integrate Atlassian into AI workflows without context switching
- MCP-compatible client users seeking quick Atlassian integration
| - Developers, content creators, and project teams using Atlassian Cloud
- Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
- Users who need natural-language search, write, and cross-product workflows
|
|---|
| Not for | - Teams requiring enterprise-grade official support or Atlassian-maintained assurance
- Users without an MCP-compatible client
- High-compliance environments needing strict centralized token governance
| - Users without an Atlassian Cloud site or relevant product permissions
- Deployments requiring a self-hosted MCP server
- Users unwilling to grant an AI client access to Atlassian data or actions
- Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
|
|---|
| Required permissions | - Requires an Atlassian API token that inherits all permissions of its creator
- Tools can perform create, update, and delete mutations on Jira and Confluence data
- Runs locally and needs access to Atlassian cloud APIs
| - Jira and Confluence provide read, write, and search permission groups
- Jira Service Management provides read and write access through API tokens only
- Bitbucket Cloud provides read and write access through scoped API tokens only
- Compass is available through OAuth 2.1 only
- The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
- Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
|
|---|
| Risks and side effects | - The API token inherits all of the creator's permissions, so a leak is high-impact
- Never ask LLMs to analyze config files containing your token
- Third-party, non-official project; Atlassian API changes may require maintenance
- AI-driven mutations (deleting pages, transitioning issues) risk unintended changes
| - AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
- Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
- Use least privilege, scoped tokens, and minimal project or workspace access
- Require human confirmation for high-impact or destructive actions and monitor audit logs
|
|---|
| Supported clients | Cline, Claude Desktop, Cursor | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 0 | 0 |
|---|