| FMRS | 37 / 100 · D | 66 / 100 · C |
|---|
| Reliability | 6 / 20 | 8 / 20 |
|---|
| Security and permissions | 8 / 20 | 15 / 20 |
|---|
| Maintenance | 8 / 20 | 15 / 20 |
|---|
| Documentation | 8 / 20 | 15 / 20 |
|---|
| Setup experience | 7 / 20 | 13 / 20 |
|---|
| Best for | - Developers who need quick access to technical documentation and API guides
- Product managers searching for requirements, specs, and project updates
- HR teams accessing policy documents and employee resources quickly
- Support teams finding troubleshooting guides and knowledge base articles
- Anyone who wants to interact with Confluence using natural language
| - 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 Server or Data Center (on-premise), as this tool supports only Confluence Cloud.
- Legacy users expecting specific domain tools (like conf_ls_spaces), but v3.0 migrated to generic HTTP method tools.
| - 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 account with access to Confluence and the spaces you want to query.
- Requires an API token (permissions granted automatically upon creation).
- The server uses your own credentials and runs locally.
| - 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 risk: If your API token is compromised, others may access your Confluence data. Store it securely.
- Data access scope: AI assistants can read and modify all content you have permission to access, including create, update, delete.
- Large responses can lead to high token costs: always use jq filtering and limit parameters to avoid unexpected costs.
- Response truncation: Responses exceeding ~40,000 characters are truncated, and the full raw data is saved to a temporary file.
| - 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, Cursor AI, Continue | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 5 | 0 |
|---|