| FMRS | 57 / 100 · C | 66 / 100 · C |
| Reliability | 10 / 20 | 8 / 20 |
|---|
| Security and permissions | 11 / 20 | 15 / 20 |
|---|
| Maintenance | 10 / 20 | 15 / 20 |
|---|
| Documentation | 13 / 20 | 15 / 20 |
|---|
| Setup experience | 13 / 20 | 13 / 20 |
| Best for | - Interactive editing sessions where documents are open in Word (Windows/macOS).
- Collaborative review where AI generates tracked changes and comments.
- Cross-platform creation and editing of .docx files without needing Word installed.
| - 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 | - Full cross-platform live features (some live tools are Windows-only, macOS has limitations).
- Team collaboration requiring online sync (server runs entirely locally).
- Non-technical users needing a GUI or no-code setup.
| - 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 | - Access to the local file system to read and write .docx files.
- Automation control of Microsoft Word via COM (Windows) or JXA (macOS).
- Ability to modify document content, including tracked changes, comments, formatting, etc.
| - 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 | - AI may accidentally modify wrong content; use tracked changes and undo to mitigate.
- Live editing depends on Word automation, which may be affected by Word version or permissions.
- Local-only operation ensures no data is collected, but document privacy is still a consideration.
| - 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 | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
| Tools | 3 | 0 |