| FMRS | 38 / 100 · D | 66 / 100 · C |
|---|
| Reliability | 3 / 20 | 8 / 20 |
|---|
| Security and permissions | 6 / 20 | 15 / 20 |
|---|
| Maintenance | 7 / 20 | 15 / 20 |
|---|
| Documentation | 8 / 20 | 15 / 20 |
|---|
| Setup experience | 14 / 20 | 13 / 20 |
|---|
| Best for | - Organizations using Atlassian Confluence Data Center.
- Teams that need AI access to internal documentation.
- Developers looking to integrate Confluence content into automated processes.
| - 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 on Confluence Cloud instead of Data Center (may work but not explicitly supported).
- Scenarios requiring advanced permission management or audit features.
- Production environments with high stability requirements, as this is a community-maintained project.
| - 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 API access to the Confluence instance, typically via a Personal Access Token.
- Depending on token permissions, can read, create, update, or delete Confluence content.
- Ability to make network requests to the Confluence instance's API.
| - 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 | - Token leakage could lead to unauthorized access to Confluence data.
- Community-maintained project may lack timely security updates.
- Operational errors could inadvertently delete or modify important documents.
| - 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 | 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 |
|---|