| FMRS | 59 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 10 / 20 | 15 / 20 |
|---|
| Maintenance | 12 / 20 | 15 / 20 |
|---|
| Documentation | 15 / 20 | 15 / 20 |
|---|
| Setup experience | 14 / 20 | 13 / 20 |
|---|
| Best for | - Users who have Outlook Desktop installed and want to avoid cloud API integration.
- Users who need quick setup without OAuth or admin consent.
- Users who want to leverage local Outlook session and cached data.
| - 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 | - Users who do not use Outlook Desktop.
- Users who need cloud API or remote access to Outlook data.
- Users on unsupported Outlook versions (e.g., new Outlook on Windows without COM) or without necessary permissions (macOS).
| - 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 | - Windows: Access to Outlook COM object model; may require authorization or registry policy changes.
- macOS: Requires Automation and Accessibility permissions to control Outlook via osascript and read Exchange inbox.
| - 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 | - Programmatic Access prompts may appear; must allow access or configure registry.
- Automated tools could be misused by malicious instructions, potentially sending or modifying emails, calendar, or tasks unexpectedly.
- Local-only, not cloud-based.
| - 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 | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 29 | 0 |
|---|